From: Linus Walleij <linus.walleij@linaro.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Frank Rowand <frowand.list@gmail.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Marek Vasut <marek.vasut@gmail.com>
Subject: Re: [PATCH 1/4] dt-bindings: gpio: document the new pull-up/pull-down flags
Date: Fri, 11 Jan 2019 10:57:09 +0100 [thread overview]
Message-ID: <CACRpkdafckngrTPuSJggmZdJsWNz6ASeQeLu2aTTmpw-fySBOA@mail.gmail.com> (raw)
In-Reply-To: <20190103164102.31437-2-thomas.petazzoni@bootlin.com>
On Thu, Jan 3, 2019 at 5:41 PM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
> This commit extends the flags that can be used in GPIO specifiers to
> indicate if a pull-up resistor or pull-down resistor should be
> enabled.
>
> While some pinctrl DT bindings already offer the capability of
> configuring pull-up/pull-down resistors at the pin level, a number of
> simple GPIO controllers don't have any pinmuxing capability, and
> therefore do not rely on the pinctrl DT bindings.
>
> Such simple GPIO controllers however sometimes allow to configure
> pull-up and pull-down resistors on a per-pin basis, and whether such
> resistors should be enabled or not is a highly board-specific HW
> characteristic.
>
> By using two additional bits of the GPIO flag specifier, we can easily
> allow the Device Tree to describe which GPIOs should have their
> pull-up or pull-down resistors enabled. Even though the two options
> are mutually exclusive, we still need two bits to encode at least
> three states: no pull-up/pull-down, pull-up, pull-down.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> Documentation/devicetree/bindings/gpio/gpio.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/gpio/gpio.txt b/Documentation/devicetree/bindings/gpio/gpio.txt
> index f0ba154b5723..03d8adf67c16 100644
> --- a/Documentation/devicetree/bindings/gpio/gpio.txt
> +++ b/Documentation/devicetree/bindings/gpio/gpio.txt
> @@ -67,6 +67,10 @@ Optional standard bitfield specifiers for the last cell:
> https://en.wikipedia.org/wiki/Open_collector
> - Bit 3: 0 means the output should be maintained during sleep/low-power mode
> 1 means the output state can be lost during sleep/low-power mode
> +- Bit 4: 0 means no pull-up resistor should be enabled
> + 1 means a pull-up resistor should be enabled
> +- Bit 5: 0 means no pull-down resistor should be enabled
> + 1 means a pull-down resistor should be enabled
As per the commit message this should be more verbose IMO,
add something like "this setting will only apply to hardware
with a simple on/off approach to pull up/down: if the hardware
has more elaborate pull up/down settings such as specifying a
specific resistance, the driver should use pin control bindings.
Yours,
Linus Walleij
next prev parent reply other threads:[~2019-01-11 9:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 16:40 [PATCH 0/4] Proposal to support pull-up/pull-down GPIO configuration Thomas Petazzoni
2019-01-03 16:40 ` [PATCH 1/4] dt-bindings: gpio: document the new pull-up/pull-down flags Thomas Petazzoni
2019-01-11 9:57 ` Linus Walleij [this message]
2019-01-03 16:41 ` [PATCH 2/4] gpio: rename gpio_set_drive_single_ended() to gpio_set_config() Thomas Petazzoni
2019-01-11 10:01 ` Linus Walleij
2019-01-03 16:41 ` [PATCH 3/4] gpio: add core support for pull-up/pull-down configuration Thomas Petazzoni
2019-01-08 14:00 ` Jan Kundrát
2019-01-08 14:04 ` Thomas Petazzoni
2019-01-11 10:11 ` Linus Walleij
2019-01-11 10:05 ` Linus Walleij
2019-01-11 12:58 ` Thomas Petazzoni
2019-01-11 14:38 ` Linus Walleij
2019-01-11 16:41 ` Rob Herring
2019-01-03 16:41 ` [PATCH 4/4] gpio: pca953x: add ->set_config implementation Thomas Petazzoni
2019-01-11 10:14 ` Linus Walleij
2019-02-07 14:44 ` Thomas Petazzoni
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=CACRpkdafckngrTPuSJggmZdJsWNz6ASeQeLu2aTTmpw-fySBOA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).