From: Yixun Lan <dlan@gentoo.org>
To: 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, Yixun Lan <dlan@gentoo.org>
Subject: [PATCH 0/2] pinctrl: spacemit: add clock/reset support
Date: Sat, 12 Apr 2025 14:58:09 +0800 [thread overview]
Message-ID: <20250412-02-k1-pinctrl-clk-v1-0-e39734419a2d@gentoo.org> (raw)
SpacemiT K1 pinctrl requires two clocks in order to be functional,
also one reset line from hardware persepective.
In this series, adding clock property in dt-binding, and activate
them in the driver. But for reset, making it optional for now.
Notice that, devm_clk_get_optional_enabled() API has be choosed,
which will make old dtb blob still functioinal with new kernel.
For DT part patch, I plan to submit after clock driver merged.
This may result dtb warnings in this version due to the mising
clock property in pinctrl dt node.
Signed-off-by: Yixun Lan <dlan@gentoo.org>
---
Yixun Lan (2):
dt-bindings: pinctrl: spacemit: add clock and reset property
pinctrl: spacemit: add clock support for K1 SoC
.../bindings/pinctrl/spacemit,k1-pinctrl.yaml | 18 ++++++++++++++++++
drivers/pinctrl/spacemit/pinctrl-k1.c | 10 ++++++++++
2 files changed, 28 insertions(+)
---
base-commit: 0af2f6be1b4281385b618cb86ad946eded089ac8
change-id: 20250412-02-k1-pinctrl-clk-9649d6ad22c4
Best regards,
--
Yixun Lan
next reply other threads:[~2025-04-12 6:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 6:58 Yixun Lan [this message]
2025-04-12 6:58 ` [PATCH 1/2] dt-bindings: pinctrl: spacemit: add clock and reset property Yixun Lan
2025-04-12 11:31 ` ALOK TIWARI
2025-04-12 13:55 ` Yixun Lan
2025-04-12 6:58 ` [PATCH 2/2] pinctrl: spacemit: add clock support for K1 SoC Yixun Lan
2025-04-12 18:27 ` Rob Herring
2025-04-12 22:34 ` Yixun Lan
2025-04-15 19:38 ` Rob Herring
2025-04-15 23:06 ` Yixun Lan
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=20250412-02-k1-pinctrl-clk-v1-0-e39734419a2d@gentoo.org \
--to=dlan@gentoo.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.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
all inboxes | Powered by JetHome®