10:02 <sicelo> btw, might be of *some* interest to fmg, uvos, and Wizzup : there's this https://lore.kernel.org/linux-input/ZkKQoTq2xyNvJlHE@google.com/T/#t

10:03 <sicelo> phosh people are behind it ... but who knows ... maybe as we support more devices, might be useful for us too

10:03 <Wizzup> yeah I am not quite sure how this should work from kernel side either

10:04 <sicelo> i must confess i haven't followed it much myself ...

10:06 <sicelo> it might not be about kernel itself ... but more for kernel to report that *this* particular key is a wakeup (or non-wakeup) key

10:07 <Wizzup> oh, I was thinking that this would not emit certain keys when inhibited or something

10:07 <Wizzup> I guess that doesn't make sense

10:08 <sicelo> then userspace takes appropriate action (e.g. unblanking, or refusing to unblank). i think the idea here is that for different phones, you might want key X to wake you up, but on another one, the same key should not wake you up

10:08 <Wizzup> *shrug* I guess

10:08 <Wizzup> I mean isn't it obvious that the volume keys should not wake up the device

10:08 <sicelo> :-P

10:08 <sicelo> for maemo it's obvious

10:09 <sicelo> but think of the way things are for many other phones ... the phone will suspend to ram after a while

10:09 <Wizzup> well it seems to be like the keys should still wake up the device, then it can decide how to handle it

10:10 <sicelo> yes it's an interesting problem, i guess.

10:13 <Wizzup> yeah I think we've got it solved for us for now at least

10:38 <sicelo> i think this is where it all started - https://gitlab.gnome.org/World/Phosh/phoc/-/issues/363

10:38 <sicelo> so those capacitive keys don't (wouldn't) cause wakeups for us currently?

10:44 <Wizzup> that is right, we disable the ts

10:46 <sicelo> yes. i think the keys are a 'second' ts, or something? there was something to that effect i seem to recal

10:49 <sicelo> anyway for d4, i think the problem was handled in the driver for those keys, specific to mapphones. iiuc, this patch is basically handling the same problem, but (hopefully?) in a generic way

10:53 <Wizzup> the second ts is an unrelated issue though

10:53 <Wizzup> as in not related to this

13:00 <sicelo> been a bit stuck on a few IRL stuff and didn't have time for L5 ... hope to get back to it soon

13:07 <sicelo> so if your debian packaging contains: debian/patches/*.patch, the build stuff knows to automatically apply all of them before build starts? or you need some instruction?

13:15 <Wizzup> I think you also need debian/patches/series but I always find that a real PITA so I try to avoid it personally

13:17 <sicelo> ah, ok