linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-input@vger.kernel.org, linu-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add switch for dock events
Date: Fri, 23 May 2008 18:23:00 -0700	[thread overview]
Message-ID: <20080523182300.bd05ec54.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080523160955.GA19674@srcf.ucam.org>

On Fri, 23 May 2008 17:09:55 +0100 Matthew Garrett <mjg59@srcf.ucam.org> wrote:

> Add a switch to signal dock events to userspace.
> 
> Signed-off-by: Matthew Garrett <mjg@redhat.com>
> 
> ---
> 
> I've done this as an input event rather than anything else since there 
> isn't necessarily a terribly coherent concept of a dock device. HPs (for 
> example) don't use ACPI for docking - the dock is simply an extension of 
> devices that are already on the system. We can't sensibly create a dock 
> platform device and then generate uevents on it. Doing it this way lets 
> us standardise on a way to send docking events to userspace, which lets 
> desktops do things like automatically expand onto external monitors when 
> the system is docked.
> 
> diff --git a/include/linux/input.h b/include/linux/input.h
> index 28a094f..0bc55ee 100644
> --- a/include/linux/input.h
> +++ b/include/linux/input.h
> @@ -638,6 +638,7 @@ struct input_absinfo {
>  #define SW_TABLET_MODE		0x01  /* set = tablet mode */
>  #define SW_HEADPHONE_INSERT	0x02  /* set = inserted */
>  #define SW_RADIO		0x03  /* set = radio enabled */
> +#define SW_DOCK			0x04  /* set = plugged into dock */
>  #define SW_MAX			0x0f
>  #define SW_CNT			(SW_MAX+1)
> 
> 

Confused.  This patch doesn't do anything.

Also, please sort out the changelogging?

- The one-line changelog you have there would make a decent _title_. 
  Better than the one which was actually chosen.

- The not-to-be-included discussion which you have below the "---"
  cutoff line would make a reasonable changelog.

  reply	other threads:[~2008-05-24  1:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23 16:09 [PATCH] Add switch for dock events Matthew Garrett
2008-05-24  1:23 ` Andrew Morton [this message]
2008-05-28 13:06 ` [PATCH 1/3] Input: " Matthew Garrett
2008-05-28 13:21   ` [PATCH 2/3] ACPI: Send switch event on " Matthew Garrett
2008-05-28 13:29     ` [PATCH 3/3] Misc: Add HP WMI laptop extras driver Matthew Garrett
2008-05-29  5:42       ` RESEND: " Andrew Morton
2008-05-29  8:07         ` Matthew Garrett
2008-05-29  8:23       ` Matthew Garrett
2008-06-02 23:30         ` Andrew Morton
2008-06-07 10:00       ` Carlos Corbacho
2008-05-29  5:32     ` RESEND: [PATCH 2/3] ACPI: Send switch event on dock events Andrew Morton
2008-05-29  8:15       ` Matthew Garrett
2008-05-29  8:22     ` Version 2: " Matthew Garrett
2008-06-09  9:48       ` Andrew Morton
2008-05-29  8:20   ` Version 2: [PATCH 1/3] Input: Add switch for " Matthew Garrett

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=20080523182300.bd05ec54.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linu-acpi@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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).