10:26 <naoki> Kwiboo: https://github.com/radxa/u-boot/commit/fc2c80b7f35faa283afc871fc23b3f2f5589ec44 there is (extremely dirty) patch to detect board type and override dtb file name for Radxa ZERO 3E/3W

10:27 <naoki> will you consider this method in your patch set? or should I fix it later? ;)

10:36 <qschulz> naoki: Are you 100% sure that the ADC value are those ones? We have some channels oscillating around a number

10:37 <qschulz> naoki: sorry, cannot read properly it seems

10:37 <naoki> that commit was made by Radxa

10:39 <naoki> probably I'll make some changes not to abuse evb_rk3568

10:39 <naoki> (when I will send it to mainline u-boot)

10:40 <naoki> macromorgan already did it similar one

10:41 <robmur01> abusing a MAC address hook seems pretty yuck too... :)

10:45 <qschulz> naoki: look what board/anbernic/rgxx3_rk3566/rgxx3-rk3566.c is doing, that is probably a more suitable hook function?

11:04 <naoki> qschulz: I think so

15:44 <tarel2> Do any of you know the registers for the blue led on the pine phone pro ?

15:45 <CounterPillow> there isn't a single register for the LED, you'll have to set GPIO muxes and then the GPIO

15:54 <CounterPillow> If you're trying to do this from userspace, use the actual kernel your OS has to abstract this away from you and simply toggle the LED through the sysfs or what have you.

17:47 <tarel2> I have only programmed the pi and pico microcontroller.  What is gpio muxes?

18:08 <CounterPillow> functions can be assigned to different pins depending on what the pin mux is set to.

18:09 <CounterPillow> If you are not writing a low level tiny boot blob, you should not be touching the registers to blink an LED, but use the existing abstractions implemented by the drivers.

18:11 <tarel2> I know you don't have to do such .   I have been programming my raspberry pi pico microcontroller in arm 32 bit assembly and got my pi blinking led with the help of the firmware and making a small bare metal app so I thought why not try the phone.

18:13 <tarel2> any maybe one day help with the power management so I can switch to the pine phone pro all the time.

18:15 <tarel2> My Android device are the last not running Linux

18:15 <CounterPillow> Ok, then grab the RK3399 TRM from http://opensource.rock-chips.com/ and the PinePhone Pro schematics from Pine's website and check which pin is hooked up to the LED, and then check the GRF section of the TRM for the pinmux setting registers and the GPIO section for how the GPIO controller works

18:17 <tarel2> so you had to look at the schematics and the datasheet of the cpu to figure out , what the gpio is?

18:40 <CounterPillow> Yes?

18:41 <CounterPillow> If you want to know which registers to poke at in the SoC, the technical reference manual is the resource to consult

18:43 <tarel2> I looked for while I did not find that page

18:43 <CounterPillow> What page?

18:44 <tarel2> https://opensource.rock-chips.com/wiki_Main_Page

18:45 <CounterPillow> Okay?

18:46 <tarel2> The pine64 official page for the cpu  those files are not all there

18:46 <tarel2> haha never been so happy to see offsets in my life

18:47 <CounterPillow> You should edit that page then and improve it instead of complaining to a random IRC channel unaffiliated with pine64

18:48 <tarel2> I was not complaining , I was just stating .

18:49 <tarel2> If you work on the Linux code great job

18:49 <tarel2> I love my pine phone pro

18:54 <tarel2> really  I can't tell how great a job the kernel people do .   After working a bit with soc ,  its not easy.