robclark changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
<_[m]123> ah that s because I changed to highger frequency but so no more external screen ☚ī¸ tried 6.7 and 6.8
<_[m]123> works again hmpf
hightower3 has joined #aarch64-laptops
hightower4 has quit [Ping timeout: 480 seconds]
<konradybcio> enjoy
schaeffer has quit [Ping timeout: 480 seconds]
f_ has quit [Read error: Connection reset by peer]
f_ has joined #aarch64-laptops
jglathe_volterra has quit [Remote host closed the connection]
iivanov has quit [Quit: Leaving...]
jglathe_volterra has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
ungeskriptet has quit [Quit: The Lounge - https://thelounge.chat]
ungeskriptet has joined #aarch64-laptops
ungeskriptet has quit [Quit: The Lounge - https://thelounge.chat]
martiert has joined #aarch64-laptops
matthias_bgg has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
ungeskriptet has joined #aarch64-laptops
<jglathe_> :grin:
Caterpillar has quit [Ping timeout: 480 seconds]
KREYREN_oftc has joined #aarch64-laptops
ungeskriptet has quit [Quit: The Lounge - https://thelounge.chat]
ungeskriptet has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
<agl> Which kernel parameter are neccessary to switch on IOxx_DMA_LAZY ?
<agl> for the USB ports
<agl> s/parameter/parameters/
<agl> on the x13s
<jhovold> agl: you don't need to do that anymore
<jhovold> but if you still want to do it, it's "iommu.passthrough=0 iommu.strict=0"
<agl> I need it for my ACASIS-BOX. I have it to do in the .config of linux-x13s of x13s-alarm, and then it works.
<agl> jhovold: Thanks :)
<agl> THE ACASIS-Box with a SSD and some ports seems a little bit difficult.
alpernebbi has joined #aarch64-laptops
<agl> jhovold: I see it works WITHOUT ..._DMA_LAZY or without the iommu.... parameters! I have tried this!
alpernebbi has quit []
alpernebbi has joined #aarch64-laptops
alpernebbi has quit []
alpernebbi has joined #aarch64-laptops
<jhovold> agl: as I said, you don't need it anymore since the underlying issue was fixed
<bamse> jhovold: i was about to resubmit the touchscreen patches...but realized that i was on the wrong path...
<bamse> jhovold: as i was extending the binding and the driver, i stumbled upon i2c-hid-of-elan.c
<bamse> jhovold: so we apparently have the generic driver that doesn't allow us to set that one timeout, and then we have a elan-specific driver...
<bamse> jhovold: so, if we could just figure out what elan-chip we actually have...
<jhovold> bamse: heh, nice find, looks just like what we need :)
<bamse> no idea why there are two drivers doing essentially the same thing...
<bamse> jhovold: didn't you or someone over there have schematics for the "display" as well? or could you ping someone who has that information?
<jhovold> bamse: i don't have it but I think I know someone who does, i'll check
f_ is now known as funderscore
funderscore is now known as f_
<jhovold> bamse: there was no product string tobe found in windows?
<jhovold> oh, and did you notice that pmic_glink device links errors are gone in rc5?
<bamse> jhovold: i have not rebooted yet
<jhovold> saravanna apparently finally got around to fixing that
<bamse> nice, i didn't notice
baspar[m] has quit [Ping timeout: 480 seconds]
Nao[m] has quit [Ping timeout: 480 seconds]
<bamse> in -rc5...
<bamse> sounds like a -rc1 change
<jhovold> yeah, what could go wrong, right?
<jhovold> still, i'm down to essentially a single error in the log after boot now (sound driver)
baspar[m] has joined #aarch64-laptops
Nao[m] has joined #aarch64-laptops
<jhovold> and the bluetooth frame reassembly error every other boot
<bamse> the timeout from the sound driver?
<jhovold> right
<jhovold> a reminder that that needs to fixed at some point
<bamse> yeah...and i need to figure out how to reproduce that other issue, with pmic_glink not coming up as well
todi has joined #aarch64-laptops
<jhovold> bamse: nothing in the schematics, but I'll see what I can find out from Lenovo
<jenneron[m]> bamse: which timeout? just curious
<jhovold> and lumag looked for a product name in Windows, without any luck there either
<jenneron[m]> i2c-hid-of has got some new bindings recently which allowed me to make it working on flex 5g
<jhovold> jenneron[m]: we need a delay after deasserting the touchscreen reset at boot
<jhovold> it's not actually in the bindings yet, but yeah, the driver know how to handle it now
<jenneron[m]> i see
<jhovold> the thing is, such details should not be in the devicetree
<jhovold> but rather in the driver, based on the compatible string
<jenneron[m]> that's if you know the IC..
<jenneron[m]> unlike my case with flex 5g
<jhovold> so know we need to figure out a name for the Elan device with product id 0x901c
<jhovold> can't you find a pid in the dsdt there too?
<jenneron[m]> evtest reports bus 0x18 vendor 0x4f3 product 0x2a7d version 0x100
<jhovold> so that's Elan too IIUC
<jenneron[m]> yeah it is elan
<jenneron[m]> DSDT: Name (_HID, "ELAN901C")
<jhovold> or maybe I'm reading this wrong, and 901c is the product name?
<bamse> jenneron[m]: i noticed that as i reviewed your(?) patches, but wanted to figure out the path forward...
<jhovold> the X13s dsdt have the same string for the touchscreen, not sure about the pid anymore
<jhovold> bamse: can you check dmesg?
<bamse> it wouldn't be totally crazy if it's the same touchscreen on both
<bamse> jhovold: "msdu_done bit in attention is not set" :)
<bamse> jhovold: what do you want me to check? if there's anything useful in the logs identifying the touchscreen?
<jhovold> bamse: tell that to kalle, he's not seeing that warning: https://bugzilla.kernel.org/show_bug.cgi?id=218005
<jhovold> there should be a pid in there somewhere
<jhovold> dmesg | grep HID should tell
<bamse> i'm back on my clean upstream kernel....let's see if i can do the sysfs dance
<jenneron[m]> jhovold: i'm not sure what you asked me to look at, but here's the dsdt https://raw.githubusercontent.com/aarch64-laptops/build/master/misc/lenovo-flex-5g/dsdt.dsl
<jenneron[m]> touchscreen is Device (TSC1)
<bamse> jhovold: [342566.707605] hid-multitouch 0018:04F3:2FE6.0003: input: I2C HID v1.00 Device [hid-over-i2c 04F3:2FE6] on 4-0010
<jenneron[m]> nah it's not the same touchscreen at least
<jhovold> so different PID than jenneron[m]: 0x2FE6 vs 0x2a7d
<jhovold> guess that string in the dsdt doesn't mean much
<bamse> right
<jhovold> bamse: but judging from that bugzilla entry, that ath11k spam message depends on which network the reporter is connected too
<jhovold> and I've never seen it here (or elsewhere)
<bamse> jhovold: i'm not surprised, i have it on all my ath11k-devices
<_[m]123> sending my x13s with fedex to poland (for free) to replace my touchpad 🤞
<_[m]123> they said, the ssd is a user replacable item and doens't void the warranty 🎉
<bamse> nice
<_[m]123> I'll cheer when they actually replace it
<bamse> jhovold: fun stuff, speedtest.net over wifi gives me 3mbps down and 293mbps up today again...
<bamse> jhovold: numbers consistent with iperf3 towards my local machine...not sure what's up
<jhovold> bamse: I have 513 down 523 up Mbit/s just now with my 6.8-rc5 wip branch
<jhovold> but I did notice that I only got 50 Mbit/s in one direction sometimes when doing the PCIe work this last few weeks
<jhovold> a reboot helped so possibly another firmware regression in the January 15 release (i.e. .36)
<bamse> how do i check which version i'm on?
<jhovold> dmesg | grep LITE-3
<jhovold> as you run arch, I assume we both run .36
<jhovold> WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36
<jhovold> heh, forgot to disconnect the USB-C ethernet, the wifi numbers are 473/523 Mbits/s (down/up)
<bamse> jhovold: yeah, got .36 here as well
<Dylanger> jenneron: I successfully expanded Kernel Partition 1 via deleting the 2nd Kernel partition, now I have a 64MB kernel partition and I got to leave my user LUKs partition alone 😎
<Dylanger> Gonna look into grabbing Fedora's Kernel and packaging it into a depthcharge compatible kernel image, then SELinux should work
<bamse> jhovold: perhaps we could just propose elan,<pid> as compatibles for those touchscreens?
hightower4 has joined #aarch64-laptops
hightower3 has quit [Ping timeout: 480 seconds]
matthias_bgg has quit [Quit: Leaving]
jglathe_ has quit [Remote host closed the connection]
jglathe_x13s has joined #aarch64-laptops
<jglathe_x13s> on 6.8-rc5 now, yay the pmic_glink errors are gone
Mary has quit [Quit: The Lounge - https://thelounge.chat]
Mary has joined #aarch64-laptops
Mary has quit []
Mary has joined #aarch64-laptops
hightower3 has joined #aarch64-laptops
hightower4 has quit [Ping timeout: 480 seconds]
hightower4 has joined #aarch64-laptops
cyrinux3 has joined #aarch64-laptops
cyrinux has quit [Ping timeout: 480 seconds]
hightower3 has quit [Ping timeout: 480 seconds]
cyrinux3 has quit []
cyrinux3 has joined #aarch64-laptops
hightower3 has joined #aarch64-laptops
hightower4 has quit [Read error: Connection reset by peer]