From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Ike Panhc <ike.pan@canonical.com>
Cc: linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
Matthew Garrett <mjg@redhat.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 3/3] ideapad: add hotkey support
Date: Wed, 17 Nov 2010 13:29:43 -0800 [thread overview]
Message-ID: <20101117212943.GA6661@core.coreip.homeip.net> (raw)
In-Reply-To: <1289977238-15113-1-git-send-email-ike.pan@canonical.com>
On Wed, Nov 17, 2010 at 03:00:38PM +0800, Ike Panhc wrote:
> Hotkey enabled by this patch:
> Fn+F3: Video mode switch
> Fn+F5: software rfkill for wifi
>
> For some ideapad when push Fn+F3, hardware generates Super-P keys, those key
> will not be enabled by this patch.
>
> Signed-off-by: Ike Panhc <ike.pan@canonical.com>
> ---
> drivers/platform/x86/ideapad-laptop.c | 74 +++++++++++++++++++++++++++++++++
> 1 files changed, 74 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/platform/x86/ideapad-laptop.c b/drivers/platform/x86/ideapad-laptop.c
> index d75c21f..d397034 100644
> --- a/drivers/platform/x86/ideapad-laptop.c
> +++ b/drivers/platform/x86/ideapad-laptop.c
> @@ -28,6 +28,8 @@
> #include <acpi/acpi_drivers.h>
> #include <linux/rfkill.h>
> #include <linux/platform_device.h>
> +#include <linux/input.h>
> +#include <linux/input/sparse-keymap.h>
>
> #define IDEAPAD_DEV_CAMERA 0
> #define IDEAPAD_DEV_WLAN 1
> @@ -39,6 +41,7 @@ struct ideapad_private {
> acpi_handle handle;
> struct rfkill *rfk[5];
> struct platform_device *platform_device;
> + struct input_dev *inputdev;
> } *ideapad_priv;
>
> static struct {
> @@ -325,6 +328,68 @@ static void ideapad_platform_exit(void)
> }
> /* the above is platform device */
>
> +/*
> + * input device
> + */
> +static const struct key_entry ideapad_keymap[] = {
> + { KE_KEY, 0x06, { KEY_SWITCHVIDEOMODE } },
> + { KE_KEY, 0x0D, { KEY_WLAN } },
> + { KE_END, 0 },
> +};
> +
> +static int ideapad_input_init(void)
__devinit?
> +{
> + struct input_dev *inputdev;
> + int error;
> +
> + inputdev = input_allocate_device();
> + if (!inputdev) {
> + pr_info("Unable to allocate input device\n");
> + return -ENOMEM;
> + }
> +
> + inputdev->name = "Ideapad extra buttons";
> + inputdev->phys = "ideapad/input0";
> + inputdev->id.bustype = BUS_HOST;
> + inputdev->dev.parent = &ideapad_priv->platform_device->dev;
> +
> + error = sparse_keymap_setup(inputdev, ideapad_keymap, NULL);
> + if (error) {
> + pr_err("Unable to setup input device keymap\n");
> + goto err_free_dev;
> + }
> +
> + error = input_register_device(inputdev);
> + if (error) {
> + pr_err("Unable to register input device\n");
> + goto err_free_keymap;
> + }
> +
> + ideapad_priv->inputdev = inputdev;
Why don't you pass ideapad_priv in as an argument instead of relying on
global. I know that there can only be one, but then why do you have a
structure?
> + return 0;
> +
> +err_free_keymap:
> + sparse_keymap_free(inputdev);
> +err_free_dev:
> + input_free_device(inputdev);
> + return error;
> +}
> +
> +static void ideapad_input_exit(void)
__devexit? The rest of the driver might user these markups as well.
> +{
> + if (ideapad_priv->inputdev) {
> + sparse_keymap_free(ideapad_priv->inputdev);
> + input_unregister_device(ideapad_priv->inputdev);
> + }
> + ideapad_priv->inputdev = NULL;
You fail driver initialization when ideapad_input_init() fails so there
is no point in checking whether ideapad_priv->inputdev is null or not.
Otherwise looks good from input POV.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2010-11-17 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 6:59 [PATCH 0/3] ideapad: hotkey enablement Ike Panhc
2010-11-17 7:00 ` [PATCH 1/3] ideapad: add platform driver for ideapad Ike Panhc
2010-11-17 7:00 ` [PATCH 2/3] ideapad: let camera power control entry under platform driver Ike Panhc
2010-11-17 7:00 ` [PATCH 3/3] ideapad: add hotkey support Ike Panhc
2010-11-17 21:29 ` Dmitry Torokhov [this message]
2010-11-18 7:35 ` Corentin Chary
2010-11-19 7:09 ` Ike Panhc
2010-12-02 23:41 ` Dave Hansen
2010-12-02 23:43 ` Ike Panhc
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=20101117212943.GA6661@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=ike.pan@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@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
Powered by JetHome