From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 1/1] iMX51: introduce MX51_GPIO_NR
Date: Wed, 24 Nov 2010 18:04:09 +0100 [thread overview]
Message-ID: <87zksywt4l.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <AANLkTi=Q=UOSUoJ40ThyyyDqMoC849W-cn36CkVFxKhQ@mail.gmail.com> (Fabio Estevam's message of "Wed, 24 Nov 2010 14:49:21 -0200")
Fabio Estevam <festevam@gmail.com> writes:
Hi,
> Hi Arnaud,
>
> 2010/11/22 Arnaud Patard <arnaud.patard@rtp-net.org>:
>> Currently, to define a GPIO number, we're using something like :
>>
>> #define EFIKAMX_PCBID0 ? ? ? ? (2*32 + 16)
>>
>> to define GPIO 3 16.
>>
>> This is not really readable and it's error prone imho (note the 3 vs 2).
>> So, I'm introducing a new macro to define this in a better way. Now, the
>> code sample become :
>>
>> #define EFIKAMX_PCBID0 ? ? ? ? MX51_GPIO_NR(3, 16)
>
> Can you rename the macro to MX5x_GPIO_NR instead of MX51_GPIO_NR?
>
> This way we can also use this macro for MX53 and MX508 when they show
> up in mainline.
I've been wondering about to use MX5X instead of MX51 but I kept MX51
because I didn't know how the GPIO will work on MX53. If they're
compatible, you're right, the name should be MX5X_GPIO_NR and not
MX51_GPIO_NR. Assuming you mail means that, I'm going to switch to
MX5X_GPIO_NR.
Arnaud
next prev parent reply other threads:[~2010-11-24 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 22:45 [patch 1/1] iMX51: introduce MX51_GPIO_NR Arnaud Patard (Rtp)
2010-11-24 5:21 ` Amit Kucheria
2010-11-24 7:46 ` Lothar Waßmann
2010-11-24 16:28 ` Arnaud Patard (Rtp)
2010-11-24 16:49 ` Fabio Estevam
2010-11-24 17:04 ` Arnaud Patard (Rtp) [this message]
2010-11-24 23:06 ` Richard Zhao
2010-11-25 8:24 ` Sascha Hauer
2010-11-25 8:52 ` Sascha Hauer
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=87zksywt4l.fsf@lechat.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--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;
as well as URLs for NNTP newsgroup(s).