mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	Linus Walleij <linus.walleij@stericsson.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] gpiolib: wm8994: Pay attention to the value set when enabling as output
Date: Thu, 7 Jun 2012 22:53:05 +0100	[thread overview]
Message-ID: <20120607215305.GA19760@sirena.org.uk> (raw)
In-Reply-To: <CACRpkdY379kHbaMhGD4Q9y=Nkv2NPey+n1zUuTLAE-j7f8gadA@mail.gmail.com>

On Thu, Jun 07, 2012 at 01:11:20PM +0200, Linus Walleij wrote:
> <broonie@opensource.wolfsonmicro.com> wrote:

> > + ? ? ? if (value)
> > + ? ? ? ? ? ? ? value = WM8994_GPN_LVL;

> > ? ? ? ?return wm8994_set_bits(wm8994, WM8994_GPIO_1 + offset,
> > - ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?WM8994_GPN_DIR, 0);
> > + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?WM8994_GPN_DIR | WM8994_GPN_LVL, value);
> > ?}

> The commit message is so terse compared to what the code does that
> I cannot claim to understand what this patch is doing.

> Could you elaborate on the problem ans symptoms, just for a nice
> commit log?

I'm not really sure what more there is to say...  previously we were
ignoring the value that's set as part of setting output mode so if
someone wanted to set a value different to the one the chip happened to
have that wouldn't happen.  Ignoring the vaue that the user is trying to
set seems like an obvious enough bug in itself.

  reply	other threads:[~2012-06-07 21:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 17:12 Mark Brown
2012-06-07 11:11 ` Linus Walleij
2012-06-07 21:53   ` Mark Brown [this message]
2012-06-08  8:57     ` Linus Walleij
2012-06-09  3:07 Mark Brown
2012-06-11 20:51 ` Linus Walleij
2012-07-05 12:45 ` Linus Walleij

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=20120607215305.GA19760@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®