narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
sputnik has quit [Ping timeout: 268 seconds]
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 258 seconds]
vagrantc has quit [Ping timeout: 245 seconds]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 240 seconds]
hipboi has joined #linux-amlogic
camus has quit [Ping timeout: 255 seconds]
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-amlogic
camus has joined #linux-amlogic
hipboi_ has joined #linux-amlogic
hipboi has quit [Ping timeout: 276 seconds]
hipboi_ has quit [Remote host closed the connection]
hipboi has joined #linux-amlogic
camus has quit [Ping timeout: 276 seconds]
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-amlogic
hipboi has quit [Ping timeout: 265 seconds]
sputnik has joined #linux-amlogic
sputnik has quit [Remote host closed the connection]
sputnik has joined #linux-amlogic
camus has joined #linux-amlogic
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 245 seconds]
camus1 is now known as camus
camus has quit [Ping timeout: 250 seconds]
hipboi has joined #linux-amlogic
camus has joined #linux-amlogic
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 245 seconds]
camus1 is now known as camus
hipboi has quit [Ping timeout: 245 seconds]
hipboi has joined #linux-amlogic
Stricted has quit [*.net *.split]
Stricted- has joined #linux-amlogic
cyrozap has quit [*.net *.split]
cyrozap has joined #linux-amlogic
hipboi has quit [Ping timeout: 240 seconds]
camus has quit [Quit: camus]
camus has joined #linux-amlogic
hipboi has joined #linux-amlogic
camus has quit [Read error: Connection reset by peer]
camus1 has joined #linux-amlogic
camus1 is now known as camus
hipboi has quit [Ping timeout: 268 seconds]
vagrantc has joined #linux-amlogic
hipboi has joined #linux-amlogic
vagrantc has quit [Client Quit]
hipboi has quit [Ping timeout: 245 seconds]
hipboi has joined #linux-amlogic
camus1 has joined #linux-amlogic
camus has quit [Read error: Connection reset by peer]
camus1 is now known as camus
cmeerw has joined #linux-amlogic
cmeerw has quit [Ping timeout: 276 seconds]
camus has quit [Quit: camus]
camus has joined #linux-amlogic
Lyude has quit [Quit: WeeChat 3.0.1]
Lyude has joined #linux-amlogic
warpme_ has joined #linux-amlogic
repk has joined #linux-amlogic
<narmstrong_> warpme_: make sure you have amlogic,dram-access-quirk in the sdio node
<narmstrong_> warpme_: what base dtsi are you using ?
<warpme_> narmstrong_: i added dram-access-quirk. no better :-(. Here is DT i'm using: https://pastebin.com/yHAb6gn3
<warpme_> narmstrong_: btw: i received link to android kernel radxa uses for radza-zero. comparing with mainline linux dt for other boards with ap6256 (i.e. rockpi-4b) i see difference in clocking: mainline kernel: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi?h=v5.13.5#n32 radxa android kernel:
<narmstrong_> the pwm_channel2_conf is weird
<warpme_> narmstrong_: just fyi (if you not get sch for radxa: https://dl.radxa.com/zero/docs/hw/ )
<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
camus has quit [Quit: camus]
<warpme_> narmstrong_: with above commit reverted:
<warpme_> :-)
<narmstrong_> :-/
sputnik has quit [Ping timeout: 240 seconds]
buzzmarshall has joined #linux-amlogic
cmeerw has joined #linux-amlogic
sputnik has joined #linux-amlogic
sputnik has quit [Ping timeout: 255 seconds]
sputnik has joined #linux-amlogic
<Ballerburg9005> 4<<:q
cmeerw has quit [Ping timeout: 268 seconds]
vagrantc has joined #linux-amlogic
warpme_ has quit [Quit: Connection closed for inactivity]
elastic_dog has quit [Ping timeout: 252 seconds]
sputnik has quit [Ping timeout: 256 seconds]
elastic_dog has joined #linux-amlogic