linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@insightbb.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: lenb@kernel.org, Richard Hughes <hughsient@gmail.com>,
	linux-acpi@vger.kernel.org, linux-input@atrey.karlin.mff.cuni.cz,
	ibm-acpi-devel@lists.sourceforge.net
Subject: Re: Exporting EV_SW SW_LID events from thinkpad-acpi to input layer
Date: Sat, 16 Jun 2007 12:00:51 -0400	[thread overview]
Message-ID: <200706161200.52863.dtor@insightbb.com> (raw)
In-Reply-To: <20070616144411.GA2127@khazad-dum.debian.net>

On Saturday 16 June 2007 10:44, Henrique de Moraes Holschuh wrote:
> thinkpad-acpi can now be made to export EV_SW SW_LID events to the input
> layer.
> 
> However, most (all?) thinkpads will also generate ACPI notifications to
> \_SB.LID, on LID changes, i.e. this would duplicate an ACPI LID event, and I
> undertand ACPI is already moving to provide those over an input device by
> itself.
> 
> Given that situation, is it desireable for thinkpad-acpi to export EV_SW
> SW_LID events by itself (possibly duplicating an event that the ACPI layer
> will also issue)?  Or should I just ignore the lid events, and leave them
> for the ACPI layer to deal with?
> 

I would just rely on ACPI button driver to deliver EV_SW/SW_LID events.
After all there is only one lid switch on the box so having 2 input
devices rep[orting it is counter-intuitive.
 
-- 
Dmitry

      reply	other threads:[~2007-06-16 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16 14:44 Exporting EV_SW SW_LID events from thinkpad-acpi to input layer Henrique de Moraes Holschuh
2007-06-16 16:00 ` Dmitry Torokhov [this message]

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=200706161200.52863.dtor@insightbb.com \
    --to=dtor@insightbb.com \
    --cc=hmh@hmh.eng.br \
    --cc=hughsient@gmail.com \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    /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).