From: Florian Fainelli <florian@openwrt.org>
To: Jamie Iles <jamie@jamieiles.com>
Cc: Wim Van Sebroeck <wim@iguana.be>,
linux-mips@linux-mips.org, linux-watchdog@vger.kernel.org,
Manuel Lauss <manuel.lauss@googlemail.com>,
stable@kernel.org
Subject: Re: [PATCH 2/3] WATCHDOG: mtx1-wdt: request gpio before using it
Date: Fri, 10 Jun 2011 17:34:34 +0200 [thread overview]
Message-ID: <201106101734.35048.florian@openwrt.org> (raw)
In-Reply-To: <20110607095847.GB21174@pulham.picochip.com>
Hello Jamie,
On Tuesday 07 June 2011 11:58:47 Jamie Iles wrote:
> On Thu, Jun 02, 2011 at 02:54:20PM +0200, Florian Fainelli wrote:
> > Otherwise, the gpiolib autorequest feature will produce a WARN_ON():
> >
> > WARNING: at drivers/gpio/gpiolib.c:101 0x8020ec6c()
> > autorequest GPIO-215
> > [...]
> >
> > CC: stable@kernel.org
> > Signed-off-by: Florian Fainelli <florian@openwrt.org>
> > ---
> > diff --git a/drivers/watchdog/mtx-1_wdt.c b/drivers/watchdog/mtx-1_wdt.c
> > index 63df28c..16086f8 100644
> > --- a/drivers/watchdog/mtx-1_wdt.c
> > +++ b/drivers/watchdog/mtx-1_wdt.c
> > @@ -214,6 +214,11 @@ static int __devinit mtx1_wdt_probe(struct
> > platform_device *pdev)
> >
> > int ret;
> >
> > mtx1_wdt_device.gpio = pdev->resource[0].start;
> >
> > + ret = gpio_request(mtx1_wdt_device.gpio, "mtx1-wdt");
> > + if (ret < 0) {
> > + dev_err(&pdev->dev, "failed to request gpio");
> > + return ret;
> > + }
>
> Could you use gpio_request_one() here to make sure the GPIO is in the
> correct direction first?
Makes sense, I will respin a v2 of these.
--
Florian
prev parent reply other threads:[~2011-06-10 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 12:54 [PATCH 2/3] WATCHDOG: mtx1-wdt: request gpio before using it Florian Fainelli
2011-06-07 9:58 ` Jamie Iles
2011-06-10 15:34 ` Florian Fainelli [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=201106101734.35048.florian@openwrt.org \
--to=florian@openwrt.org \
--cc=jamie@jamieiles.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=manuel.lauss@googlemail.com \
--cc=stable@kernel.org \
--cc=wim@iguana.be \
/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