From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: "Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Richard Cochran" <richardcochran@gmail.com>,
"Gregory CLEMENT" <gregory.clement@bootlin.com>,
"Marek Behún" <kabel@kernel.org>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: pinctrl: Convert marvell,armada-3710-(sb|nb)-pinctrl to DT schema
Date: Mon, 29 Sep 2025 17:43:04 +0200 [thread overview]
Message-ID: <87ms6di7sn.fsf@bootlin.com> (raw)
In-Reply-To: <20250924223528.2956771-1-robh@kernel.org> (Rob Herring's message of "Wed, 24 Sep 2025 17:35:24 -0500")
On 24/09/2025 at 17:35:24 -05, "Rob Herring (Arm)" <robh@kernel.org> wrote:
> Convert the marvell,armada3710-(sb|nb)-pinctrl binding to DT schema
> format. The binding includes the "marvell,armada-3700-xtal-clock"
> subnode which is simple enough to include here.
>
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---
> .../bindings/clock/armada3700-xtal-clock.txt | 29 ---
> .../marvell,armada-3710-xb-pinctrl.yaml | 122 +++++++++++
> .../pinctrl/marvell,armada-37xx-pinctrl.txt | 195 ------------------
> 3 files changed, 122 insertions(+), 224 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/clock/armada3700-xtal-clock.txt
> create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,armada-3710-xb-pinctrl.yaml
> delete mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,armada-37xx-pinctrl.txt
>
> diff --git a/Documentation/devicetree/bindings/clock/armada3700-xtal-clock.txt b/Documentation/devicetree/bindings/clock/armada3700-xtal-clock.txt
> deleted file mode 100644
> index 4c0807f28cfa..000000000000
> --- a/Documentation/devicetree/bindings/clock/armada3700-xtal-clock.txt
> +++ /dev/null
> @@ -1,29 +0,0 @@
> -* Xtal Clock bindings for Marvell Armada 37xx SoCs
> -
> -Marvell Armada 37xx SoCs allow to determine the xtal clock frequencies by
> -reading the gpio latch register.
> -
> -This node must be a subnode of the node exposing the register address
> -of the GPIO block where the gpio latch is located.
> -See Documentation/devicetree/bindings/pinctrl/marvell,armada-37xx-pinctrl.txt
> -
> -Required properties:
> -- compatible : shall be one of the following:
> - "marvell,armada-3700-xtal-clock"
> -- #clock-cells : from common clock binding; shall be set to 0
> -
> -Optional properties:
> -- clock-output-names : from common clock binding; allows overwrite default clock
> - output names ("xtal")
> -
> -Example:
> -pinctrl_nb: pinctrl-nb@13800 {
> - compatible = "armada3710-nb-pinctrl", "syscon", "simple-mfd";
> - reg = <0x13800 0x100>, <0x13C00 0x20>;
> -
> - xtalclk: xtal-clk {
> - compatible = "marvell,armada-3700-xtal-clock";
> - clock-output-names = "xtal";
> - #clock-cells = <0>;
> - };
> -};
> diff --git a/Documentation/devicetree/bindings/pinctrl/marvell,armada-3710-xb-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/marvell,armada-3710-xb-pinctrl.yaml
> new file mode 100644
> index 000000000000..c4d09d8720bd
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/marvell,armada-3710-xb-pinctrl.yaml
> @@ -0,0 +1,122 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/pinctrl/marvell,armada-3710-xb-pinctrl.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Marvell Armada 37xx SoC pin and gpio controller
> +
> +maintainers:
> + - Gregory CLEMENT <gregory.clement@bootlin.com>
> + - Marek Behún <kabel@kernel.org>
> + - Miquel Raynal <miquel.raynal@bootlin.com>
> +
> +description: >
> + Each Armada 37xx SoC come with two pin and gpio controller one for the south
> + bridge and the other for the north bridge.
As I think you'll send a v2 because of the robot complaint, maybe you
could rephrase a bit to ease the reading:
"...two pin/gpio controllers, one for..."
> +
> + Inside this set of register the gpio latch allows exposing some configuration
> + of the SoC and especially the clock frequency of the xtal. Hence, this node is
> + a represent as syscon allowing sharing the register between multiple hardware
represented as a?
> + block.
blocks?
The rest looks fine, so:
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
Thanks,
Miquèl
prev parent reply other threads:[~2025-09-29 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 22:35 [PATCH] dt-bindings: pinctrl: Convert marvell,armada-3710-(sb|nb)-pinctrl to DT schema Rob Herring (Arm)
2025-09-25 4:39 ` Rob Herring (Arm)
2025-09-29 15:43 ` Miquel Raynal [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=87ms6di7sn.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=kabel@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=sboyd@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).