From: Rob Herring <robh@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
devicetree@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Claudiu Beznea <claudiu.beznea@microchip.com>
Subject: Re: [PATCH] dt-bindings: pinctrl: Allow values for drive-push-pull and drive-open-drain
Date: Wed, 4 May 2022 16:18:29 -0500 [thread overview]
Message-ID: <YnLtpd639JgU5RKF@robh.at.kernel.org> (raw)
In-Reply-To: <20220429194610.2741437-1-robh@kernel.org>
On Fri, 29 Apr 2022 14:46:11 -0500, Rob Herring wrote:
> A few platforms, at91 and tegra, use drive-push-pull and
> drive-open-drain with a 0 or 1 value. There's not really a need for values
> as '1' should be equivalent to no value (it wasn't treated that way) and
> drive-push-pull disabled is equivalent to drive-open-drain. So dropping the
> value can't be done without breaking existing OSs. As we don't want new
> cases, mark the case with values as deprecated.
>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Thierry Reding <thierry.reding@gmail.com>
> Cc: Jonathan Hunter <jonathanh@nvidia.com>
> Cc: Nicolas Ferre <nicolas.ferre@microchip.com>
> Cc: Claudiu Beznea <claudiu.beznea@microchip.com>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> .../devicetree/bindings/pinctrl/pincfg-node.yaml | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2022-05-04 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 19:46 [PATCH] dt-bindings: pinctrl: Allow values for drive-push-pull and drive-open-drain Rob Herring
2022-05-04 21:18 ` Rob Herring [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=YnLtpd639JgU5RKF@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=thierry.reding@gmail.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).