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
Lyude has joined #linux-amlogic
hexdump0815 has quit [Ping timeout: 252 seconds]
hexdump0815 has joined #linux-amlogic
konsgn has quit [Read error: Connection reset by peer]
konsgn has joined #linux-amlogic
paulk has quit [Ping timeout: 272 seconds]
paulk has joined #linux-amlogic
paulk has joined #linux-amlogic
chewitt has joined #linux-amlogic
Lyude has quit [Ping timeout: 260 seconds]
paulk has quit [Ping timeout: 265 seconds]
paulk has joined #linux-amlogic
paulk has joined #linux-amlogic
jacobk_ has joined #linux-amlogic
jacobk has quit [Ping timeout: 276 seconds]
chewitt has quit [Quit: Zzz..]
<lvrp16> anyone have the g12a datasheet? there's a bug for the spicc clk_sel due to missing clocks. I want to make sure g12a and g12b are the same before I send the patch
<lvrp16> it was causing all the wrong clock issues.
<lvrp16> went from 4 fps to 21 fps on my testing spi display
<xdarklight> lvrp16: I don't have a reliable datasheet. if you have a board with that SoC, set the SPI clock and then compare /sys/kernel/debug/clk/clk_summary with /sys/kernel/debug/meson-clk-msr/measure_summary
<lvrp16> xdarklight: wait, clock measure works?
<lvrp16> when who where
<xdarklight> basically since it was upstreamed a few years ago. I've been just recently using it to diagnose clock problems
zsoltiv_ has joined #linux-amlogic
<lvrp16> for gxbb through g12? :O here I'm still measuring with a scope haha
<lvrp16> I'm trying to get 200MHz and 333MHz SPI working atm
<lvrp16> tuning all these delays. I wish I had a 400MHz scope.