As you've found, attaching devices to buses created by extra overlays is trickier than doing so for the standard interfaces.
You can export labels as detailed in https://www.raspberrypi.com/documentati ... ml#part2.3, but making use of them is still slightly awkward. i believe the best route is to use "target-path" instead of target, which stops it having to find the label when trying to load the overlay. ads1115-overlay.dts looks to be a reasonable example of that for i2c3-6 (which only exist on a Pi4 or 5).
You do then have an issue of generating unique labels for each interface if you want more than one i2c mux, so at some point it is simplest to give up and write your own overlay.
You can export labels as detailed in https://www.raspberrypi.com/documentati ... ml#part2.3, but making use of them is still slightly awkward. i believe the best route is to use "target-path" instead of target, which stops it having to find the label when trying to load the overlay. ads1115-overlay.dts looks to be a reasonable example of that for i2c3-6 (which only exist on a Pi4 or 5).
You do then have an issue of generating unique labels for each interface if you want more than one i2c mux, so at some point it is simplest to give up and write your own overlay.
Statistics: Posted by 6by9 — Tue Apr 16, 2024 9:31 am
