<hrw>
"sudo evtest" is listing it as input device but, as it comes with IR remotes, it has some weird key combos and does not react at all at random IR remote I found at home.
naoki has joined #linux-rockchip
<hrw>
I am considering removing it from my nanopc-t6 patchset as I am not sure does it work at all.
<naoki>
hrw: why?
<hrw>
naoki: personal preference
<hrw>
'do not enable things you cannot test'
crabbedhaloablut has quit []
crabbedhaloablut has joined #linux-rockchip
<naoki>
hmm
<hrw>
spi flash? fine. maskrom key? fine. usb 2.0/c? fine, gpu (even without outputs)? fine. first 3 are testable and work. gpu gets driver loaded as expected and does not require any pins.
<hrw>
ir-receiver is pinctl, gpio line and then when driver loads and input device is created then turns out to be harder to test
<hrw>
Bus 003 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
<hrw>
dsimic: low confidentiality rate. some vendors would put email address across all pages
<Kwiboo>
naoki: thanks for the note on zero-3 leds, please send a fix patch for zero-3 if you think it should use pwm-leds instead of gpio-leds
<Kwiboo>
hrw: I will test your nanopc-t6 series on a non-lts nanopc-t6 later, will also test if ir-receiver works
<dsimic>
hrw: basically, it can be considered public
<hrw>
Kwiboo: I looked at u-boot recently. Both variants of nanopc-t6 use 'board id' on saradc so it looks like code to follow other rockchip boards will be needed to find is it 2301 (non-lts) or 2310 (lts) version.
<hrw>
dsimic: it is in public space so it is public now
<hrw>
dsimic: seen too many slides at conferences with "CompanyName Confidential" left on bottom part of slide so seeing 'OtherCompanyName Confidential' across page feels like 'every normal day' ;D
<hrw>
Kwiboo: thanks
<hrw>
Kwiboo: "ir-keytable -v -t -p rc-5,rc-5-sz,jvc,sony,nec,sanyo,mce_kbd,rc-6,sharp,xmp" is what I used to test IR-receiver. It reacted to random remote
<naoki>
Kwiboo: zero-3? I think it was ROCK S0... anyway, I'll try to convert gpio-leds to pwm-leds, I'll send a patch for S0 too (I don't have it)
<naoki>
but probably it will be done after making ROCK 5C (Lite) DT
<dsimic>
hrw: frankly, I no longer even notice such banners :)
<Kwiboo>
naoki: hehe, you are correct it was s0 you mentioned and not zero-3 related to pwm-leds :)
<hrw>
dsimic: ;D
kevery1 has joined #linux-rockchip
naoki has quit [Ping timeout: 255 seconds]
kevery has quit [Ping timeout: 260 seconds]
kevery1 is now known as kevery
<hrw>
ok, let me try u0boot
<hrw>
s/0/-/
<hrw>
ok, looks like I need to remind myself how to properly build u-boot and read doc/board/rockchip/* again ;d
<hrw>
booted
naoki has joined #linux-rockchip
naoki has quit [Client Quit]
raster has quit [Quit: Gettin' stinky!]
<hrw>
hm. if I use nandwrite to write u-boot-rockchip-spi.bin then it fails to boot (stuck on 'out'). if write same file with 'upgrade_tool' then it boots.
<qschulz>
hrw: which SoC?
<hrw>
qschulz: rk3588
<qschulz>
hrw: i don't have devices with SPI flashes on RK3588... Maybe dump the NAND with nandwrite and upgrade_tool and see the difference?
<qschulz>
hrw: is nandwrite actually erasing the flash before writing?
<qschulz>
or do you need to run flasherase before?
<hrw>
qschulz: good point with that erase. will check
<Kwiboo>
if vref-supply is from pmic it may complicate things, or at least require more things in SPL, think I looked at changing code to get correct default 1v8 ref voltage at one point without having to have a valid regulator udevice
<Kwiboo>
suggest you base your code on zero3-rk3566.c instead, and ensure both models are listed in CONFIG_OF_LIST, that way you have correct control FDT in U-Boot and EFI boot
<hrw>
ok
<hrw>
uf. CMD_ADC helps
<dsimic>
Kwiboo: I'm wondering what are the actual benefits of such runtime detection?
<dsimic>
so there can be one U-Boot build for the two board variants?
<qschulz>
dsimic: same sdcard image for lts and non-lts
<hrw>
dsimic: LTS one has usb2 ports where user can plug install media or keyboard.
<Kwiboo>
hrw: be sure to read a single adc value using adc cmd, reading all may return a different value compared to single read for a channel, guessing some delay may be needed or similar when reading different channels
<hrw>
Kwiboo: ok
<Kwiboo>
especially channel 0 that typically is 1v8 and channel 1 is something different, it will return different value for channel 1 compared when reading a single value
<hrw>
Kwiboo: linux DT has spi2->pmic->regulators->avcc_1v8_s0
<Kwiboo>
hrw: you can probably include SPI + PMIC + rk8xx-regulator in SPL to get it working, but feel like is is a little bit unneccecery just to get the already known 1v8 ref value
<hrw>
I can rewrite that series in many ways but would like to get 2 opinions
<dsimic>
hrw: I can respond later, when I reach those messages in my overflowing inbox :)
<hrw>
Kwiboo: my knowledge of u-boot internals can be seen in git log - mostly small tweaks around rockpro64 config years ago
<hrw>
dsimic: thanks
<dsimic>
anytime :)
<diederik>
hrw: o/
<hrw>
diederik: \o
<dsimic>
:D
<dsimic>
different hands waved :)
<diederik>
lol, looks like aerc has some quirks (too ...)
<hrw>
dsimic: depends how you look at it. it could be left hand in both cases
<diederik>
dsimic: I'm actually used to the 'reply' being like that
<dsimic>
ah, I wasn't aware of all that :)
<dsimic>
hrw: sure, depends on the perspective :)
<Kwiboo>
hrw: I can take a look at using a fallback adc vref in u-boot at a later time, already looked into something similar 1-2 month ago, linux DT changes need to be merged before we can pick DT to u-boot, so guessing v2025.01 will be earliest target version
<hrw>
Kwiboo: to be honest I do u-boot part only because started the Linux part. Bought that board to have some physical system running edk2.
<hrw>
so will flash edk2 back and play in that sandbox
<hrw>
Kwiboo: and: thanks!
<diederik>
FTR: that aerc quirk is known and fixed already :-D Got a response to my question (on IRC) in 3 minutes :-O
paulk has quit [Ping timeout: 272 seconds]
paulk has joined #linux-rockchip
paulk has joined #linux-rockchip
psydroid has quit [Read error: Connection reset by peer]
psydroid has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
Stat_headcrabed has joined #linux-rockchip
Stat_headcrabed has quit [Quit: Stat_headcrabed]
dsimic has quit [Ping timeout: 265 seconds]
dsimic has joined #linux-rockchip
Stat_headcrabed has joined #linux-rockchip
Stat_headcrabed has quit [Quit: Stat_headcrabed]
Stat_headcrabed has joined #linux-rockchip
System_Error has quit [Remote host closed the connection]
warpme has quit [Remote host closed the connection]
warpme has joined #linux-rockchip
System_Error has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]