ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi has joined #aarch64-laptops
jonasbits has quit [Ping timeout: 480 seconds]
jonasbits has joined #aarch64-laptops
<steev>
bamse: i'm showing 9 patches on top of next at this point; the 4 patches for the battery, my disable crypto unit patch, the cpufreq max freqency patches (2), and then 2 wcd934x patches
<steev>
you probably have 3 for the battery (or even 2 if you don't bother having the one that gives a rougher guesstimate)
<bamse>
steev: didn't we fix the cryto crash?
<steev>
if we did, i wasn't aware?
<steev>
i definitely wasn't tagged in anything to test
<steev>
(or it was while i was on vacation and not at all paying attention to my email)
<bamse>
i think we set out to do something about it...but i honestly don't remember if we reached the goal line on that one
<steev>
i know *i* didn't, because my commit message for the disable specifically says someone way smarter than me needs to come along and fix it
<steev>
tis exciting to see the backlight control in next :D
<steev>
want me to hit the mailing list and mention it has gone missing?
<bamse>
i have the crypto patch in arm64-fixes-for-5.16, but it looks like i forgot to send a pull request on that one(?)
<steev>
oops
<steev>
5.17 works too :D
<steev>
maz: what's your setup for your c630? i've suspended and resumed a few times here and no issues. running kali (debian testing), gnome on wayland
<steev>
i'm also using clk_ignore_unused on the kernel command line (the only extra option aside from quiet splash
<bamse>
steev: yeah...clk_ignore_unused and pd_ignore_unused are required...and will remain so
<steev>
oh, i'm not using pd_ignore_unused
<bamse>
steev: hmm..maybe things works without that(?)
<bamse>
but clocks doesn't work..by design
<bamse>
added the crypto patch to the 5.17-fixes branch, will give is a spin in linux-next and then send out a PR for that
<bamse>
dianders: thanks for the pointer, i'll keep looking the other way...at least for a while longer
<steev>
i can very easily ignore errors :D except the one maz experiences, which i've experienced in the past, but not recently
<bamse>
the lockup?
<steev>
yeah, the dpu encoder timeout
<steev>
i tried going through my logs to pull out the conversations i had with abnihav and lumag about it yesterday but gave up as i needed to focus on our release, but that's out now, so maybe soon i'll go back through them
<robclark>
hmm, not sure if that gdsc patch landed already.. but it is a timing thing, so even before there was some element of luck about whether you'd hit it
<bamse>
robclark: stephen and i had some feedback and questions on the gdsc patch, but i haven't seen any follow up after that
<robclark>
right.. doug poked them on the internal bug y'day about reposting a v2
<steev>
gdsc has not landed iirc
<steev>
maz: hm, okay, let me flip to using gnome on xorg and see if i can reproduce it faster
<maz>
steev: one thing the machine screams about is the lack of ipa_fws.mdt firmware. no idea where to find that one.
<steev>
on the windows partition
<steev>
that's the modem firmware (or you can disable the ipa module)
<maz>
steev: right. I don't think I'll ever care about that, so happy to disable it.
<steev>
./scripts/config --disable QCOM_IPA
<steev>
or you can just blacklist it from loading
<maz>
the latter. I like compiling things! ;-)
<bamse>
maz: screams repeatedly? or screams once?
<maz>
bamse: just once.
<bamse>
okay good
<bamse>
so just cover your eyes at the right moment and you're good :)
<maz>
oh, I've become really good at turning a blind eye at so many things... ;-)
<bamse>
just wanted to confirm, because we've had other cases where it just won't stop complaining (not ipa...)
<bamse>
yeah, there's a little bit too much of that still...hopefully we can improve the base state at least, so you only get the upstream "regressions"
<bamse>
but on the other hand, i find it really useful to actually be running upstream and find those regressions
<bamse>
and i like that you do it as well maz :)
<maz>
;-)
SallyAhaj has joined #aarch64-laptops
iivanov has quit []
Lucanis has quit [Ping timeout: 480 seconds]
jonasbits has quit [Ping timeout: 480 seconds]
hightower3 has joined #aarch64-laptops
hightower3 has quit [Read error: Connection reset by peer]