00:19 <steev> javierm: okay, yeah, leaving it at default or setting to 10 (which as you mention is the default), seems to *sometimes* boot correctly; setting it to 30 is always booting correctly (at least wrt display)

00:43 <steev> additionally... i seem to be missing thermal zones 11, 12 and 13, which is odd

08:14 <javierm> steev: yeah, here 10 secs seems to always lead to a timeout in some cases while 30 secs always work

09:10 <javierm> steev: your email is steev at kali dot org, right?

10:44 <javierm> steev: I've cc'ed you on a patch

11:03 <juergh> javierm, which timeout is that?

11:13 <javierm> juergh: driver_deferred_probe_timeout

11:29 <javierm> steev: it would be great if you can chime in and mention that also have the same issue, because gregkh is pushing back my patch...

14:57 <steev> javierm: sorry, was asleep will do after my meeting

14:57 <steev> but yes that's my email :)

14:59 <javierm> steev: no worries. It seems gregkh feels strong about not reverting to the old (not time bound) probe deferral behavior, and that the arbitrary 10 secs timeout is an improvement...

15:00 <javierm> steev: so I may just built-in CONFIG_SC_GPUCC_7180 in the fedora kernel

15:01 <steev> i don't think that will fix it

15:01 <steev> i have 8280XP =y in my config and run into the issue here on the x13s so

15:03 <javierm> steev: interesting. Because IIUC the problem here was "adreno_smmu: iommu@5040000" DT node failing to probe with -110 due "gpucc: clock-controller@5090000" not bound with the gpucc-sc7180 clk driver

15:04 <javierm> but with the timeout increased to 30 secs, that probe failed with -517 and eventually probed once the gpucc-sc7180 module was loaded / clk driver registered

15:04 <javierm> steev: in any case and regardless of our issues, I believe that changing the probe deferral behaviour was just wrong and the default should be to keep probing

15:05 <javierm> steev: I don't know about kali, but at least in fedora we build as much as possible as a module and try to only have the modules actually needed to mount the rootfs in the initrd

15:06 <javierm> all the rest are in the rootfs

15:06 <steev> kali does the same (pretty much) as debian

15:06 <javierm> steev: which is the same than fedora right?

15:06 <javierm> I mean, all these are general purpose distros anyways

15:06 <steev> roughly, yeah, i think y'all do compressed modules/firmware and debian doesnt'

15:06 <javierm> steev: yeah, we do

15:09 <javierm> steev: so it would be great if you can give your opinion on that thread too then. Because even if we fix our config for this particular issue to not happey, it will bite us in other platforms again

15:09 <javierm> *happen

15:17 <steev> good news, meeting was canceled, grabbing coffee and then i will

15:20 <javierm> steev: meeting canceled is always good news :)

16:21 <steev> javierm: on your chromebook, do you have many thermal zones? (> 10 ?)

16:21 <steev> on 6.0.8, i have 13, however, on 6.1-rcX, I'm only seeing up to 10

16:22 <steev> which is kinda bad because we use 12 for the thermal throttling

16:23 <steev> i guess technically it's 14 zones total, but only see 11 zones on 6.1 and all 14 on 6.0

16:27 <javierm> steev: hmm, I'm seeing 29 thermal zones with 6.1-rc4

16:27 <javierm> ls -d /sys/class/thermal/thermal_zone* | wc -l

16:27 <javierm> 28

16:27 <steev> okay

16:27 <steev> so it's something on my end then :)

16:28 <javierm> Ok

16:28 <javierm> steev: thanks for answering to the thread btw

16:35 <steev> no problem :)

16:35 <steev> i want to see it fixed as the multigen lru stuff is in 6.1 and i'd like to use it asap

18:22 <bamse> jenneron[m]: the battery support on sc8180x is based on qcom pmic(s) and exposed using "pmic_glink" - as steev linked to

18:24 <bamse> jenneron[m]: vkoul was looking at audio for sc8180x, but had some issues with soundwire iirc...

18:25 <steev> jenneron[m]: oh, also of note, you do need the pd-mapper and such services

18:27 <steev> oooh, next got a lot of goodies in :) down to ~75 patches on top of next

18:29 <bamse> steev: "and such services", aren't we don't to just pd-mapper?

18:29 <steev> yeah, but iirc, it still "depends" on the others

18:31 <steev> oh, i guess it just deps on qrtr-ns still

18:34 <steev> jenneron[m]: so you need at least qrtr-ns and pd-mapper to use the battery

18:34 <steev> though qrtr-ns does absolutely nothing because it's in the kernel now

18:35 <steev> bamse: maybe a new release of pd-mapper that doesn't dep on it? or maybe a branch for stuff that is > $ancient-kerels

18:59 <steev> bamse: jhovold: have either of you tried to boot -next recently? 20221111 and newer just immediately reboot here after leaving efi services

19:34 <jenneron[m]> t's better to tell that to mothenjoyer69 since he tests battery

19:34 <jenneron[m]> i have a branch https://gitlab.com/jenneron/linux/-/commits/galaxy-book-s-6.0.6-battery, but it doesn't work for him

21:01 <bamse> steev: i have not

21:07 <Leandro[m]> so uh which devices are currently being worked on by this group?

21:08 <steev> c630, flex5g, thinkpad x13s, galaxybook go, galaxybook2, some chromebooks but i never pay attention to those so not sure which

21:08 <Leandro[m]> hmm

21:08 <Leandro[m]> still got my eyes on galaxy book go but lets see what i can find here

21:11 <Leandro[m]> anyone got a list of the chromebooks?

21:11 <Leandro[m]> so far the galaxy book go is the most affordable it seems

21:12 <steev> chromebook spin? seems to come to mind

21:12 <steev> not sure

21:12 <Leandro[m]> like, acer chromebook spin xyz?

21:14 <steev> something along those lines

21:14 <steev> SC7180 or some such is the snapdragon chipset used

21:14 <Leandro[m]> what about mt8183, jenneron keeps trying to get me to buy a device with that

21:14 <Leandro[m]> lmao

21:25 <aceridus> Leandro[m]: Walmart has the Lenovo IdeaPad 3 with that SoC on sale for $99 right now

21:25 <HdkR> Leandro[m]: Do you want a working device, or one that isn't to tinker on? :P

21:25 <Leandro[m]> yes

21:26 <Leandro[m]> aceridus: damn if only i were from US

21:27 <aceridus> Leandro[m]: Do they not ship to where you are?

21:27 <Leandro[m]> i dont think they ship to germany

21:27 <Leandro[m]> even if they do, its probably going to be expensive

21:28 <aceridus> https://www.walmart.com/ip/Lenovo-IdeaPad-3-Chrome-14M836-14-HD-Laptop-MediaTek-MT8183-4GB-LPDDR4X-ARM-Mali-G72-MP3-64GB-eMMC-Chrome-OS-Abyss-Blue-82KN002GUS/1182249616

21:28 <aceridus> Worth a look, it might still be a good deal even with International shipping.

21:29 <Leandro[m]> doesnt look like they ship outside US

21:29 <Leandro[m]> and i dont really want to hire some import company

21:30 <aceridus> I can certainly use more help on the GBG though. I feel like I am in over my head when it comes to the remaining hardware...

21:31 <Leandro[m]> ok so either galaxy book go, Acer Chromebook spin 311 or that one Lenovo IdeaPad Duet

21:31 <aceridus> The touchpad might be the next easiest thing to figure out, but when it comes to WiFi and the memory regions and mbn firmware loading I am lost

21:32 <Leandro[m]> latter 2 are interesting because pen support, gbg is interesting cuz qcom and woa

21:34 <aceridus> My dreams suggested the best way to find the vdd gpio for the touchpad might just be to try exporting them all to user space and then set them to output with the correct active state. Not sure if that would work, but if so it may require reloading the driver or writing something to the sysfs bind file of the driver.

21:35 <Leandro[m]> * pen support(and price), gbg

21:35 <Leandro[m]> aceridus: jenneron what do you think about my small list

21:40 <aceridus> Leandro[m]: I have the Duet. It is a nice device in a small 10" tablet form factor, but hard to use extensively because of the size and the keyboard being cramped

21:40 <Leandro[m]> welp given how im used to small keyboards, that shouldnt be an issue

21:46 <aceridus> Leandro[m]: Are you referring to the Lenovo Chromebook Duet with the Helio P60T?

21:46 <steev> bamse: speaking of battery.... every so often (i think i've seen it twice, overall) the battery just reports 0%, modprobe -r/modprobe cycle doesn't do anything

21:46 <Leandro[m]> aceridus: seems like it

21:46 <Leandro[m]> ct-X636F

21:47 <aceridus> Leandro[m]: Yea, that is the one I have. I would get the Spin 311, the extra size of an 11.6" device will be nicer

22:05 <Leandro[m]> i must say i love the form factor of the surface go, is the lenovo thing simillar? aceridus

22:11 <aceridus> Leandro[m]: I would say yes. The Duet is a tablet on its own. The back cover attaches magnetically and has a kickstand, but can be removed for the thinnest and lightest tablet experience. The keyboard attaches magnetically via pogo pins. All three pieces together act as a case for the tablet. It is a very nice design overall, it is just the size can be prohibitive to long productivity sessions. It is great for media consumption though.

22:12 <steev> im in the minority that absolutely cannot stand kickstands

22:12 <aceridus> I have not had a chance to use a Surface Go though, so I am speaking from comparing based on the Surface webpage

22:15 <aceridus> steev: Yea, it is serviceable as long as you have a hard surface to setup on, but a useless design if you want to use it while lying in bed and need to type, for example.

22:16 <swgws> using a surface tablet without a hard surface is a specialized skill

22:18 <Leandro[m]> my lap take it or leave it

22:19 <Leandro[m]> at least on the modern surfaces the kickstand is fully adjustable, on my rt its either open or closed

22:19 <aceridus> That is the Achilles' heel of the convertible tablet form factor. It is an exercise in futility to try to use those things on your lap or while lying in bed.

22:21 <Leandro[m]> true

22:53 <hexdump0815> Leandro[m]: mt8183 chromebooks are boring in case you want to help bringing them forward as nearly everything is working well on them meanwhile including suspend etc. - but they are maybe the best choice as a cheap useable aarch64 laptop

22:54 <hexdump0815> Leandro[m]: galaxy book go would be nice to help getting it forward

23:25 <aceridus> hexdump0815: Not sure if you saw this yet, but I made a small patch that gets rid of the flood of descriptor messages at boot on the galaxy book go: https://oftc.irclog.whitequark.org/aarch64-laptops/2022-11-02#31586419

23:27 <aceridus> I don't know if it is a correct solution or not. It feels a bit like it is fixing a symptom instead of the actual problem. The hard coded VID/PID are certainly not an acceptable long term patch if it happens to be a relevant fix for the hardware...

23:28 <hexdump0815> aceridus: oh - thanks for the pointer - looks like i overlooked this one - even if not final, its a least better than all that log spam

23:29 <aceridus> I say that because although it gets rid of the messages at boot it doesn't handle the bus arbitration issue that pops up eventually, at least on my own image.

23:30 <aceridus> You actually only need the top line from my patch since the second line was only there for me to verify the quirk was being applied correctly (it took a handful of attempts to get it to work, so the dev_info message was useful)