From: "Rob Herring (Arm)" <robh@kernel.org>
To: Simon Glass <sjg@chromium.org>
Cc: Brian Masney <bmasney@redhat.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-kernel@vger.kernel.org,
Fabio Estevam <festevam@nabladev.com>,
devicetree@vger.kernel.org, huang lin <hl@rock-chips.com>,
Heiko Stuebner <heiko@sntech.de>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Jeffy Chen <jeffy.chen@rock-chips.com>,
Jonas Karlman <jonas@kwiboo.se>,
linux-rockchip@lists.infradead.org,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 1/6] dt-bindings: clock: rockchip: Add RV1106 CRU support
Date: Wed, 22 Jul 2026 12:16:25 -0500 [thread overview]
Message-ID: <178474058544.1144777.17019195106018644429.robh@kernel.org> (raw)
In-Reply-To: <20260714193656.2196447-2-sjg@chromium.org>
On Tue, 14 Jul 2026 13:36:38 -0600, Simon Glass wrote:
> Add the clock binding header and schema for the Rockchip RV1106 clock
> and reset unit. The clock IDs are numbered continuously from 0, in the
> same way as the RV1103B. The header also covers the MMC drive and
> sample phase clocks, which the CRU provides using control registers in
> the GRF region.
>
> The RV1103 is a package variant of the RV1106 and uses the same CRU.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> Changes in v2:
> - Renumber the clock IDs to be continuous, starting from 0
> - Provide the MMC phase clocks from the CRU rather than a grf-cru
> - Mention the MMC phase clocks in the rockchip,grf description
>
> .../bindings/clock/rockchip,rv1106-cru.yaml | 60 ++++
> .../dt-bindings/clock/rockchip,rv1106-cru.h | 300 ++++++++++++++++++
> 2 files changed, 360 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rv1106-cru.yaml
> create mode 100644 include/dt-bindings/clock/rockchip,rv1106-cru.h
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-07-22 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 19:36 [PATCH v2 0/6] Add support for the Rockchip RV1106 and RV1103 Simon Glass
2026-07-14 19:36 ` [PATCH v2 1/6] dt-bindings: clock: rockchip: Add RV1106 CRU support Simon Glass
2026-07-22 17:16 ` Rob Herring (Arm) [this message]
2026-07-14 19:36 ` [PATCH v2 2/6] clk: rockchip: Add clock controller for the RV1106 Simon Glass
2026-07-21 23:20 ` Brian Masney
2026-07-14 19:36 ` [PATCH v2 3/6] dt-bindings: soc: rockchip: grf: Add RV1106 compatibles Simon Glass
2026-07-21 8:16 ` Krzysztof Kozlowski
2026-07-21 12:30 ` Heiko Stübner
2026-07-14 19:36 ` [PATCH v2 4/6] ARM: dts: rockchip: Add support for RV1106 and RV1103 Simon Glass
2026-07-14 19:36 ` [PATCH v2 5/6] dt-bindings: arm: rockchip: Add Luckfox Pico Mini B Simon Glass
2026-07-14 19:36 ` [PATCH v2 6/6] ARM: dts: " Simon Glass
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=178474058544.1144777.17019195106018644429.robh@kernel.org \
--to=robh@kernel.org \
--cc=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@nabladev.com \
--cc=heiko@sntech.de \
--cc=hl@rock-chips.com \
--cc=jeffy.chen@rock-chips.com \
--cc=jonas@kwiboo.se \
--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=sboyd@kernel.org \
--cc=sjg@chromium.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