From: Grant Likely <grant.likely@secretlab.ca>
To: Simon Horman <horms@verge.net.au>, Magnus Damm <magnus.damm@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org, linus.walleij@linaro.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] gpio: em: Add Device Tree support
Date: Sat, 02 Mar 2013 20:07:32 +0000 [thread overview]
Message-ID: <20130302200732.E18BB3E206B@localhost> (raw)
In-Reply-To: <20130228051122.GA12312@verge.net.au>
On Thu, 28 Feb 2013 14:11:23 +0900, Simon Horman <horms@verge.net.au> wrote:
> On Wed, Feb 27, 2013 at 07:13:46PM +0900, Magnus Damm wrote:
> > Hi Dmitry,
> >
> > Thanks for your feedback!
> >
> > On Wed, Feb 27, 2013 at 7:41 AM, Dmitry Torokhov
> > <dmitry.torokhov@gmail.com> wrote:
> > > Hi Magnus,
> > >
> > > On Tue, Feb 26, 2013 at 10:26:23PM +0900, Magnus Damm wrote:
> > >> From: Magnus Damm <damm@opensource.se>
> > >>
> > >> Update the Emma Mobile GPIO driver to add DT support.
> > >>
> > >
> > > ...
> > >
> > >> @@ -366,15 +387,33 @@ static int em_gio_remove(struct platform
> > >> return 0;
> > >> }
> > >>
> > >
> > > #ifdef CONFIG_OF here? No need to have extra aliases in modules if OF
> > > support is not enabled (or is entire ARM arch now enables device tree?).
> > >
> > >> +static const struct of_device_id em_gio_dt_ids[] = {
> > >> + { .compatible = "renesas,em-gio", },
> > >> + {},
> > >> +};
> > >> +MODULE_DEVICE_TABLE(of, em_gio_dt_ids);
> > >> +
> >
> > I suppose we could sprinkle a couple of #ifdefs across the code, but I
> > have to say that I'm not that fond of #ifdefs in general. So if it was
> > up to me only then I would aim at having exactly zero #ifdefs in my
> > drivers at the expense of slightly larger binaries in some cases.
>
> My take on this is as follows (if anyone cares):
>
> * The driver in question is currently only useful in conjunction with
> the Emev2 SoC and the kzm9g board which uses that SoC. The current
> (and to date only) practice when booting that board and thus SoC
> with merged upstream code is to do so using DT.
>
> * The inclusion of the code above does not appear to cause build-time
> breakage even if CONFIG_OF is not set.
>
> So it seems to me that it is reasonable to leave the code as is
> without being guarded by an #ifdef.
I completely agree. Applied for v3.10
g.
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies, Ltd.
prev parent reply other threads:[~2013-03-03 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 13:26 [PATCH] gpio: em: Add Device Tree support Magnus Damm
2013-02-26 22:41 ` Dmitry Torokhov
2013-02-27 10:13 ` Magnus Damm
2013-02-28 5:11 ` Simon Horman
2013-03-02 20:07 ` Grant Likely [this message]
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=20130302200732.E18BB3E206B@localhost \
--to=grant.likely@secretlab.ca \
--cc=dmitry.torokhov@gmail.com \
--cc=horms@verge.net.au \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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;
as well as URLs for NNTP newsgroup(s).