Device Tree • Re: How to select a device tree on the basis of GPIOs?

Coming back to this thread after doing some basic testing.

Test environment:

• 4B
• Bookworm lite
• Ciseco PiLITEr (small board with 8 LEds)
• Stock confing.tx with the following added at the end:

  Code:

  [all]# GPIO setupgpio=4=op,dlgpio=17=op,dlgpio=18=op,dlgpio=22=op,dlgpio=23=op,dlgpio=24=op,dlgpio=25=op,dlgpio=27=op,dlgpio=5=ip,pugpio=6=ip,pugpio=13=ip,pugpio=16=ip,pugpio=19=ip,pugpio=21=ip,pu#gpio filter tests[gpio5=1]gpio=4=op,dh[all][gpio6=1]gpio=17=op,dh[all][gpio13=1]gpio27=op,dh[gpio21=1]gpio=18=op,dh[all][gpio16=1]gpio27=op,dh[gpio19=0]gpio=18=op,dh[all]

Results:

• LEDs 1 and 2 light so multiple GPIO filters are possible as long as filters are reset with [all] between them.
• LED 3 does not light, LED 4 does. Last one wins when criteria for that filter are met.
• LEDs 5 and 6 do not light. Last one wins when its criteria are not met.

Conclusion:
Multiple GPIO filters can be activate in the same cofig.txt as long as the current filter is reset with [all] before the next one. If more than one filter is present without [all] between them last one wins regardless of whether its criteria are met or not.

Aside:
I wonder if the behaviour is the same with other overlapping but mutually exclusive filters ([pi4] and [cm4] for example)

Statistics: Posted by thagrol — Sat Jul 06, 2024 2:54 pm

---