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)
mcbridematt has quit [Quit: Leaving]
mcbridematt has joined #aarch64-laptops
<steev> bamse: so, i did more ~~playing around~~testing, and yeah, with the dp enabled, the c630 just doesn't like to wake the display up from resume. so i added a slight hack to disable it for the moment - this is what i'm testing now - https://github.com/steev/linux/tree/c630-6.0.0-rc5-only-batt
<steev> also tried just vanilla 6.0.0-rc5, and it boots fine and shows the no audio issue, so it's nothing from any of the stuff i was applying on top, so that's.... goodishly bad
<bamse> steev: okay, i will hook mine up to an external display and play around with it some more
<clover[m]> jhovold: with this userspace fix (https://github.com/szclsya/x13s-alarm/pull/6/files), touchscreen@10 seems to be found but doesn't know how to describe it.... (full message at <https://matrix.org/_matrix/media/r0/download/matrix.org/JWpOiBdKncVWwoToHDYMRmhW>)
<clover[m]> * found but linux doesn't know
<bamse> clover[m]: you mean linux finds a device, but still doesn't think there's a hid device there?
<bamse> or more than that?
<clover[m]> well everything works, it just doesnt say "Touch Screen" like it does with all of the "working" hid-over-i2c devices
<clover[m]> it says "UNKNOWN"
<clover[m]> bamse: without the udev rule, linux finds the i2c device but wont automatically load it as an hid-over-i2c device
<clover[m]> maybe the driver only loads i2c-0 devices and neglects to load ic2-1, no clue
<clover[m]> s/ic2/i2c/
<steev> clover[m]: that *shouldn't* be the case, because the c630 has devices on i2c-3, i2c-5, and i2c-11
<bamse> it's rather the case that there would be some relation between the two, which we haven't modelled
<steev> same "fix" works here on mine too bamse, so apparently they sent me a touchscreen version
<bamse> :)
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
<steev> bamse: does c630 have dpu_hw_600
<bamse> computer says 400 and/or 401
<steev> ah, so it's not even in the DPU_HW_VER stuff
<steev> oh, that's md5 stuff
<bamse> DPU_HW_VER_400
<steev> i'm in the wrong file :)
<bamse> at the end of dpu_hw_catalog.c
<steev> i was looking in msm_mdss.c :)
iivanov has joined #aarch64-laptops
iivanov has quit []
iivanov has joined #aarch64-laptops
iivanov__ has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
<steev> hmm
<steev> audio works on next (c630) so... wtf fixes it
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
iivanov__ has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
iivanov has quit [Quit: Leaving...]
gwolf has joined #aarch64-laptops
<jhovold> steev: that NULL-deref is expected unless you drop dmitry's series first
<steev> jhovold: ah, okay, i thought as much, but wasn't sure
<jhovold> clover[m]: interesting. But you shouldn't need any udev rule like that. We should root cause why it doesn't bind without it.
<HdkR> Why Gen2? :|
<mahmoudajawad[m]> Don't know. Maybe because it was engineered before gen 3 becomes available?
<mahmoudajawad[m]> Do we have any specs to show what performance difference are there between gen 2 and 3?
flowriser has quit [Ping timeout: 480 seconds]
derzahl has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
Penguinpee_ is now known as Penguinpee
hexdump01 has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
derzahl has joined #aarch64-laptops
derzahl has quit [Ping timeout: 480 seconds]
<clover[m]> Thus is kinda cool though. There are not many arm linux tablets available
mcbridematt has quit [Remote host closed the connection]
<robclark> HdkR: I don't think any 7c3 thing shipping yet
derzahl has joined #aarch64-laptops
kbingham has joined #aarch64-laptops
kbingham has quit []
kbingham has joined #aarch64-laptops
<clover[m]> Leo Shen: Any update on what we can do to protect battery on X13s?
_whitelogger has joined #aarch64-laptops
<szclsya[m]> nothing yet
minecrell8 has quit []
minecrell has joined #aarch64-laptops
<szclsya[m]> usually there're something like "charging_threshold" in the power supply sysfs, but there isn't any in x13s's
<szclsya[m]> also the windows app also doesn't contain such functionality, so the ec probably doesn't support it at all
<szclsya[m]> https://github.com/VR-25/acc/blob/dev/install/ctrl-files.sh here's a list of charging control apis on android. but since we are using an open source driver our's is different (and unfortunately doesn't contain charging control apis
<clover[m]> i know they were able to tweak the kernel for the pinephone to get charging control
<szclsya[m]> I *think* it should be supported by the soc (hey they can do it on a mobile chip, and the sc8280xp is basically a beefed up 865, no reason to remove such functionality eh
<clover[m]> i do see a /sys/class/power_supply/qcom-battmgr-bat/voltage_max_design on the x13s
<clover[m]> > $ cat /sys/class/power_supply/qcom-battmgr-bat/voltage_now
<clover[m]> 7946000
<clover[m]> I am at 42%, someone better at math tell me what the voltage is at 100% lol
<szclsya[m]> all the properties in x13s's sysfs are ro though. not sure if that would work
<clover[m]> ah, odd
luxio_39[m] has quit [Write error: connection closed]
mahmoudajawad[m] has quit [Write error: connection closed]
fevv8[m] has quit [Write error: connection closed]
jenneron[m] has quit [Write error: connection closed]
ungeskriptet[m] has quit [Write error: connection closed]
travmurav[m] has quit [Write error: connection closed]
frytaped[m] has quit [Write error: connection closed]
Lucy[m] has quit [Write error: connection closed]
qzed has quit [Write error: connection closed]
harvestz[m] has quit [Write error: connection closed]
robertmader[m] has quit [Write error: connection closed]
Dylanger has quit [Write error: connection closed]
harvests[m] has quit [Write error: connection closed]
Sobek[m] has quit [Write error: connection closed]
testing has quit [Write error: connection closed]
steevdave[m] has quit [Write error: connection closed]
danielt has quit [Write error: connection closed]
davidebeatrici[m] has quit [Write error: connection closed]
AlexMarty[m] has quit [Write error: connection closed]
clover[m] has quit [Write error: connection closed]
amstan has quit [Write error: connection closed]
Manis[m] has quit [Write error: connection closed]
mothenjoyer69 has quit [Write error: connection closed]
szclsya[m] has quit [Remote host closed the connection]
ajhalaney[m] has quit [Write error: connection closed]
clover[m] has joined #aarch64-laptops
<clover[m]> so the driver for the axp20x allows the sysfs to be writable, but the qcom-battmgr-bat thing that the x13s uses doesnt?
abc123bac2[m] has joined #aarch64-laptops
abc123bac2[m] has quit [Remote host closed the connection]
clover[m] has quit [Remote host closed the connection]
abc123bac2[m] has joined #aarch64-laptops
clover[m] has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
ajhalaney[m] has joined #aarch64-laptops
arisu has joined #aarch64-laptops
AlexMarty[m] has joined #aarch64-laptops
amstan has joined #aarch64-laptops
cmeerw[m] has joined #aarch64-laptops
danielt has joined #aarch64-laptops
davidebeatrici[m] has joined #aarch64-laptops
Dylanger has joined #aarch64-laptops
fevv8[m] has joined #aarch64-laptops
frytaped[m] has joined #aarch64-laptops
testing has joined #aarch64-laptops
harvests[m] has joined #aarch64-laptops
harvestz[m] has joined #aarch64-laptops
szclsya[m] has joined #aarch64-laptops
jenneron[m] has joined #aarch64-laptops
Lucy[m] has joined #aarch64-laptops
luxio_39[m] has joined #aarch64-laptops
mahmoudajawad[m] has joined #aarch64-laptops
Manis[m] has joined #aarch64-laptops
mothenjoyer69 has joined #aarch64-laptops
psydroid[m] has joined #aarch64-laptops
Guest422 has joined #aarch64-laptops
robertmader[m] has joined #aarch64-laptops
Sobek[m] has joined #aarch64-laptops
steevdave[m] has joined #aarch64-laptops
underpantsgnome[m] has joined #aarch64-laptops
travmurav[m] has joined #aarch64-laptops
ungeskriptet[m] has joined #aarch64-laptops