From: Michael Buesch <mb@bu3sch.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: openwrt-devel@lists.openwrt.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bcm47xx: Fix GPIO API return codes
Date: Wed, 18 Feb 2009 01:52:16 +0100 [thread overview]
Message-ID: <200902180152.16346.mb@bu3sch.de> (raw)
In-Reply-To: <20090217162918.d88bc543.akpm@linux-foundation.org>
On Wednesday 18 February 2009 01:29:18 Andrew Morton wrote:
> On Sat, 14 Feb 2009 21:27:19 +0100
> Michael Buesch <mb@bu3sch.de> wrote:
>
> > The GPIO API is supposed to return 0 or a negative error code,
> > but the SSB GPIO functions return the bitmask of the GPIO register.
> > Fix this by ignoring the bitmask and always returning 0. The SSB GPIO functions can't fail.
> >
> > Signed-off-by: Michael Buesch <mb@bu3sch.de>
> >
> > ---
> >
> > Index: linux-2.6/arch/mips/include/asm/mach-bcm47xx/gpio.h
> > ===================================================================
> > --- linux-2.6.orig/arch/mips/include/asm/mach-bcm47xx/gpio.h 2009-01-01 19:27:06.000000000 +0100
> > +++ linux-2.6/arch/mips/include/asm/mach-bcm47xx/gpio.h 2009-02-14 21:26:14.000000000 +0100
> > @@ -31,24 +31,28 @@ static inline void gpio_set_value(unsign
> >
> > static inline int gpio_direction_input(unsigned gpio)
> > {
> > - return ssb_gpio_outen(&ssb_bcm47xx, 1 << gpio, 0);
> > + ssb_gpio_outen(&ssb_bcm47xx, 1 << gpio, 0);
> > + return 0;
> > }
> >
> > static inline int gpio_direction_output(unsigned gpio, int value)
> > {
> > - return ssb_gpio_outen(&ssb_bcm47xx, 1 << gpio, 1 << gpio);
> > + ssb_gpio_outen(&ssb_bcm47xx, 1 << gpio, 1 << gpio);
> > + return 0;
> > }
> >
> > -static int gpio_intmask(unsigned gpio, int value)
> > +static inline int gpio_intmask(unsigned gpio, int value)
> > {
> > - return ssb_gpio_intmask(&ssb_bcm47xx, 1 << gpio,
> > - value ? 1 << gpio : 0);
> > + ssb_gpio_intmask(&ssb_bcm47xx, 1 << gpio,
> > + value ? 1 << gpio : 0);
> > + return 0;
> > }
> >
> > -static int gpio_polarity(unsigned gpio, int value)
> > +static inline int gpio_polarity(unsigned gpio, int value)
> > {
> > - return ssb_gpio_polarity(&ssb_bcm47xx, 1 << gpio,
> > - value ? 1 << gpio : 0);
> > + ssb_gpio_polarity(&ssb_bcm47xx, 1 << gpio,
> > + value ? 1 << gpio : 0);
> > + return 0;
> > }
>
> What are the consequences of the bug which you fixed? User-visible
> runtime failures? Something else?
>
> Please always include this information in the changelogs - without it I
> cannot make which-kernel-needs-this decisions.
Well, it fixes all users of the API that don't ignore the return value.
"Fixes" means "turns them from completely not working at all into - working properly".
This is the case for gpio-spi, for example. gpio-spi doesn't work on bcm47xx without
this fix. gpio-spi is in 2.6.29.
I didn't search for other API-users that might be broken.
So I'd like to see this going to Linus as soon as possible.
--
Greetings, Michael.
prev parent reply other threads:[~2009-02-18 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 20:27 [PATCH] bcm47xx: Fix GPIO API return codes Michael Buesch
2009-02-15 13:27 ` [OpenWrt-Devel] " Florian Fainelli
2009-02-15 14:22 ` Michael Buesch
2009-02-18 0:29 ` Andrew Morton
2009-02-18 0:52 ` Michael Buesch [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=200902180152.16346.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openwrt-devel@lists.openwrt.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