From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] pinmux: add a driver for the CSR SiRFprimaII pinmux
Date: Sat, 08 Oct 2011 15:08:27 +0200 [thread overview]
Message-ID: <3712698.4MAZQPafzW@wuerfel> (raw)
In-Reply-To: <CAGsJ_4xpYMzHGi09jt2Y9xCocYJ0iHYRfdvwCzcH65uaF2sP0g@mail.gmail.com>
On Saturday 08 October 2011 19:58:23 Barry Song wrote:
> > You can probably simplify this and other things with
> > preprocessor macros if you want to, like:
> >
> > #define SIRF_FUNC_ENTRY(a) \
> > { .name = "##a##", .pins = ##a##_pins, .num_pins =
> > ARRAY_SIZE(##a##_pins), .padmux = &##a##_padmux }
> >
> > Then just:
> >
> > static const struct sirfsoc_pinmux_func sirfsoc_pinmux_funcs[] = {
> > SIRF_FUNC_ENTRY(lcd_16bits),
> >
> >
> > The macro syntax is probably wrong, the preprocessor always
> > craze me out, but you get the idea.
>
> :-) .name = "##a##" should be changed to .name = #a
>
> #name will convert name into a string "name"
>
Better don't use string concatenation at all if you can avoid it.
A generic macro like
#define SIRF_PINMUX(_name, _pins, _padmux) \
{ .name = (_name), .pins = (_pins), \
.num_pins = ARRAY_SIZE(_pins), padmux = (_padmux), }
is both very easy to understand for someone reading it casually and
lets you actually grep for where the identifiers are being used.
> static const struct sirfsoc_pinmux_func sirfsoc_pinmux_funcs[] = {
> SIRF_FUNC_ENTRY(lcd_16bits),
for the first time, you have no clue what that does, but
static const struct sirfsoc_pinmux_func sirfsoc_pinmux_funcs[] = {
SIRF_PINMUX("lcd_16bits", lcd_16bits_pins, &lcd_16bits_padmux),
...
};
Makes it very clear what you are referencing here and needs no extra lines.
Arnd
next prev parent reply other threads:[~2011-10-08 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 2:22 [PATCH v2] pinmux: add a driver for the CSR SiRFprimaII pinmux Barry Song
2011-09-01 11:12 ` Linus Walleij
2011-09-01 11:35 ` Barry Song
2011-10-08 11:58 ` Barry Song
2011-10-08 13:08 ` Arnd Bergmann [this message]
2011-10-09 5:39 ` Barry Song
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=3712698.4MAZQPafzW@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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