From: Alex Elder <elder@riscstar.com>
To: Yixun Lan <dlan@gentoo.org>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: pinctrl: spacemit: add clock and reset property
Date: Mon, 21 Apr 2025 14:11:16 -0500 [thread overview]
Message-ID: <8e7cdada-6623-41ee-8839-b6db1d24050f@riscstar.com> (raw)
In-Reply-To: <20250416-02-k1-pinctrl-clk-v2-1-2b5fcbd4183c@gentoo.org>
On 4/15/25 7:15 PM, Yixun Lan wrote:
> SpacemiT K1 SoC's pinctrl controller requires two clocks in order
> to work properly, also has one reset line from hardware perspective.
You mention the reset line here but that isn't implemented
by this patch (or the next).
I assume the reset series will be merged soon, and if that's
the case, maybe you can add two more patches to incorporate
that in the next version of this series.
Other than the description, this looks good to me. You'll
want one of the DT maintainers to sign off, though.
-Alex
>
> Signed-off-by: Yixun Lan <dlan@gentoo.org>
> ---
> .../bindings/pinctrl/spacemit,k1-pinctrl.yaml | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml
> index b01ecd83b71b5e9f47256adde23bc8b183bef05e..d80e88aa07b45f4a3d90e8217caf93d32655927d 100644
> --- a/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml
> @@ -17,6 +17,19 @@ properties:
> items:
> - description: pinctrl io memory base
>
> + clocks:
> + items:
> + - description: Functional Clock
> + - description: Bus Clock
> +
> + clock-names:
> + items:
> + - const: func
> + - const: bus
> +
> + resets:
> + maxItems: 1
> +
> patternProperties:
> '-cfg$':
> type: object
> @@ -94,6 +107,8 @@ patternProperties:
> required:
> - compatible
> - reg
> + - clocks
> + - clock-names
>
> additionalProperties: false
>
> @@ -108,6 +123,9 @@ examples:
> pinctrl@d401e000 {
> compatible = "spacemit,k1-pinctrl";
> reg = <0x0 0xd401e000 0x0 0x400>;
> + clocks = <&syscon_apbc 42>,
> + <&syscon_apbc 94>;
> + clock-names = "func", "bus";
>
> uart0_2_cfg: uart0-2-cfg {
> uart0-2-pins {
>
next prev parent reply other threads:[~2025-04-21 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 0:15 [PATCH v2 0/2] pinctrl: spacemit: add clock/reset support Yixun Lan
2025-04-16 0:15 ` [PATCH v2 1/2] dt-bindings: pinctrl: spacemit: add clock and reset property Yixun Lan
2025-04-21 19:11 ` Alex Elder [this message]
2025-04-21 19:11 ` Rob Herring (Arm)
2025-04-16 0:15 ` [PATCH v2 2/2] pinctrl: spacemit: add clock support for K1 SoC Yixun Lan
2025-04-21 19:11 ` Alex Elder
2025-04-18 23:59 ` [PATCH v2 0/2] pinctrl: spacemit: add clock/reset support Yixun Lan
2025-04-23 8:39 ` 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=8e7cdada-6623-41ee-8839-b6db1d24050f@riscstar.com \
--to=elder@riscstar.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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).