* [PATCH] Input: psmouse - add small delay for IBM trackpoint pass-through mode
@ 2015-08-15 14:40 Stefan Assmann
2015-08-26 20:13 ` Dmitry Torokhov
0 siblings, 1 reply; 4+ messages in thread
From: Stefan Assmann @ 2015-08-15 14:40 UTC (permalink / raw)
To: linux-input; +Cc: linux-kernel, dmitry.torokhov, sassmann
There are trackpoint devices that fail to respond to the PS2 command
PSMOUSE_CMD_GETID if immediately queried after the parent device is
deactivated. Add a small delay for the hardware to get in a sane state
before sending any PS2 commands.
One example of such a system is:
Lenovo ThinkPad X120e, model 30515QG
synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x121c00, board id: 1811, fw id: 797391
Signed-off-by: Stefan Assmann <sassmann@kpanic.de>
---
drivers/input/mouse/psmouse-base.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/input/mouse/psmouse-base.c b/drivers/input/mouse/psmouse-base.c
index ec347703..ad18dab 100644
--- a/drivers/input/mouse/psmouse-base.c
+++ b/drivers/input/mouse/psmouse-base.c
@@ -1540,6 +1540,10 @@ static int psmouse_connect(struct serio *serio, struct serio_driver *drv)
if (error)
goto err_clear_drvdata;
+ /* give PT device some time to settle down before probing */
+ if (serio->id.type == SERIO_PS_PSTHRU)
+ usleep_range(10000, 15000);
+
if (psmouse_probe(psmouse) < 0) {
error = -ENODEV;
goto err_close_serio;
--
2.4.3
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH] Input: psmouse - add small delay for IBM trackpoint pass-through mode
@ 2015-08-16 15:33 Andreas Mohr
2015-08-17 7:35 ` Stefan Assmann
0 siblings, 1 reply; 4+ messages in thread
From: Andreas Mohr @ 2015-08-16 15:33 UTC (permalink / raw)
To: Stefan Assmann; +Cc: linux-kernel, linux-input
Hi,
[rogue out-of-band reply, sorry - lkml.org mail info is broken]
> There are trackpoint devices that fail to respond to the PS2 command
> PSMOUSE_CMD_GETID if immediately queried after the parent device is
> deactivated. Add a small delay for the hardware to get in a sane state
> before sending any PS2 commands.
Hmm, "deactivated"?
Probably a parent needs to be "activated" for a passthrough device
(child device?)
to be able to communicate? (I don't know much about these things though...)
> + usleep_range(10000, 15000);
Ah, used _range() API - strong bonus points
for caring about wakeup minimization! :)
(and I take it you surely cared to check proper device operation
at both cases of doing usleep()
with either upper or lower delay amount specified... ;)
In general it's somewhat sad
to see an unconditional implementation
via woefully imprecise delay-only operation here -
is there a way to have it implemented
as a properly *handshaked* protocol,
i.e. try (re-)doing some other query type
which would fail until init is ok or timeout?
OTOH in that case PSMOUSE_CMD_GETID probably happens to be
just that kind of "handshaked success" query type to be used here...
Or, IOW (pseudo code):
delay;
if (!query()) fail;
sounds rather worse from a handshaked-protocol POV than
while (retries_remaining)
if (query()) break;
delay;
This reasoning would probably suggest
that such a loop should be added *within* psmouse_probe(), at the first
check (i.e., PSMOUSE_CMD_GETID).
OTOH that handshaked loop is only feasible
if doing repeated PSMOUSE_CMD_GETID query attempts
is actually supported (tolerated) by devices
(vs. no-op delaying and *then* trying one time only),
i.e. that repeated PSMOUSE_CMD_GETID queries will succeed
rather than fail or even block...
BTW, to make it obvious why non-handshaked operation may easily end up worse:
certain devices (out of a couple thousands of different
China-made human interface device models
which will be relevant here ;)
might perhaps *require* getting queried immediately *without* any prior delay,
in which case the first (AND LAST!) PSMOUSE_CMD_GETID query
after the (your) delay
would now already fail for those devices...
HTH,
Andreas Mohr
--
GNU/Linux. It's not the software that's free, it's you.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] Input: psmouse - add small delay for IBM trackpoint pass-through mode
2015-08-16 15:33 Andreas Mohr
@ 2015-08-17 7:35 ` Stefan Assmann
0 siblings, 0 replies; 4+ messages in thread
From: Stefan Assmann @ 2015-08-17 7:35 UTC (permalink / raw)
To: Andreas Mohr; +Cc: linux-kernel, linux-input
On 16.08.2015 17:33, Andreas Mohr wrote:
> Hi,
>
> [rogue out-of-band reply, sorry - lkml.org mail info is broken]
Hi Andreas,
>
>> There are trackpoint devices that fail to respond to the PS2 command
>> PSMOUSE_CMD_GETID if immediately queried after the parent device is
>> deactivated. Add a small delay for the hardware to get in a sane state
>> before sending any PS2 commands.
>
> Hmm, "deactivated"?
> Probably a parent needs to be "activated" for a passthrough device
> (child device?)
> to be able to communicate? (I don't know much about these things though...)
Comment from few lines above where I put the code.
/*
* If this is a pass-through port deactivate parent so the device
* connected to this port can be successfully identified
*/
>
>
>> + usleep_range(10000, 15000);
>
> Ah, used _range() API - strong bonus points
> for caring about wakeup minimization! :)
>
> (and I take it you surely cared to check proper device operation
> at both cases of doing usleep()
> with either upper or lower delay amount specified... ;)
Yes, I went as low as 10ms and figured it still works. Then I added
another 5ms if the kernel wants to wake up at a later time. If that's
too much we can decrease the upper limit, although this should only
happen once per boot.
>
>
>
>
> In general it's somewhat sad
> to see an unconditional implementation
> via woefully imprecise delay-only operation here -
> is there a way to have it implemented
> as a properly *handshaked* protocol,
> i.e. try (re-)doing some other query type
> which would fail until init is ok or timeout?
> OTOH in that case PSMOUSE_CMD_GETID probably happens to be
> just that kind of "handshaked success" query type to be used here...
Thought about that too, but I know too little about the hardware to give
you a proper answer. I'm not even sure why PSMOUSE_CMD_GETID sometimes
fails at all. I assume that hardware needs some time to settle down
after the parent gets deactivated to accept commands.
>
>
> Or, IOW (pseudo code):
>
> delay;
> if (!query()) fail;
>
> sounds rather worse from a handshaked-protocol POV than
>
> while (retries_remaining)
> if (query()) break;
> delay;
>
>
> This reasoning would probably suggest
> that such a loop should be added *within* psmouse_probe(), at the first
> check (i.e., PSMOUSE_CMD_GETID).
>
> OTOH that handshaked loop is only feasible
> if doing repeated PSMOUSE_CMD_GETID query attempts
> is actually supported (tolerated) by devices
> (vs. no-op delaying and *then* trying one time only),
> i.e. that repeated PSMOUSE_CMD_GETID queries will succeed
> rather than fail or even block...
>
>
>
> BTW, to make it obvious why non-handshaked operation may easily end up worse:
> certain devices (out of a couple thousands of different
> China-made human interface device models
> which will be relevant here ;)
> might perhaps *require* getting queried immediately *without* any prior delay,
> in which case the first (AND LAST!) PSMOUSE_CMD_GETID query
> after the (your) delay
> would now already fail for those devices...
All you're saying is correct. Please note that I carefully limited the
sleep to only SERIO_PS_PSTHRU devices, so the majority of devices out
there is not going to see this at all. IIRC, PSMOUSE_CMD_GETID is the
initial command to be sent to a PS2 device, so a delay before that
should not do any harm. Of course I cannot prove that this will not have
any side-effect on some random hardware, but I'm really trying to narrow
down the number of affected devices to those who may profit from the
change.
Thanks for the feedback.
Stefan
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] Input: psmouse - add small delay for IBM trackpoint pass-through mode
2015-08-15 14:40 [PATCH] Input: psmouse - add small delay for IBM trackpoint pass-through mode Stefan Assmann
@ 2015-08-26 20:13 ` Dmitry Torokhov
0 siblings, 0 replies; 4+ messages in thread
From: Dmitry Torokhov @ 2015-08-26 20:13 UTC (permalink / raw)
To: Stefan Assmann; +Cc: linux-input, linux-kernel
On Sat, Aug 15, 2015 at 04:40:18PM +0200, Stefan Assmann wrote:
> There are trackpoint devices that fail to respond to the PS2 command
> PSMOUSE_CMD_GETID if immediately queried after the parent device is
> deactivated. Add a small delay for the hardware to get in a sane state
> before sending any PS2 commands.
>
> One example of such a system is:
> Lenovo ThinkPad X120e, model 30515QG
> synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x121c00, board id: 1811, fw id: 797391
>
> Signed-off-by: Stefan Assmann <sassmann@kpanic.de>
Applied, thank you.
> ---
> drivers/input/mouse/psmouse-base.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/input/mouse/psmouse-base.c b/drivers/input/mouse/psmouse-base.c
> index ec347703..ad18dab 100644
> --- a/drivers/input/mouse/psmouse-base.c
> +++ b/drivers/input/mouse/psmouse-base.c
> @@ -1540,6 +1540,10 @@ static int psmouse_connect(struct serio *serio, struct serio_driver *drv)
> if (error)
> goto err_clear_drvdata;
>
> + /* give PT device some time to settle down before probing */
> + if (serio->id.type == SERIO_PS_PSTHRU)
> + usleep_range(10000, 15000);
> +
> if (psmouse_probe(psmouse) < 0) {
> error = -ENODEV;
> goto err_close_serio;
> --
> 2.4.3
>
--
Dmitry
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-08-26 20:13 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-08-15 14:40 [PATCH] Input: psmouse - add small delay for IBM trackpoint pass-through mode Stefan Assmann
2015-08-26 20:13 ` Dmitry Torokhov
-- strict thread matches above, loose matches on Subject: below --
2015-08-16 15:33 Andreas Mohr
2015-08-17 7:35 ` Stefan Assmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox