linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Initialization of TPPS/2 IBM TrackPoint in too slow
Date: Fri, 31 Jul 2015 19:17:02 +0200	[thread overview]
Message-ID: <201507311917.02131@pali> (raw)
In-Reply-To: <20150731170849.GG5613@dtor-ws>

[-- Attachment #1: Type: Text/Plain, Size: 2324 bytes --]

On Friday 31 July 2015 19:08:49 Dmitry Torokhov wrote:
> On Fri, Jul 31, 2015 at 06:59:21PM +0200, Pali Rohár wrote:
> > Hello,
> > 
> > here is output from dmesg for psmouse.ko
> > 
> > [  266.378751] psmouse: calling psmouse_init()
> > [  267.167150] psmouse serio1: synaptics: queried max coordinates:
> > x [..5676], y [..4758] [  267.198416] psmouse serio1: synaptics:
> > queried min coordinates: x [1266..], y [1096..] [  267.260402]
> > psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id:
> > 0x1e2b1, caps: 0xf002a3/0x943300/0x12e800, board id: 3072, fw id:
> > 2560
> > [  267.260418] psmouse serio1: synaptics: serio: Synaptics
> > pass-through port at isa0060/serio1/input0 [  267.299629] input:
> > SynPS/2 Synaptics TouchPad as
> > /devices/platform/i8042/serio1/input/input39 [  268.697333]
> > psmouse serio4: cypress_ps2: send extension cmd 0x00, [0 0 0 0] [ 
> > 269.259351] psmouse serio4: cypress_ps2: Command 0x00 response
> > data (0x): 00 00 14 [  269.562762] psmouse serio4: alps: E6
> > report: 00 00 64
> > [  269.825915] psmouse serio4: alps: E7 report: 10 00 64
> > [  270.086671] psmouse serio4: alps: EC report: 10 00 64
> > [  270.125866] psmouse serio4: alps: Likely not an ALPS touchpad:
> > E7=10 00 64, EC=10 00 64 [  270.388147] psmouse serio4: elantech:
> > unexpected magic knock result 0x00, 0x02, 0x64. [  271.390241]
> > psmouse serio4: trackpoint: IBM TrackPoint firmware: 0x0e,
> > buttons: 3/3 [  271.586156] input: TPPS/2 IBM TrackPoint as
> > /devices/platform/i8042/serio1/serio4/input/input40
> > 
> > As you can see it takes about 5 seconds to initialize TrackPoint
> > input device. And about 3 seconds from stage after synaptics
> > export serio device. I think this is just because of trying to
> > detect device type. Is there any way how to speed it up? Maybe for
> > synaptics serio devices try to probe for TPPS/2 at first?
> 
> Did you abandon your trusty Dell with ALPS? ;)
> 

No, I'm not going to do that :-) 

> Yes, I think we should limit the number of protocols that we probe on
> pass-through port to standard PS/2 flavors + TPPS/2 since I have
> never seen anything else there.
> 
> Thanks.

And If not limiting, at least changing order and preferring TPPS/2.

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-07-31 17:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 16:59 Initialization of TPPS/2 IBM TrackPoint in too slow Pali Rohár
2015-07-31 17:08 ` Dmitry Torokhov
2015-07-31 17:17   ` Pali Rohár [this message]
2015-07-31 17:30     ` Dmitry Torokhov
2015-07-31 18:11       ` Pali Rohár
2015-08-21  8:13         ` Pali Rohár

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201507311917.02131@pali \
    --to=pali.rohar@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).