From: Joe Perches <joe@perches.com>
To: Chen Yu <yu.c.chen@intel.com>
Cc: dvhart@infradead.org, akpm@linux-foundation.org, arnd@arndb.de,
mchehab@osg.samsung.com, gregkh@linuxfoundation.org,
jslaby@suse.com, rui.zhang@intel.com, rafael.j.wysocki@intel.com,
mika.westerberg@intel.com, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] [v2] surface pro 3: Add support driver for Surface Pro 3 buttons
Date: Fri, 07 Aug 2015 01:27:58 -0700 [thread overview]
Message-ID: <1438936078.2322.29.camel@perches.com> (raw)
In-Reply-To: <1438934272-17959-1-git-send-email-yu.c.chen@intel.com>
On Fri, 2015-08-07 at 15:57 +0800, Chen Yu wrote:
> Since Surface Pro 3 does not follow the specs of "Windows ACPI Design
> Guide for SoC Platform", code in drivers/input/misc/soc_array.c can
> not detect these buttons on it.
The comments below are all just style trivia
and can be ignored entirely.
> diff --git a/drivers/platform/x86/surfacepro3_button.c b/drivers/platform/x86/surfacepro3_button.c
[]
> +#define handle_surface_button_notify(type, code) \
> +({ \
> + int ret = 0; \
> + if (SURFACE_BUTTON_NOTIFY_PRESS_##type == event) \
> + pressed = true; \
> + if (pressed || \
> + (SURFACE_BUTTON_NOTIFY_RELEASE_##type == event)) { \
> + key_code = code; \
> + ret = 1; \
> + } else \
> + ret = 0; \
> + ret; \
> +})
This seems a bit complicated.
The else ret = 0 isn't necessary as it's initialized to 0.
bool might be better than int.
> +static void surface_button_notify(struct acpi_device *device, u32 event)
> +{
> + struct surface_button *button = acpi_driver_data(device);
> + struct input_dev *input;
> + int key_code = KEY_RESERVED;
> + bool pressed = false;
> +
> + if (!handle_surface_button_notify(POWER, KEY_POWER) &&
> + !handle_surface_button_notify(HOME, KEY_LEFTMETA) &&
> + !handle_surface_button_notify(VOLUME_UP, KEY_VOLUMEUP) &&
> + !handle_surface_button_notify(VOLUME_DOWN, KEY_VOLUMEDOWN))
> + dev_info_ratelimited(&device->dev,
> + "Unsupported event [0x%x]\n", event);
Some might prefer alignment to the open parenthesis:
if (!handle_surface_button_notify(POWER, KEY_POWER) &&
!handle_surface_button_notify(HOME, KEY_LEFTMETA) &&
!handle_surface_button_notify(VOLUME_UP, KEY_VOLUMEUP) &&
!handle_surface_button_notify(VOLUME_DOWN, KEY_VOLUMEDOWN))
I think the older switch/case was easier to understand.
next prev parent reply other threads:[~2015-08-07 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 7:57 Chen Yu
2015-08-07 8:27 ` Joe Perches [this message]
2015-08-07 8:48 ` Chen, Yu C
2015-08-11 2:45 ` Darren Hart
2015-08-18 1:42 ` Yu Chen
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=1438936078.2322.29.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=mika.westerberg@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rui.zhang@intel.com \
--cc=yu.c.chen@intel.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
Powered by JetHome