Pali has quit [Ping timeout: 268 seconds]
kvw_5 has joined #maemo-leste
kvw_5_ has quit [Ping timeout: 240 seconds]
cockroach has quit [Quit: leaving]
_blasty`_ has quit [Ping timeout: 246 seconds]
pere has quit [Ping timeout: 246 seconds]
RedW has quit [Ping timeout: 246 seconds]
RedW has joined #maemo-leste
pere has joined #maemo-leste
_blasty` has joined #maemo-leste
belcher has quit [Ping timeout: 252 seconds]
belcher has joined #maemo-leste
t_rex has quit [Ping timeout: 260 seconds]
t_rex has joined #maemo-leste
ikmaak has quit [Ping timeout: 252 seconds]
ikmaak has joined #maemo-leste
mp107 has quit [Quit: The Lounge - https://thelounge.chat]
mp107 has joined #maemo-leste
<kek> clort81 opened an issue: https://github.com/maemo-leste-extras/desktop-cmd-exec/issues/1 (Excellent. Maybe we can document here or on wiki.)
pere has quit [Ping timeout: 240 seconds]
Pali has joined #maemo-leste
pere has joined #maemo-leste
blitzaxt[m] has quit [Quit: Idle for 30+ days]
<tmlind> siceloa, freemangordon: fyi, found a gpio regression that might affect n900 issues you guys have been seeing: https://lore.kernel.org/linux-omap/20210415085305.56413-1-tony@atomide.com/T/#u
<Entitlement> tmlind - [ [PATCH] gpio: omap: Save and restore sysconfig ]
<siceloa> I was just looking at that
* sicelo doesn't understand this stuff so much, haha, but, is this for PM? does it affect us while we don't have PM working on N900 yet?
<sicelo> i genuinely wish i could make PM work, even if it's only 50% efficients
<sicelo> otherwise, gpio issue i noticed on N900 is with lp5523 driver (for keyboard LEDs and RGB) - the gpio for this chip is never set HIGH, so chip never gets enabled. i sent a patch to the LED maintainers and still waiting for feedback.
<tmlind> sicelo: yeah this would be only with pm enabled
<tmlind> sicelo: can happen easily during the boot while drivers are loading, so if a gpio bank is only partially working, weird things can happen
* sicelo should do something about that serial for N900 ... otherwise we'll be left too far behind, and end up with lots of regressions, and useless device :)
<tmlind> sicelo: presumably these gpio issues started happening with commit fb2c599f0566 ("ARM: omap3: enable off mode automatically")
<sicelo> i see. but off mode isn't automatically enabled still? at least with 5.12-rc6, /sys/kernel/debug/pm_debug/enable_off_mode was initially 0
<tmlind> sicelo: hmm it should be, you still need to idle the uarts though for any deeper idle modes to start triggering
<sicelo> i'll test it again
<tmlind> ok
<sicelo> in fact i can boot 5.12-rc6 right away :)
<sicelo> there was some bandgap/eocz stuff you discussed with fmg in the recent past, which i seem to think you mentioned could also have an effect on entering some of the idle levels. i'll check logs and see if any of that makes a difference/improvement for me
<tmlind> yeah the bandgap fixes all are in v5.12-rc series already
<parazyd> sicelo: btw thanks for investigating the dnsmasq configuration, will save me some time :)
<tmlind> sicelo: but please apply that gpio patch as the gpio banks can get messed up during init
<sicelo> tmlind: sure. i'll do that later today, with -rc7
<sicelo> parazyd: yw. how does the pp name its cellular data interface? wwan as well, or?
<tmlind> sicelo: ok thanks
<parazyd> Yea I believe so
<sicelo> tmlind: any suggested way for me to check if the patch works?
<sicelo> 5.12-rc6 dmesg is here, https://paste.ubuntu.com/p/2HwSd8H9b2/ for reference
<Entitlement> sicelo - [ Ubuntu Pastebin ]
<tmlind> sicelo: yeah see the droid4-pm script on detaching serial console and idling uarts
<tmlind> sicelo: then disconnect usb and blank the lcd, and five seconds later do sudo cat /sys/kernel/debug/pm_debug/count and look at the core domain ret and off numbers
<sicelo> sure
<tmlind> unfortunately off number won't increase much with current kernels as there are way too many timers happening :(
<sicelo> i said earlier that enable_off_mode was initially 0 ... so you're right, it's 1 as i've just booted up
uvos has joined #maemo-leste
<sicelo> tmlind: i just briefly looked at the droi4-pm script. the are some registers/addresses read via devmem. i guess those come from the TRM? just tried one of them on N900 and naturally got core dumped :p
<sicelo> "Address Hole seen by MPU at address 4a009540"
<sicelo> i guess i'll need to find those registers in 3430 TRM? Wizzup did talk about registers here, https://github.com/maemo-leste/bugtracker/issues/317 , but didn't get time to document which ones
<Entitlement> sicelo - [ N900 and Droid 4 power management · Issue #317 · maemo-leste/bugtracker · GitHub ]
<sicelo> tmlind: a slightly different question - i have some changes for N900 dts. which ML would i send a patch to? linux-omap maybe?
<Wizzup> sicelo: I have n900 script for you
<tmlind> sicelo: yeah you can add parsing for 34xx regs, there's really only two regs on 34xx to look at
<Wizzup> n900-pm
<Wizzup> (I'll need to find it.)
<sicelo> thanks Wizzup. please ping when you've found it :)
<uvos> why are we not including n900-pm on leste yet? at least for devel, even if it dosent allow the device to idle yet.
<sicelo> on GH it's empty for now, at least last i checked
<sicelo> so can't be included ;)
<uvos> also what devices are blocking idle/ what dose omapconf audit have to say on n900
<tmlind> sicelo: you need to look at cm_idlest_per cm_idlest1_core regs, the bits are inverted i recall
<sicelo> have to find them ... will check
<sicelo> uvos: i don't know yet about devices blocking idle, and hopefully the registers help. omapconf i'll build and see what it reports
<sicelo> i still have to build for the gpio patch too.
<uvos> sicelo: ok just cuourious, i thought wizzup might know
<tmlind> sicelo: looking at those two regs pretty much tells you what is blocking
<tmlind> some bits need to be ignored, they always block
<uvos> omapconf reads the same thing + some more stats and formats it nice
<uvos> btwe
<tmlind> yeah ok
<sicelo> nice - but i must first find their addresses, or they're already somehow accessible /sys perhaps?
<tmlind> you can find the addresses by searching the trm for the soc, then read them with devm or rwmem
<tmlind> busybox devmem
<sicelo> cool. i have the trm. will check later
<tmlind> sicelo: start with a minimal kernel with as few drivers loaded as possible
<tmlind> sicelo: omap2plus_defconfig built kernel idles on omap3 just fine for me as tested with minimal modules and nfsroot
<tmlind> and has been for years and years
<Wizzup> sicelo: looks like I made an empty repo for it a while ago ... https://github.com/maemo-leste/n900-pm
<Entitlement> Wizzup - [ maemo-leste/n900-pm · GitHub ]
<Wizzup> sicelo: you read this right? https://leste.maemo.org/Nokia_N900#Power_Management
<Entitlement> Wizzup - [ Nokia N900 - Maemo Leste Wiki ]
<sicelo> tmlind: oh, nice! maybe it's the wl1251 (which is not in omap2plus). but i'll take out more of the modules
<sicelo> Wizzup: yes, i have seen it. now i'm not sure if i tried it, but will do again
<Wizzup> At least running the python script should help
<Wizzup> (tell you what might be blocking)
<Wizzup> (You need to change `inp` to the value that is reported)
<Wizzup> Still looking for my n900-pm script, not sure if I can find it atm, might just be on a n900 at home (I am not home)
<sicelo> sure. no rush - i'm also not in position to do a lot atm
<sicelo> '00000000001000001000000001000010' this is the `inp`, for example?
<sicelo> besides that number, it returned "ST_SDRC
<sicelo> ST_OMAPCTRL
<sicelo> ST_I2C1
<sicelo> ST_MCSPI4"
<sicelo> so that's nice, i guess - at least something's working
<Wizzup> sicelo: I think you enter it as hex
<Wizzup> You might be able to use hex(int(valuehere, 2))
<sicelo> looks like no value is reported (for me to change to). that binary number = inp
<Wizzup> but iirc you're looking for:
<Wizzup> 00001fff 48005020 (584be965) cm_idlest_per blocking bits: 0007e000
<Wizzup> f7df3fb9 48004a20 (b32988a8) cm_idlest1_core blocking bits: 0020c046
<Wizzup> what kind of info
<Wizzup> and I think that requires an extra patch
<sicelo> ok. yes i'm not getting that output. what i sent above is the only output from the python script
<Wizzup> from tmlind
<Wizzup> not sure if it applies on latetst
<Wizzup> latest*
<sicelo> i'll give it a try too ;)
<uvos> parazyd: you can updatedroid4-wlanconfig from upstream https://github.com/IMbackK/droid4-wlanconfig
<Entitlement> uvos - [ GitHub - IMbackK/droid4-wlanconfig ]
<parazyd> ok
<uvos> parazyd: to fix the issue on newer kernels wrt mounting pds
<parazyd> Should it immediately go to main or just devel?
<uvos> immediate since the old version is broken in main right now
<Wizzup> sicelo: you need that patch to debug off mode issues iirc
<parazyd> ack
<Wizzup> at least it should make it much less like opaque
<sicelo> it doesn't apply. but will look into it more closely
<Wizzup> It's a small patch, so it might not be too hard to fix
<siceloa> yes
<siceloa> uvos: looks like omapconf is for omap4 and higher
<uvos> siceloa: theres a old version
<uvos> for omap3
<uvos> iirc
<uvos> let me look for it
<Entitlement> uvos - [ Omapconf support for DM37xx - Processors forum - Processors - TI E2E support for... ]
<uvos> maybe not
<uvos> :(
<uvos> wierd since i thought AM335x is more or less an omap3. i gues not
<tmlind> am335x is cortex-a8 with omap4 interconnects and ethernet integrated with tilcd instead of omapdrm, quite similar to ti81xx
inky has quit [Ping timeout: 240 seconds]
inky has joined #maemo-leste
pere has quit [Ping timeout: 252 seconds]
inky has quit [Ping timeout: 268 seconds]
inky has joined #maemo-leste
inky has quit [Ping timeout: 265 seconds]
pere has joined #maemo-leste
inky has joined #maemo-leste
<Wizzup> (test)
<Wizzup> nvm
inky has quit [Ping timeout: 252 seconds]
inky has joined #maemo-leste
t_rex has quit [Ping timeout: 260 seconds]
inky has quit [Ping timeout: 240 seconds]
inky has joined #maemo-leste
t_rex has joined #maemo-leste
t_rex has quit [Ping timeout: 240 seconds]
t_rex has joined #maemo-leste
inky has quit [Ping timeout: 252 seconds]
inky has joined #maemo-leste
jonsger has joined #maemo-leste
inky has quit [Ping timeout: 265 seconds]
inky has joined #maemo-leste
vanjski has joined #maemo-leste
inky has quit [Ping timeout: 240 seconds]
vanjski has quit [Quit: Connection closed]
inky has joined #maemo-leste
pagurus has joined #maemo-leste
jonsger has quit [Ping timeout: 240 seconds]
sunshavi has quit [Remote host closed the connection]
sunshavi has joined #maemo-leste
ikmaak has quit [Ping timeout: 252 seconds]
ikmaak has joined #maemo-leste
Oksana has joined #maemo-leste
uvos has quit [Remote host closed the connection]