From: Rob Herring <robh@kernel.org>
To: Samuel Holland <samuel@sholland.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-sunxi@lists.linux.dev,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Andre Przywara <andre.przywara@arm.com>,
Maxime Ripard <mripard@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
linux-gpio@vger.kernel.org, Chen-Yu Tsai <wens@csie.org>
Subject: Re: [PATCH 3/3] dt-bindings: pinctrl: sunxi: Disallow the resets property
Date: Sun, 5 Jun 2022 16:25:56 -0500 [thread overview]
Message-ID: <20220605212556.GA3545625-robh@kernel.org> (raw)
In-Reply-To: <20220531053623.43851-4-samuel@sholland.org>
On Tue, 31 May 2022 00:36:23 -0500, Samuel Holland wrote:
> None of the sunxi pin controllers have a module reset line. This is
> confirmed by documentation (A80) as well as experimentation (A33).
>
> Since the property is not applicable to any variant of the hardware,
> let's remove it from the binding.
>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
> ---
>
> .../bindings/pinctrl/allwinner,sun4i-a10-pinctrl.yaml | 3 ---
> 1 file changed, 3 deletions(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-06-05 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 5:36 [PATCH 0/3] pinctrl: sunxi: Remove non-existent reset line references Samuel Holland
2022-05-31 5:36 ` [PATCH 1/3] pinctrl: sunxi: Remove reset controller consumers Samuel Holland
2022-05-31 5:36 ` [PATCH 2/3] ARM: dts: sunxi: Drop resets from r_pio nodes Samuel Holland
2022-05-31 5:36 ` [PATCH 3/3] dt-bindings: pinctrl: sunxi: Disallow the resets property Samuel Holland
2022-06-05 21:25 ` Rob Herring [this message]
2022-05-31 15:22 ` [PATCH 0/3] pinctrl: sunxi: Remove non-existent reset line references Jernej Škrabec
2022-06-01 4:42 ` Samuel Holland
2022-06-01 15:24 ` Jernej Škrabec
2022-06-15 13:26 ` 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=20220605212556.GA3545625-robh@kernel.org \
--to=robh@kernel.org \
--cc=andre.przywara@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.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).