<narmstrong_>
ok yeah they use 2 pwms to get a more precise pwm output
<warpme_>
narmstrong_: clocking entries were suggested by radxa team (i used radxa work on initial armbian boot)....
<narmstrong_>
I see nothing special on clocking
<warpme_>
narmstrong_: in android dt is see pwr_reg_on approach while in mainlinux we have sdio pwrseq approach. Isn't difference that: req_on is 1 binary change (off->on) - like power supply turning on. pwrseq is however short activation of reset line. shouldn't we use reg_on (like in android)? At end there should be no difference but.... (btw: i already tested with change reset-gpios from GPIO_ACTIVE_LOW to GPIO_ACTIVE_HIGH:
<warpme_>
with high driver not seeing chip at all)
Stricted- is now known as Stricted
<warpme_>
narmstrong_: btw: i REALLY surprised how well this board works. h264 decoder works well (it fails for me only on 2160p h264; this is contrary to sm1 which fails an many samples). hevc however works partially (some samples makes it hang). If hevc will be fixed - i would say g12 is useable soc for linux media player...
Ballerburg9005 has quit [Ping timeout: 240 seconds]
Ballerbu1g9005 has joined #linux-amlogic
Ballerbu1g9005 has quit [Ping timeout: 250 seconds]
Ballerburg9005 has joined #linux-amlogic
<narmstrong_>
warpme_: the pwrseq alway worked up to now, but the errors you encounter really reminds me what amlogic,dram-access-quirk solved