c0rnelius | figured out why the led isn't working on rev 1.5. they moved it from gpio 8 to 10. | 15:40 |
---|---|---|
c0rnelius | steev | 15:40 |
steev | c0rnelius: oooh | 20:37 |
steev | well that is... frustrating | 20:38 |
c0rnelius | Yeah. I created a hack in the dts to support it but it's not pretty. | 20:39 |
c0rnelius | It's whatever though. I just care that it works. | 20:39 |
steev | btw, in case you see it in yours on 5.17+ - https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=314d8cd2787418c5ac6b02035c344644f47b292b gets rid of the bluetooth unexpected event spam | 20:42 |
c0rnelius | Thanx for the heads up. | 20:44 |
steev | i'm assuming because of the Fixes tag, it'll go in to 5.17 once it's stable at some point | 20:45 |
steev | ah, i see what you did, yeah, it's definitely not pretty | 21:02 |
c0rnelius | I was trying to think of another way but everything else I tried wasn't working. | 21:04 |
c0rnelius | It doesn't hurt anything it's just kind of stupid :) | 21:06 |
steev | i've asked in #linux-amlogic will see if theres any kinda response | 21:06 |
c0rnelius | k | 21:07 |
steev | i'm assuming that u-boot doesn't differentiate between them either | 21:07 |
steev | between being a 1.4 and a 1.51 | 21:07 |
c0rnelius | no led in the u-boot dts | 21:08 |
c0rnelius | I tried adding it but it didn't help | 21:08 |
steev | nah, it'd have to be the same as linux | 21:08 |
steev | i was just wondering if u-boot differentiated between it being a 1.4 and a 1.5 | 21:08 |
c0rnelius | no it doesn't | 21:08 |
steev | like it does with, some other devices | 21:08 |
c0rnelius | would be nice if it did | 21:11 |
c0rnelius | i original tried <&gpio_ao GPIOAO_8 GPIO_ACTIVE_HIGH>, <&gpio_ao GPIOAO_10 GPIO_ACTIVE_HIGH>; but that was a no go. | 21:16 |
c0rnelius | wait a sec maybe that does work. | 21:26 |
c0rnelius | nah only picks up the 8. | 21:30 |
steev | https://dl.radxa.com/zero/docs/hw/Radxa_Zero_sch_v1.4_20210709.pdf | 21:44 |
steev | er | 21:44 |
steev | xdarklight> steev: https://dl.radxa.com/zero/docs/hw/Radxa_Zero_sch_v1.4_20210709.pdf - page 4 mentions that ADC_CH1 is used for HW_ID | 21:44 |
steev | would probably require patching u-boot too, but could probably poke that to figure out which HW_ID we have | 21:44 |
steev | and then we could have a second dts with just that change in it | 21:45 |
c0rnelius | I'll check it out. | 21:48 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!