public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Matthew Garrett <mjg@redhat.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] acpi: Don't send KEY_UNKNOWN for random video notifications
Date: Wed, 31 Mar 2010 20:57:31 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.1003312057140.5062@localhost.localdomain> (raw)
In-Reply-To: <1260571246-24582-1-git-send-email-mjg@redhat.com>

applied to acpi-test -- looking for ack from rui, the driver maintainer

thanks,
Len Brown, Intel Open Source Technology Center

On Fri, 11 Dec 2009, Matthew Garrett wrote:

> I have a machine here that's sending 0xD1 notifications on the video
> device once every second or so. I have no idea why (it's a prototype,
> it may be broken), but sending KEY_UNKNOWN is unhelpful and results in
> the console becoming unusable. Let's not report keys unless we have
> something useful to say about them.
> 
> Signed-off-by: Matthew Garrett <mjg@redhat.com>
> ---
>  drivers/acpi/video.c |   29 ++++++++++++++++-------------
>  1 files changed, 16 insertions(+), 13 deletions(-)
> 
> diff --git a/drivers/acpi/video.c b/drivers/acpi/video.c
> index 05dff63..655183c 100644
> --- a/drivers/acpi/video.c
> +++ b/drivers/acpi/video.c
> @@ -2100,7 +2100,7 @@ static void acpi_video_bus_notify(struct acpi_device *device, u32 event)
>  {
>  	struct acpi_video_bus *video = acpi_driver_data(device);
>  	struct input_dev *input;
> -	int keycode;
> +	int keycode = 0;
>  
>  	if (!video)
>  		return;
> @@ -2136,17 +2136,19 @@ static void acpi_video_bus_notify(struct acpi_device *device, u32 event)
>  		break;
>  
>  	default:
> -		keycode = KEY_UNKNOWN;
>  		ACPI_DEBUG_PRINT((ACPI_DB_INFO,
>  				  "Unsupported event [0x%x]\n", event));
>  		break;
>  	}
>  
>  	acpi_notifier_call_chain(device, event, 0);
> -	input_report_key(input, keycode, 1);
> -	input_sync(input);
> -	input_report_key(input, keycode, 0);
> -	input_sync(input);
> +
> +	if (keycode) {
> +		input_report_key(input, keycode, 1);
> +		input_sync(input);
> +		input_report_key(input, keycode, 0);
> +		input_sync(input);
> +	}
>  
>  	return;
>  }
> @@ -2157,7 +2159,7 @@ static void acpi_video_device_notify(acpi_handle handle, u32 event, void *data)
>  	struct acpi_device *device = NULL;
>  	struct acpi_video_bus *bus;
>  	struct input_dev *input;
> -	int keycode;
> +	int keycode = 0;
>  
>  	if (!video_device)
>  		return;
> @@ -2198,17 +2200,19 @@ static void acpi_video_device_notify(acpi_handle handle, u32 event, void *data)
>  		keycode = KEY_DISPLAY_OFF;
>  		break;
>  	default:
> -		keycode = KEY_UNKNOWN;
>  		ACPI_DEBUG_PRINT((ACPI_DB_INFO,
>  				  "Unsupported event [0x%x]\n", event));
>  		break;
>  	}
>  
>  	acpi_notifier_call_chain(device, event, 0);
> -	input_report_key(input, keycode, 1);
> -	input_sync(input);
> -	input_report_key(input, keycode, 0);
> -	input_sync(input);
> +
> +	if (keycode) {
> +		input_report_key(input, keycode, 1);
> +		input_sync(input);
> +		input_report_key(input, keycode, 0);
> +		input_sync(input);
> +	}
>  
>  	return;
>  }
> @@ -2299,7 +2303,6 @@ static int acpi_video_bus_add(struct acpi_device *device)
>  	set_bit(KEY_BRIGHTNESSDOWN, input->keybit);
>  	set_bit(KEY_BRIGHTNESS_ZERO, input->keybit);
>  	set_bit(KEY_DISPLAY_OFF, input->keybit);
> -	set_bit(KEY_UNKNOWN, input->keybit);
>  
>  	error = input_register_device(input);
>  	if (error)
> -- 
> 1.6.5.2
> 

  reply	other threads:[~2010-04-01  0:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 22:40 [PATCH] acpi: Don't send KEY_UNKNOWN for random video notifications Matthew Garrett
2010-04-01  0:57 ` Len Brown [this message]
2010-04-01  6:57   ` Zhang Rui
2010-04-01 12:32     ` Matthew Garrett
2010-04-02  1:05       ` Zhang Rui

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=alpine.LFD.2.00.1003312057140.5062@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg@redhat.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