From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 04/10] pinctrl: check pinctrl ready for gpio range
Date: Fri, 1 Mar 2013 13:53:27 +0100 [thread overview]
Message-ID: <CACRpkda0Qt8qsJHGBCmRM1dRqhQSZcBY-ujCeKNJOpzvm2TraQ@mail.gmail.com> (raw)
In-Reply-To: <1361101376-3783-5-git-send-email-haojian.zhuang@linaro.org>
On Sun, Feb 17, 2013 at 12:42 PM, Haojian Zhuang
<haojian.zhuang@linaro.org> wrote:
> pinctrl_get_device_gpio_range() only checks whether a certain GPIO pin
> is in gpio range. But maybe some GPIO pins don't have back-end pinctrl
> interface, it means that these pins are always configured as GPIO
> function. For example, gpio159 isn't related to back-end pinctrl device
> in Hi3620 while other GPIO pins are related to back-end pinctrl device.
>
> Append pinctrl_ready_for_gpio_range() that is used to check whether
> pinctrl device with GPIO range is ready. This function will be called
> after pinctrl_get_device_gpio_range() fails.
>
> If pinctrl device with GPIO range is found, it means that pinctrl device
> is already launched and a certain GPIO pin just don't have back-end pinctrl
> interface. Then pinctrl_request_gpio() shouldn't return -EPROBE_DEFER in
> this case.
>
> Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org>
Patch applied to the pinctrl tree for v3.10.
Thanks,
Linus Walleij
next prev parent reply other threads:[~2013-03-01 12:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 11:42 [PATCH v9 00/10] bind pinconf to pinctrl single Haojian Zhuang
2013-02-17 11:42 ` [PATCH v9 01/10] gpio: add gpio offset in gpio range cells property Haojian Zhuang
2013-03-01 12:43 ` Linus Walleij
2013-02-17 11:42 ` [PATCH v9 02/10] gpio: fix wrong checking condition for gpio range Haojian Zhuang
2013-03-01 12:45 ` Linus Walleij
2013-02-17 11:42 ` [PATCH v9 03/10] gpio: pl061: support irqdomain Haojian Zhuang
2013-03-01 12:48 ` Linus Walleij
2013-02-17 11:42 ` [PATCH v9 04/10] pinctrl: check pinctrl ready for gpio range Haojian Zhuang
2013-03-01 12:53 ` Linus Walleij [this message]
2013-02-17 11:42 ` [PATCH v9 05/10] gpio: pl061: bind pinctrl by gpio request Haojian Zhuang
2013-03-01 12:54 ` Linus Walleij
2013-02-17 11:42 ` [PATCH v9 06/10] pinctrl: single: create new gpio function range Haojian Zhuang
2013-03-01 12:57 ` Linus Walleij
2013-02-17 11:42 ` [PATCH v9 07/10] pinctrl: generic: dump pin configuration Haojian Zhuang
2013-03-01 12:59 ` Linus Walleij
2013-02-17 11:42 ` [PATCH v9 08/10] pinctrl: single: set function mask as optional Haojian Zhuang
2013-03-01 13:00 ` Linus Walleij
2013-02-17 11:42 ` [PATCH v9 09/10] pinctrl: single: support generic pinconf Haojian Zhuang
2013-03-01 13:03 ` Linus Walleij
2013-02-17 11:42 ` [PATCH v9 10/10] document: devicetree: bind pinconf with pin single Haojian Zhuang
2013-03-01 13:04 ` 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=CACRpkda0Qt8qsJHGBCmRM1dRqhQSZcBY-ujCeKNJOpzvm2TraQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).