DORMANTno replies

[PATCH 2/2] Input: wacom - add support for three new Intuos devices

From: Ping Cheng <hidden>
Date: 2013-10-04 18:16:01

On Fri, Oct 4, 2013 at 9:47 AM, Jason Gerecke [off-list ref] wrote:
On Thu, Oct 3, 2013 at 2:54 PM, Dmitry Torokhov
[off-list ref] wrote:
quoted
On Thursday, October 03, 2013 01:53:10 PM Ping Cheng wrote:
quoted
This series of models added a hardware switch to turn touch
data on/off. To report the state of the switch, SW_TOUCH_ENABLED
is added in include/uapi/linux/input.h.

Hmm, should we just postpone creating of input device until touch is enabled
instead?

--
Dmitry
--
The idea of SW_TOUCH_ENABLED is to allow userspace to be a bit more
helpful and display a "disabled" message rather than disappearing the
device entirely when the switch is 'off'. In theory this could also be
achieved through the libwacom support library (by scanning the list of
event devices to see if any of the expected interfaces are missing),
but the approach is somewhat fragile and I'm not convinced that
linking the switch to device creation/removal is correct.

Good point, Jason. I thought Dmitry suggested to have SW_TOUCH_ENABLED
accepted before adding new devices. My misunderstanding did bring nice
feedbacks from Chris and Peter. Thank you guys.

Dmitry,

If you meant to check the status of the touch switch before creating
touch interface, that would also mean we need to delete the interface
if the switch is turned off. Otherwise, we are not supporting it
consistently. However, the switch is only an indicator of whether
tablet will post touch events or not. The actual touch device is not
removed. It is always there and connected to the system no matter what
state the switch is in. So, dynamically creating and removal of touch
interface can complicate user land support.

Does this make sense to you?

Ping
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help