All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <syrjala@sci.fi>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Daniel Mack <daniel@caiaq.de>,
	linux-kernel@vger.kernel.org, johnpol@2ka.mipt.ru,
	david-b@pacbell.net
Subject: Re: [PATCH] drivers/w1/masters/w1-gpio.c: fix read_bit()
Date: Wed, 11 Mar 2009 01:59:29 +0200	[thread overview]
Message-ID: <20090310235929.GN10127@sci.fi> (raw)
In-Reply-To: <20090310150059.ce64548a.akpm@linux-foundation.org>

On Tue, Mar 10, 2009 at 03:00:59PM -0700, Andrew Morton wrote:
> On Tue, 10 Mar 2009 10:18:00 +0100
> Daniel Mack <daniel@caiaq.de> wrote:
> 
> > On Mon, Mar 09, 2009 at 07:14:19PM -0700, Andrew Morton wrote:
> > > > --- a/drivers/w1/masters/w1-gpio.c
> > > > +++ b/drivers/w1/masters/w1-gpio.c
> > > > @@ -39,7 +39,7 @@ static u8 w1_gpio_read_bit(void *data)
> > > >  {
> > > >  	struct w1_gpio_platform_data *pdata = data;
> > > >  
> > > > -	return gpio_get_value(pdata->pin);
> > > > +	return gpio_get_value(pdata->pin) ? 1 : 0;
> > > >  }
> > > >  
> > > >  static int __init w1_gpio_probe(struct platform_device *pdev)
> > > 
> > > We recently merged a patch (I forget where) which fixed one
> > > gpio_get_value() implementation so that it always returns 0 or 1.
> > > 
> > > From which I deduce that the correct fix for <whatever problem you're
> > > seeing> is to fix <whichever driver that is>?
> > 
> > I agree those functions should return 0 and 1 only, but my patch fixes
> > the w1-gpio driver for all platforms at once, so people can use it.
> > 
> > On the other hand, I will submit a patch which modifies PXA's
> > gpio_get_value() and see what the maintainers say, but I can't go thru
> > all the implemenations of all architectures to do this.
> > 
> > So for the time being, the above patch helps many users of that driver.
> > 
> 
> Problem is, the patch will just conceal bugs.
> 
> How about this?
> 
> --- a/drivers/w1/masters/w1-gpio.c~a
> +++ a/drivers/w1/masters/w1-gpio.c
> @@ -38,8 +38,12 @@ static void w1_gpio_write_bit_val(void *
>  static u8 w1_gpio_read_bit(void *data)
>  {
>  	struct w1_gpio_platform_data *pdata = data;
> +	u8 ret;
>  
> -	return gpio_get_value(pdata->pin);
> +	ret = gpio_get_value(pdata->pin);
> +	if (WARN_ONCE(ret > 1, "gpio_get_value(): invalid return: %u\n", ret))
> +		ret = !!ret
> +	return ret;
>  }
>  
>  static int __init w1_gpio_probe(struct platform_device *pdev)

I think if you want to go that route you should add such check into
gpiolib rather than some random driver.

-- 
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/

  reply	other threads:[~2009-03-10 23:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09 16:02 [PATCH] drivers/w1/masters/w1-gpio.c: fix read_bit() Daniel Mack
2009-03-10  2:14 ` Andrew Morton
2009-03-10  9:18   ` Daniel Mack
2009-03-10 22:00     ` Andrew Morton
2009-03-10 23:59       ` Ville Syrjälä [this message]
2009-03-11  0:10       ` Daniel Mack
2009-03-11  1:17         ` Andrew Morton
2009-03-10 14:13   ` Ville Syrjälä

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=20090310235929.GN10127@sci.fi \
    --to=syrjala@sci.fi \
    --cc=akpm@linux-foundation.org \
    --cc=daniel@caiaq.de \
    --cc=david-b@pacbell.net \
    --cc=johnpol@2ka.mipt.ru \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.