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)
<jenneron[m]>
aceridus: can you push your kernel changes for galaxy book go somewhere?
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
SSJ_GZ has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
iivanov__ has joined #aarch64-laptops
iivanov has quit [Read error: Connection reset by peer]
matthias_bgg has joined #aarch64-laptops
Penguinpee has quit [Remote host closed the connection]
Penguinpee has joined #aarch64-laptops
<abelvesa>
steev: I intend to resend that soon
<abelvesa>
it kinda got ignored the first time
<steev>
yeah, mostly :( hopefully round two will be better, and i'll definitely test it :)
<ajhalaney[m]>
steev: Finally got around to looking at why that 6.0.3 tag failed to boot for me. pmic_glink got deferred, and it oops'ed, and somehow that made the display unhappy (unsure of the relationship there to be honest). This commit[0] on my branch[1] (which enables a few configs needed for fedora) makes things kosher again:
<ajhalaney[m]>
I may have failed to push it up lemme double check that bit just made that update (when I tried that in the past I failed to boot, turns out it was that pmic_glink oops all along)
<steev>
ajhalaney[m]: oh good to know, i'll pull in too
<steev>
(eventually)
<ajhalaney[m]>
javierm: thanks, guess who forgot to git add and amend? :D The links are all still good though, but not the laptop_defconfig changes are actually present. And awesome thanks steev
<ajhalaney[m]>
s/not/now/ jeez.
<javierm>
ajhalaney[m]: cool. I think you also need CONFIG_FW_LOADER_COMPRESS_XZ=y ?
<steev>
ajhalaney[m]: i *think* [0] should go to the list? not sure if the glink stuff has already gone in
<ajhalaney[m]>
steev: I'll follow up and see if jhovold already covered it in the review with bamse.. I think that patch series is still under review but I'll add to my to-do list today so it doesn't sneak away from us
<ajhalaney[m]>
javierm that's set when you do a `make laptop_defconfig` (default y in Kconfig)
<javierm>
ajhalaney[m]: yeah, but having it will save you to choose each time
<ajhalaney[m]>
javierm long term me/Brian/Eric hope to have a kernel-ark based branch with configs and stuff ready to rock but I haven't spent the time yet to do that
<steev>
this is joke, i habitually cat when i don't need to too
<javierm>
ajhalaney[m]: ah! I see that the default y is fairly recent, commit 07953c54a105 ("firmware_loader: enable XZ by default if compressed support is enabled")
<ajhalaney[m]>
javierm: I appreciate you looking out regardless :)
<javierm>
ajhalaney[m]: I wondered why I had to choose on my v5.18 branch :)
matthias_bgg has quit [Ping timeout: 480 seconds]
jhovold has quit [Ping timeout: 480 seconds]
matthias_bgg has joined #aarch64-laptops
aceridus has joined #aarch64-laptops
iivanov__ has quit [Quit: Leaving...]
<Leandro[m]>
<jenneron[m]> "aceridus: can you push your..." <- Would be epic
<aceridus>
jenneron[m]: Leandro[m]: Update from over the weekend is that I tried the 4 gpio configurations for the touchpad vdd (31 high, 31 low, 32 high, 32 low). None produced a working touchpad. It maybe a fluke or not relevant at all but when set to 32 active high I sometimes see dmesg lines related to i2c-10 setup failing. Current dst: https://dpaste.com/DL4DT62UT
<aceridus>
Leandro[m]: I am happy to hear someone else wants to jump onboard and help with the same machine. I bought one off ebay recently simply because I knew it didn't work fully with Linux yet and figured it would be a good attempt at understanding device tree more. I am very much not a kernel or DT developer, but I can sort of find my way around them at a novice level...
<Leandro[m]>
I'm probably not much better than you lol
<Leandro[m]>
But now I have an excuse to get a cheap not-17" laptop
<aceridus>
Leandro[m]: Let's figure it out together then once you get your hands on one. I have a fairly streamlined process where I rebuild the kernel/dts/rootfs in an LXD container and then move it over to a USB thumb drive. I am happy to share the bootable image if you want to get you kickstarted
<aceridus>
jenneron[m]: Leandro[m]: The keyboard works, but periodically dmesg gets flooded with 'geni_i2c a80000.i2c: Bus arbitration lost, clock line undriveable' messages. Possibly due to inactivity? dmesg: https://dpaste.com/H75F5PG84
<aceridus>
jenneron[m]: Leandro[m]: Here is a dmesg log when touchpad is set to GPIO 32 active-high and gets i2c_hid_of 10-0040 errors related to failing to change power settings and failing to reset the device. Not sure if this means I am on the correct pin, or maybe it means I am on the wrong pin? https://dpaste.com/3BD368AKD
matthias_bgg has quit [Ping timeout: 480 seconds]
hexdump01 has quit [Quit: WeeChat 1.9.1]
hexdump0815 has joined #aarch64-laptops
<aceridus>
It is also worth noting that I don't always see the i2c_hid_of 10-0040 errors, it seems more often than not I don't see any messages related to i2c_hid_of 10-0040
<hexdump0815>
oh i think i was wrong I2C8 seems to be something else
<hexdump0815>
the other hid protocol device seems to be IC11 in the dsdt which maps to i2c10, so looks like that one is correct ... please forget what i mentioned before :)
<aceridus>
Yea, I think the added complexity for the touchpad is it has an external regulator that needs to be enabled. I am working off of jenneron's recommendations and examples, so I don't know that I am getting the vdd regulator gpio correct...
SSJ_GZ has quit [Ping timeout: 480 seconds]
<jenneron[m]>
I would hardcode this power sequence in hid over i2c driver
<jenneron[m]>
to test
<jenneron[m]>
also please push your changes so it will be easier to look at it