From: Stephen Warren <swarren@wwwdotorg.org>
To: Roland Stigge <stigge@antcom.de>
Cc: broonie@opensource.wolfsonmicro.com, cjb@laptop.org,
grant.likely@secretlab.ca, rob.herring@calxeda.com,
rmk+kernel@arm.linux.org.uk, ulf.hansson@stericsson.com,
linus.walleij@linaro.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, aletes.xgr@gmail.com,
linux-arm-kernel@lists.infradead.org, lrg@ti.com, perex@perex.cz,
tiwai@suse.de, alsa-devel@alsa-project.org
Subject: Re: [PATCH] sound/gpio: of_get_named_gpio() return -EPROBE_DEFER if GPIO deferred
Date: Mon, 18 Jun 2012 11:26:28 -0600 [thread overview]
Message-ID: <4FDF64C4.8060308@wwwdotorg.org> (raw)
In-Reply-To: <1340040176-16553-1-git-send-email-stigge@antcom.de>
On 06/18/2012 11:22 AM, Roland Stigge wrote:
> of_get_named_gpio_flags() and of_get_named_gpio() return -EPROBE_DEFER if the
> respective GPIO is not (yet) available. This is useful if driver's probe()
> functions try to get a GPIO whose controller isn't probed yet. Thus, the driver
> can be probed again later on.
>
> The function still returns -EINVAL on other errors (parse error or node doesn't
> exist). This way, the case of an optional/intentionally missing GPIO is handled
> appropriately.
>
> For this change, two sound drivers (tegra_{alc5632,wm8903}) need to be
> adjusted.
Acked-by: Stephen Warren <swarren@wwwdotorg.org>
(That applies to the two separate sound patches too, if needed!)
next prev parent reply other threads:[~2012-06-18 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 17:22 [PATCH] sound/gpio: of_get_named_gpio() return -EPROBE_DEFER if GPIO deferred Roland Stigge
2012-06-18 17:26 ` Stephen Warren [this message]
2012-06-18 17:29 ` Alexandre Pereira da Silva
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=4FDF64C4.8060308@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=aletes.xgr@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cjb@laptop.org \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lrg@ti.com \
--cc=perex@perex.cz \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rob.herring@calxeda.com \
--cc=stigge@antcom.de \
--cc=tiwai@suse.de \
--cc=ulf.hansson@stericsson.com \
/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