mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Mario.Limonciello@dell.com>
To: <pali.rohar@gmail.com>
Cc: <dmitry.torokhov@gmail.com>, <linux-input@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: RE: Dell docking station & Dell Embedded Controller & PS/2 devices
Date: Mon, 7 May 2018 20:18:30 +0000	[thread overview]
Message-ID: <6825f48ea6da41799979d83ed37adf73@ausx13mpc124.AMER.DELL.COM> (raw)
In-Reply-To: <20180507200733.s43zd2hfzw4f4wr2@pali>

> > > So I guess you could write a platform driver that would install i8042
> > > filter on Dell laptops/portables, monitor keyboard data stream and kick
> > > of rescans on serio ports. The problem is filter gets "serio" so you do
> > > not really know whether ACK is spurious or not. And I would really
> > > prefer keeping this crap out of atkbd proper... And all of this is racy
> > > as hell. What happens if we get keyboard reconnected as we reinitialize
> > > it?
> >
> > If it's done as a platform driver I would suspect it's possible to tell whether
> > a dock is connected to at least give you some heuristic here to have a better
> > guess whether it's spurious.
> 
> Apparently checking for docking station is not enough. There are also
> Dell Legacy Extenders (or how it is called) which exports internal PS/2,
> Parallel and Serial Ports. It is also connecting to bottom of laptop.
> But currently I do not have them for testing.
> 
> > Pali on your system that supports this dock, check and see how many
> > System Enclosure SMBIOS tables (structure type 03) are present.
> 
> Do you mean DMI type 3 structure? Here is something from dmidecode:
> 
> Handle 0x0003, DMI type 3, 22 bytes
> Chassis Information
>         Manufacturer: Dell Inc.
>         Type: Laptop
>         Lock: Not Present
>         Version: Not Specified
>         Serial Number: --REMOVED--
>         Asset Tag: Not Specified
>         Boot-up State: Safe
>         Power Supply State: Safe
>         Thermal State: Safe
>         Security Status: None
>         OEM Information: 0x00000000
>         Height: Unspecified
>         Number Of Power Cords: 1
>         Contained Elements: 0
>         SKU Number: To be filled by O.E.M.
> 
> But probably you mean something different?

Plug in your dock before you boot up and see if you have a second structure like
that type produced.

If not, then I guess this isn't a reliable way to find the dock
on that system and I'll have to see if there is another.

  reply	other threads:[~2018-05-07 20:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24 10:41 Pali Rohár
2018-02-01 19:29 ` Dmitry Torokhov
2018-02-01 19:35   ` Mario.Limonciello
2018-02-01 21:14     ` Dmitry Torokhov
2018-02-01 21:23       ` Mario.Limonciello
2018-02-04 20:07         ` Pali Rohár
2018-05-06 13:47   ` Pali Rohár
2018-05-07  8:44     ` Pali Rohár
2018-05-07 19:33       ` Dmitry Torokhov
2018-05-07 19:58         ` Pali Rohár
2018-05-07 19:59         ` Mario.Limonciello
2018-05-07 20:07           ` Pali Rohár
2018-05-07 20:18             ` Mario.Limonciello [this message]
2018-05-07 20:28               ` Pali Rohár
2018-05-07 20:30                 ` Mario.Limonciello
2018-05-07 20:32                   ` Mario.Limonciello
2018-05-07 20:48                     ` 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=6825f48ea6da41799979d83ed37adf73@ausx13mpc124.AMER.DELL.COM \
    --to=mario.limonciello@dell.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    /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

all inboxes | Powered by JetHome®