Re: [PATCH v4 0/7] Support inhibiting input devices

[Hans de Goede]

Hi,

On 6/10/20 8:28 PM, Dmitry Torokhov wrote:
> On Wed, Jun 10, 2020 at 12:38:30PM +0200, Rafael J. Wysocki wrote:
> > On Wed, Jun 10, 2020 at 11:50 AM Hans de Goede <hdegoede@xxxxxxxxxx> wrote:
> > > Hi All,
> > >
> > > On 6/8/20 1:22 PM, Andrzej Pietrasiewicz wrote:
> > > > This is a quick respin of v3, with just two small changes, please see
> > > > the changelog below.
> > > >
> > > > Userspace might want to implement a policy to temporarily disregard input
> > > > from certain devices.
> > > >
> > > > An example use case is a convertible laptop, whose keyboard can be folded
> > > > under the screen to create tablet-like experience. The user then must hold
> > > > the laptop in such a way that it is difficult to avoid pressing the keyboard
> > > > keys. It is therefore desirable to temporarily disregard input from the
> > > > keyboard, until it is folded back. This obviously is a policy which should
> > > > be kept out of the kernel, but the kernel must provide suitable means to
> > > > implement such a policy.
> > >
> > > First of all sorry to start a somewhat new discussion about this
> > > while this patch set is also somewhat far along in the review process,
> > > but I believe what I discuss below needs to be taken into account.
> > >
> > > Yesterday I have been looking into why an Asus T101HA would not stay
> > > suspended when the LID is closed. The cause is that the USB HID multi-touch
> > > touchpad in the base of the device starts sending events when the screen
> > > gets close to the touchpad (so when the LID is fully closed) and these
> > > events are causing a wakeup from suspend. HID multi-touch devices
> > > do have a way to tell them to fully stop sending events, also disabling
> > > the USB remote wakeup the device is doing. The question is when to tell
> > > it to not send events though ...
> > >
> > > So now I've been thinking about how to fix this and I believe that there
> > > is some interaction between this problem and this patch-set.
> > >
> > > The problem I'm seeing on the T101HA is about wakeups, so the question
> > > which I want to discuss is:
> > >
> > > 1. How does inhibiting interact with enabling /
> > > disabling the device as a wakeup source ?
>
> One should not affect the other.
>
> > > 2. Since we have now made inhibiting equal open/close how does open/close
> > > interact with a device being a wakeup source ?
>
> One did not affect another, and it should not.
>
> > > And my own initial (to be discussed) answers to these questions:
> > >
> > > 1. It seems to me that when a device is inhibited it should not be a
> > > wakeup source, so where possible a input-device-driver should disable
> > > a device's wakeup capabilities on suspend if inhibited
> >
> > If "inhibit" means "do not generate any events going forward", then
> > this must also cover wakeup events, so I agree.
>
> Why? These are separate concepts. Do we disable wake on lan when
> bringing network interface down? Do we update power/wakeup when device
> is inhibited? Do we restore it afterwards? Do we un-inhibit if we
> reenable wakeup after device is inhibited? Do we return error? How?
>
> Inhibit works on logical level, i.e. if I have several input interfaces
> on the same hardware device, I cam inhibit one leaving others intact.
> This does not mean that the device should stop generating wakeup events.
> We can't even guarantee this for composite devices.

After thinking more about this I believe you are right and we should
keep these as 2 separate, completely independent settings.

Especially since the wakeup setting typically is a setting of the
parent device, where as the inhibit is done on the actual input-dev.

###

Some quick background info on my original thoughts here, as mentioned
I started thinking about this because of spurious wakeups from suspend
when the lid of an asus t101ha is "touching" its touchpad. The HID
multi-touch protocol has a setting where we can ask the device to
stop sending events. So even though the kbd + touchpad are a
single composite USB device, we can disable wakeup (in a way)
for just the touchpad at the hid-multitouch level.

So I was thinking maybe adding a separate wakeup setting to the
input device itself for this. But thinking more about it, when
the lid is closed we can just disable wakeup on the entire USB
device, since the keyboard is covered by the lid too.

And then on suspend the hid-multitouch driver can detect that its
parent (or parents parent in the case of USB) has wakeup disabled
and also tell the device to stop scanning for fingers to save some
power.

We probably also need a close and open callbacks add the HID-driver
level, so that if there are no touchpad users we can also use
the same option to put the HID multi-touch device in a low power mode
where it does not scan for fingers.

<snip>

> > > A different, but related issue is how to make devices actually use the
> > > new inhibit support on the builtin keyboard + touchpad when say the lid
> > > is closed.   Arguably this is an userspace problem, but it is a tricky
> > > one. Currently on most modern Linux distributions suspend-on-lid-close
> > > is handled by systemd-logind and most modern desktop-environments are
> > > happy to have logind handle this for them.
> > >
> > > But most knowledge about input devices and e.g. heurisitics to decide
> > > if a touchpad is internal or external are part of libinput. Now we could
> > > have libinput use the new inhibit support (1), but then when the lid
> > > closes we get race between whatever process is using libinput trying
> > > to inhibit the touchpad (which must be done before to suspend to disable
> > > it as wakeup source) and logind trying to suspend the system.
> > >
> > > One solution here would be to move the setting of the inhibit sysfs
> > > attr into logind, but that requires adding a whole bunch of extra
> > > knowledge to logind which does not really belong there IMHO.
>
> You do not need to push the knowledge into logind, you just need to
> communicate to logind what devices can be wakeup sources and which ones
> should not. Chrome OS uses udev tags/properties for that.

True, I did not think of doing the tag thingie + letting logind do
the inhibit on LID close based on that. logind could also disable
wakeup (to save power while suspended) on devices which are tagged
for it to do that (should probably be a separate tag from the
inhibit tag).

> > > I've been thinking a bit about this and to me it seems that the kernel
> > > is in the ideal position to automatically inhibit some devices when
> > > some EV_SW transitions from 0->1 (and uninhibit again on 1->0). The
> > > issue here is to chose on which devices to enable this. I believe
> > > that the auto inhibit on some switches mechanism is best done inside
> > > the kernel (disabled by default) and then we can have a sysfs
> > > attr called auto_inhibit_ev_sw_mask which can be set to e.g.
> > > (1 << SW_LID) to make the kernel auto-inhibit the input-device whenever
> > > the lid is closed, or to ((1 << SW_LID) | (1 << SW_TABLET_MODE)) to
> > > inhibit both when the lid is closed or when switched to tablet mode.
>
> This is a policy and should be kept out of the kernel. Yes, we had it
> implemented with rfkill input handler, but it caused quite a few issues.
> As far as I know it is not being used anymore and we should not try with
> SW_LID->inhibit either.
>
> I know it is faster to patch the kernel than to roll out proper
> userspace because everyone updates kernel regularly, but it does not
> mean it is the right solution.

Agreed, I just could not come up with a clean userspace solution, but
using udev+hwdb to set a tag for logind instead of having the write
to a new auto_inhibit_ev_sw_mask will work nicely.

So I think this is all resolved now (or at least we have a plan for it).

Regards,

Hans