Within the ControlLogix RSL5K Online application file Project Tree, beneath the 1756 EtherNet/IP bridge, add the CompactLogix controller's EtherNet/IP port (or , if using a dedicated 1769 module, first add the bridge and then the CompactLogix controller) and its relevant I/O hardware configuration.
If using RSL5K Rev.16 or older you will have to edit the RSL5K application Project Tree Offline and then download it to the CLX controller.
Once done, within the CLX RSL5k Online application file, browse the newly edited Ethernet network and ensure the CLX controller "sees" all the relevant CompactLogix system components.
If there are no "yellow" triangles attached to the CompactLogix system's components it means that you have established a ControlLogix backplane -> EtherNet/IP -> CompactLogix backplane connection.
Once there, you could use any CompactLogix Inputs within your ControlLogix application presuming your CLX "owns" the CompactLogix relevant Input modules.
Also, your CLX could "listen" to any CompactLogix Output modules (the XIC or XIO of the CompactLogix output tags will functionally update if used within your ControLogix application).
In order to Produce/Consume data between the two controllers, you will have to also edit the CompactLogix RSL5K application file by adding the ControlLogix system similarly to the way you have added the CompactLogix system to the ControLogix one.
Once the two systems could "see" each other you will have to create Produced Type Tags within the data originating controller tag database and identically spelled, of the same Size and Data Type Consumed Type Tags within the data arrival controller tag database.
This mechanism will transfer data from the Producing controller to the Consuming one at user defined RPI.