From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] gpio: omap_gpio: Fix valid gpio range for AM33XX
Date: Thu, 20 Jun 2013 21:42:01 +0200 [thread overview]
Message-ID: <201306202142.01999.marex@denx.de> (raw)
In-Reply-To: <51C3241E.2070709@denx.de>
Dear Stefan Roese,
> On 20.06.2013 17:26, Axel Lin wrote:
> > AM33XX has 4 gpio banks, thus the valid gpio range should be 0 ... 127.
> >
> > Signed-off-by: Axel Lin <axel.lin@ingics.com>
> > ---
> >
> > drivers/gpio/omap_gpio.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/drivers/gpio/omap_gpio.c b/drivers/gpio/omap_gpio.c
> > index a30d7f0..9aa6d41 100644
> > --- a/drivers/gpio/omap_gpio.c
> > +++ b/drivers/gpio/omap_gpio.c
> > @@ -55,7 +55,11 @@ static inline int get_gpio_index(int gpio)
> >
> > int gpio_is_valid(int gpio)
> > {
> >
> > +#if defined(CONFIG_AM33XX)
> > + return (gpio >= 0) && (gpio < 128);
> > +#else
> >
> > return (gpio >= 0) && (gpio < 192);
> >
> > +#endif
> >
> > }
>
> Those ifdef's in the code really ugly and frowned upon. Better would be
> to move this into a define in the top of the C file:
>
> #if defined(CONFIG_AM33XX)
> #define CONFIG_OMAP_MAX_GPIO 128
> #else
> #define CONFIG_OMAP_MAX_GPIO 192
> #endif
>
> And then use this define in the code:
>
> return (gpio >= 0) && (gpio < CONFIG_OMAP_MAX_GPIO);
>
> Thanks,
> Stefan
You were faster ;-) and I agree with this method.
Best regards,
Marek Vasut
prev parent reply other threads:[~2013-06-20 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 15:26 [U-Boot] [PATCH] gpio: omap_gpio: Fix valid gpio range for AM33XX Axel Lin
2013-06-20 15:35 ` Tom Rini
2013-06-20 15:47 ` Stefan Roese
2013-06-20 19:42 ` Marek Vasut [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=201306202142.01999.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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