Open digitalLumberjack opened 11 months ago
dtoverlay=i2c1
(the -pi5
is implied there, and will be in the Linux utlity once the change rolls out) works as expected. Applying overlays at runtime has never been a priority, but for the I2C subsystem it ought to work. Your rewrite is a good one, and if I was starting from scratch that's probably what I would have ended up with.
I'll take a look at the dtoverlay
command and how it is failing, but until then I suggest you carry on with your modified overlay or letting the firmware do the application
I think you'll find that while your modified overlay works for pins_2_3, parameter pins_10_11 does nothing when using the dtoverlay command (not the config.txt directive, for anyone else reading). Fixing both styles of overlay should be possible but non-trivial.
A potential fix for these problems can be found here: https://github.com/raspberrypi/utils/pull/54
Describe the bug
Hello.
On commit 392b9849c8d147c25557fea5d6dbcddbcb9e72d5
Trying to load the dtbo
i2c1-pi5
on pi5:will lead to the following error:
Steps to reproduce the behaviour
dtoverlay i2c1-pi5
Device (s)
Other
System
Recalbox 9.2 alpha
Logs
Additional context
It seems to be related to the
target = <&frag0>;
ini2c1-pi5-overlay.dts
.Using the i2c1 target in fragments fix the issue, but may I suggest using the same pattern for i2c0 and i2c1 than the
i2c2-pi5-overlay.dts
, that also fix the issue.Thank you for the hard work on pi5 hardware and kernel/mesa support, it runs almost flawlessly!