14:53 <steev> 5.15 is out

18:19 <steev> audio is broken for me but i think it's the weird pulseaudio changes not kernel side

22:18 <bamse> steev: so the reason why the touchpad stops working is that libinput relates it to the SW_LID...which we seem to not always (or even rarely) get the falling interrupt for

22:18 <steev> that is... very weird

22:18 <bamse> steev: so libinput is convinced that the lid is still closed...

22:23 <steev> is it a bug in libinput then? i don't even know how to find the SW_LID since we're not acpi

22:36 <bamse> steev: it's a gpio-keys, just registering an irq handler on gpio 124

22:37 <steev> ah, that one

22:38 <steev> would be nice if we could actually label it a lid switch, so end users can see it

22:38 <bamse> looking at the gpio state it's low, but running evtest tells me that SW_LID is high

22:39 <bamse> it's named "lid"

22:39 <bamse> but it's exposed to userspace as gpio-keys...with SW_LID and SW_TABLET_MODE exposed

22:39 <steev> https://pastebin.com/TEQdwAF8

22:40 <steev> i kinda mean the name since the other stuff has names

22:40 <steev> N: Name="hid-over-i2c 6243:0001 Keyboard"

22:40 <steev> as an example

22:40 <bamse> ahh, not sure what we should name it...unless we create one per thing

22:40 <bamse> well i do believe it's actually gpio signals from the EC

22:54 <steev> so ec driver coming soon? :P

23:12 <bamse> well, robert merged the backlight series into drm-misc-next (or whatever that branch is called)

23:13 <bamse> so the only thing left in my tree would then be the battery driver...so it would certainly be nice to come up with an acceptable design for that

23:16 <steev> :D

23:16 <steev> wait, the backlight part of the dts or just the driver portion

23:17 <bamse> he picked the driver portion, i've yet to send the dts patches again

23:17 <bamse> and it doesn't seem like it's perculated up to linux-next yet, so i presume we'll get that after the merge window

23:18 <steev> ah dang, was hoping 5.16 would be "good enough"

23:18 <steev> i'm hoping lumag is able to track down that clk rcg issue

23:18 <steev> that patch he provided does help quite a bit

23:19 <steev> and the guy who is bm16ton emailed me on friday, he asked about the blue screen as well, i haven't replied to him yet

23:26 <bamse> i wasn't sure the two issues where related...but looking at the log where i just got it seems quite likely

23:58 <steev> it started in 5.12 but was *extremely* rare, 5.13 became more common