From: "Rob Herring (Arm)" <robh@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: linux-rockchip@lists.infradead.org,
Sascha Hauer <s.hauer@pengutronix.de>,
Kyungmin Park <kyungmin.park@samsung.com>,
Heiko Stuebner <heiko@sntech.de>,
Chanwoo Choi <cw00.choi@samsung.com>,
Brian Masney <bmasney+clk@redhat.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Jerome Brunet <jbrunet+clk@baylibre.com>,
linux-pm@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>,
kernel@collabora.com, MyungJoo Ham <myungjoo.ham@samsung.com>,
Nicolas Frattaroli <nicolas.frattaroli@collabora.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/7] dt-bindings: devfreq: event: rockchip,dfi: add rk3576
Date: Mon, 5 Oct 2026 12:11:05 -0500 [thread overview]
Message-ID: <179122026463.1037372.13014542138147307791.robh@kernel.org> (raw)
In-Reply-To: <20260921-b4-rockchip-dfi-rk3576-support-v2-3-04f847016321@collabora.com>
On Mon, 21 Sep 2026 23:15:05 +0200, Sebastian Reichel wrote:
> From: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
>
> The RK3576 has DFI hardware for monitoring the DDR's bandwidth much
> like other rockchip SoCs do. Unlike the RK3588 however, it only has two
> memory channels, so only two per-channel pclks for DFI.
>
> Add a compatible for this SoC's variant, and add it to the conditionals
> at the bottom of the bindings file.
>
> Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> ---
> .../bindings/devfreq/event/rockchip,dfi.yaml | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-10-05 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 21:15 [PATCH v2 0/7] PM / devfreq: rockchip-dfi: RK3576 support Sebastian Reichel
2026-09-21 21:15 ` [PATCH v2 1/7] dt-bindings: clock: rk3576: add more DFI clocks Sebastian Reichel
2026-10-05 17:10 ` Rob Herring (Arm)
2026-09-21 21:15 ` [PATCH v2 2/7] clk: rockchip: rk3576: add missing DFI clock branch Sebastian Reichel
2026-09-21 21:15 ` [PATCH v2 3/7] dt-bindings: devfreq: event: rockchip,dfi: add rk3576 Sebastian Reichel
2026-10-05 17:11 ` Rob Herring (Arm) [this message]
2026-09-21 21:15 ` [PATCH v2 4/7] arm64: dts: rockchip: add DFI node to RK3576 Sebastian Reichel
2026-09-21 21:15 ` [PATCH v2 5/7] PM / devfreq: rockchip-dfi: move register offsets to variant struct Sebastian Reichel
2026-09-21 21:15 ` [PATCH v2 6/7] PM / devfreq: rockchip-dfi: prepare support for v4 DDRMON Sebastian Reichel
2026-09-21 21:15 ` [PATCH v2 7/7] PM / devfreq: rockchip-dfi: add RK3576 support Sebastian Reichel
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=179122026463.1037372.13014542138147307791.robh@kernel.org \
--to=robh@kernel.org \
--cc=bmasney+clk@redhat.com \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbrunet+clk@baylibre.com \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=myungjoo.ham@samsung.com \
--cc=nicolas.frattaroli@collabora.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=sebastian.reichel@collabora.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
all inboxes | Powered by JetHome®