RE: [RFC] Generic implementation for Input enable disable methods

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>-----Original Message-----
>From: ext Dmitry Torokhov [mailto:dmitry.torokhov@xxxxxxxxx]
>
>Hi Samu,
>
>I still believe that the only thing we need (apart of special plumbing
>in
>gpio-keys) is a way for userspace clients to subsribe on unsubscribe
>from certain events rather than device-wide configuration. This way we
>can avoid waking up processes that are not interested in some of the
>events.
>

Hi Dmitry,

I just noticed that control interface for gpio was applied to input-tree.
We still have a need to disable hw in certain cases. It is probably better
to forget generic implementation to input core and make control interface
as specific to each driver like proposed some months ago for example
for tel4030-keypad driver. Or what do you think?

Sw filtering which avoids to wakeup some processes is not proper solution
to embedded devices. We need to avoid waking up the processor itself.

Br,
Samu




--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux