From: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Doug Anderson <dianders@chromium.org>,
Lee Jones <lee.jones@linaro.org>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] input: cros_ec_keyb: Add of match table
Date: Mon, 25 Aug 2014 09:34:10 +0200 [thread overview]
Message-ID: <1408952050.31096.5.camel@collabora.co.uk> (raw)
In-Reply-To: <53F89A52.60605@cogentembedded.com>
[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]
Hey,
On Sat, 2014-08-23 at 17:42 +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 8/23/2014 3:03 AM, Sjoerd Simons wrote:
>
> > To enable the cros_ec_keyb driver to be auto-loaded when build as
> > module add an of match table (and export it) to match the modalias
> > information passed on to userspace as the Cros EC MFD driver registers
> > the MFD subdevices with an of_compatibility string.
>
> > Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
> > ---
> > drivers/input/keyboard/cros_ec_keyb.c | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
>
> > diff --git a/drivers/input/keyboard/cros_ec_keyb.c b/drivers/input/keyboard/cros_ec_keyb.c
> > index 791781a..0bdbf2d 100644
> > --- a/drivers/input/keyboard/cros_ec_keyb.c
> > +++ b/drivers/input/keyboard/cros_ec_keyb.c
> > @@ -342,10 +342,20 @@ static int cros_ec_keyb_resume(struct device *dev)
> >
> > static SIMPLE_DEV_PM_OPS(cros_ec_keyb_pm_ops, NULL, cros_ec_keyb_resume);
> >
> > +#ifdef CONFIG_OF
> > +static const struct of_device_id cros_ec_keyb_of_match[] = {
> Perhaps better to use '__maybe_unused' instead of #ifdef...
Hmm, looks like the rtc-ds1742.c driver is the only one in the kernel
tree using that strategy, while all others use #ifdef CONFIG_OF. So i'm
inclined to keep the #ifdef here, ooi what is your rationale behind
suggesting __maybe_unused?
> > + { .compatible = "google,cros-ec-keyb" },
> > + {},
> > +};
> > +MODULE_DEVICE_TABLE(of, cros_ec_keyb_of_match);
> > +#endif
> > +
> > +
>
> Too many empty lines.
> > static struct platform_driver cros_ec_keyb_driver = {
> > .probe = cros_ec_keyb_probe,
> > .driver = {
> > .name = "cros-ec-keyb",
> > + .of_match_table = of_match_ptr (cros_ec_keyb_of_match),
>
> There shouldn't be space before (.
Will fix the identation issues in a v2.
Thanks for the review,
Sjoerd
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6170 bytes --]
next prev parent reply other threads:[~2014-08-25 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 23:03 [PATCH 0/2] Add of match tables for the ChromeOs EC subdevices Sjoerd Simons
2014-08-22 23:03 ` [PATCH 1/2] i2c: cros-ec-tunnel: Add of match table Sjoerd Simons
2014-08-25 9:37 ` Javier Martinez Canillas
2014-08-22 23:03 ` [PATCH 2/2] input: cros_ec_keyb: " Sjoerd Simons
2014-08-23 13:42 ` Sergei Shtylyov
2014-08-25 7:34 ` Sjoerd Simons [this message]
2014-08-25 9:33 ` Javier Martinez Canillas
-- strict thread matches above, loose matches on Subject: below --
2014-09-19 8:08 [PATCH 0/2 v2] Add OF match tables for the ChromeOs EC subdevices Sjoerd Simons
2014-09-19 8:08 ` [PATCH 2/2] input: cros_ec_keyb: Add of match table Sjoerd Simons
2014-10-08 18:39 ` Dmitry Torokhov
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=1408952050.31096.5.camel@collabora.co.uk \
--to=sjoerd.simons@collabora.co.uk \
--cc=dianders@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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