From: Detlev Casanova <detlev.casanova@collabora.com>
To: linux-kernel@vger.kernel.org
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Philipp Zabel <p.zabel@pengutronix.de>,
Elaine Zhang <zhangqing@rock-chips.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, kernel@collabora.com,
Detlev Casanova <detlev.casanova@collabora.com>
Subject: [PATCH v2 0/3] Add CRU support for rk3576 SoC
Date: Fri, 2 Aug 2024 17:35:38 -0400 [thread overview]
Message-ID: <20240802214053.433493-1-detlev.casanova@collabora.com> (raw)
Add support for clocks and resets on the rk3576.
Patches from downstream have been squashed and rebased.
The resets have been renumbered without gaps and their actual register/bit
information is set in rst-rk3576.c as it has been done for rk3588.
Changes since v1:
- Remove reset defines that are probably out of the main core
- Separate resets and clocks bindings
- Renumber the resets without gaps
Detlev.
Detlev Casanova (1):
dt-bindings: clock: add rk3576 cru bindings
Elaine Zhang (2):
clk: rockchip: Add dt-binding header for rk3576
clk: rockchip: Add clock controller for the RK3576
.../bindings/clock/rockchip,rk3576-cru.yaml | 73 +
drivers/clk/rockchip/Kconfig | 7 +
drivers/clk/rockchip/Makefile | 1 +
drivers/clk/rockchip/clk-rk3576.c | 1819 +++++++++++++++++
drivers/clk/rockchip/clk.h | 53 +
drivers/clk/rockchip/rst-rk3576.c | 555 +++++
.../dt-bindings/clock/rockchip,rk3576-cru.h | 589 ++++++
.../dt-bindings/reset/rockchip,rk3576-cru.h | 484 +++++
8 files changed, 3581 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3576-cru.yaml
create mode 100644 drivers/clk/rockchip/clk-rk3576.c
create mode 100644 drivers/clk/rockchip/rst-rk3576.c
create mode 100644 include/dt-bindings/clock/rockchip,rk3576-cru.h
create mode 100644 include/dt-bindings/reset/rockchip,rk3576-cru.h
--
2.46.0
next reply other threads:[~2024-08-02 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 21:35 Detlev Casanova [this message]
2024-08-02 21:35 ` [PATCH v2 1/3] dt-bindings: clock: add rk3576 cru bindings Detlev Casanova
2024-08-04 9:52 ` Krzysztof Kozlowski
2024-08-06 21:22 ` Detlev Casanova
2024-08-07 5:50 ` Krzysztof Kozlowski
2024-08-02 21:35 ` [PATCH v2 2/3] clk: rockchip: Add dt-binding header for rk3576 Detlev Casanova
2024-08-04 9:53 ` Krzysztof Kozlowski
2024-08-06 15:23 ` Detlev Casanova
2024-08-07 5:49 ` Krzysztof Kozlowski
2024-08-02 21:35 ` [PATCH v2 3/3] clk: rockchip: Add clock controller for the RK3576 Detlev Casanova
2024-08-03 6:53 ` zhangqing
[not found] ` <a9a9219d-325c-4afa-b40c-b261ff95263c@rock-chips.com>
2024-08-06 14:15 ` Detlev Casanova
2024-08-06 15:13 ` Heiko Stübner
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=20240802214053.433493-1-detlev.casanova@collabora.com \
--to=detlev.casanova@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=zhangqing@rock-chips.com \
/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