From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: devicetree@vger.kernel.org,
Chris Brandt <chris.brandt@renesas.com>,
linux-gpio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Jacopo Mondi <jacopo+renesas@jmondi.org>
Subject: Re: [PATCH] pinctrl: rza1: Switch to using "output-enable"
Date: Tue, 8 Sep 2020 14:53:23 -0600 [thread overview]
Message-ID: <20200908205323.GA900491@bogus> (raw)
In-Reply-To: <20200821111401.4021-1-geert+renesas@glider.be>
On Fri, 21 Aug 2020 13:14:01 +0200, Geert Uytterhoeven wrote:
> For pins requiring software driven IO output operations, the RZ/A1 Pin
> Controller uses either the "output-high" or "output-low" DT property to
> enable the corresponding output buffer. The actual line value doesn't
> matter, as it is ignored.
>
> Commit 425562429d4f3b13 ("pinctrl: generic: Add output-enable property")
> introduced a new DT property for this specific use case.
>
> Update the RZ/A1 Pin Controller DT bindings and driver to use this new
> property instead. Preserve backwards compatibility with old DTBs in the
> driver, as this comes at a very small cost.
>
> Notes:
> - The DT binding examples already used the new property,
> - There are no upstream users of the old properties.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> To be queued in sh-pfc for v5.10.
>
> .../devicetree/bindings/pinctrl/renesas,rza1-pinctrl.txt | 5 ++---
> drivers/pinctrl/pinctrl-rza1.c | 3 ++-
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
Acked-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2020-09-08 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 11:14 [PATCH] pinctrl: rza1: Switch to using "output-enable" Geert Uytterhoeven
2020-08-21 12:02 ` Chris Brandt
2020-08-24 8:30 ` Jacopo Mondi
2020-08-25 7:10 ` Geert Uytterhoeven
2020-09-08 20:53 ` 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=20200908205323.GA900491@bogus \
--to=robh@kernel.org \
--cc=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jacopo+renesas@jmondi.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.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).