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 - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
nsaenz has joined #linux-amlogic
nsaenz has quit [Remote host closed the connection]
Darkmatter66 has joined #linux-amlogic
Darkmatter66_ has quit [Ping timeout: 240 seconds]
_whitelogger has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
Darkmatter66_ has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 272 seconds]
_whitelogger has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
<xdarklight> chewitt: too bad :/
<chewitt> is the "5f6c6d61ffffffff" value = 50ºC or was that just a lucky guess?
<xdarklight> it was a lucky guess unfortunately :/
<xdarklight> chewitt: hmm, another random guess: can you enable the SAR ADC node (&saradc) on your board like it's done here: https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/amlogic/meson-gxl-s905x-p212.dtsi (note: you may have to copy the vddio_ao18 over as well)?
<xdarklight> maybe Linux is disabling the ADC clock and now u-boot (who uses the ADC to read the temperature) gets only garbage
Darkmatter66 has joined #linux-amlogic
Darkmatter66_ has quit [Ping timeout: 272 seconds]
afaerber has quit [Remote host closed the connection]
afaerber has joined #linux-amlogic
drieschel has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
drieschel has quit [Quit: drieschel]
sputnik_ has quit [Remote host closed the connection]
<chewitt> xdarklight: I'll have a play once kids are in bed, thanks
return0e has quit [Ping timeout: 252 seconds]
return0e has joined #linux-amlogic
<chewitt> HUB:~ # cat /sys/class/hwmon/hwmon0/temp1_input
<chewitt> 50000
<chewitt> so that's a beer I owe you :)
<chewitt> the next item on my list is figuring out why these boxes can't see the cpu serial
<chewitt> on all the GXL devices I have "cat /sys/bus/platform/devices/firmware\:secure-monitor/serial" shows the serial
<chewitt> on these two GXBB device I see "cat: read error: Invalid argument"
<chewitt> as most Android boxes don't have MAC addresses set, I'm using a simple systemd service to create a persistent MAC from the CPU serial
<chewitt> but this isn't possible on these boxes
<chewitt> and I'm not sure if this is something specific to these two (WeTek Hub/Play 2) or all GXBB devices
warpme_ has joined #linux-amlogic
<xdarklight> chewitt: sweet :)
<xdarklight> chewitt: are you running mainline or -next ?
<chewitt> mainline
<chewitt> as much as the bleeding edge can be interesting.. it's also hard work
<chewitt> i'll test without last night's patch later .. if it's just the missing saradc node etc. I'll send a patch to add it to the wetek dtsi
<xdarklight> ah, Jerome added the correct clock for the efuse driver
<xdarklight> and you're missing the serial from the secure-monitor
<xdarklight> so these probably aren't related
<xdarklight> but maybe it's one of these: https://github.com/torvalds/linux/commit/d6ee1e7e9004d3d246cdfa14196989e0a9466c16 (just another random guess...)
warpme_ has quit [Quit: warpme_]
warpme_ has joined #linux-amlogic
warpme_ has quit [Quit: warpme_]