From: "Heiko Stübner" <heiko@sntech.de>
To: robh@kernel.org, WeiHao Li <cn.liweihao@gmail.com>
Cc: hjc@rock-chips.com, andy.yan@rock-chips.com, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, WeiHao Li <cn.liweihao@gmail.com>
Subject: Re: [PATCH v2 3/8] dt-bindings: clock: rk3368: Add SCLK_MIPIDSI_24M
Date: Fri, 05 Sep 2025 07:52:47 +0200 [thread overview]
Message-ID: <2267196.NgBsaNRSFp@diego> (raw)
In-Reply-To: <20250905025632.222422-4-cn.liweihao@gmail.com>
Hi,
Am Freitag, 5. September 2025, 04:56:27 Mitteleuropäische Sommerzeit schrieb WeiHao Li:
> Add a clock id for mipi dsi reference clock, mipi dsi node used it.
>
> Signed-off-by: WeiHao Li <cn.liweihao@gmail.com>
another process-related comment :-) .
(1) You already got in v1 the
Acked-by: Rob Herring (Arm) <robh@kernel.org>
So when sending a v2, please include such received tags
(if there are no major changes to the relevant code)
This prevents people from reviewing things needlessly multiple times.
So patch 3 would look something like:
------------
Add a clock id for mipi dsi reference clock, mipi dsi node used it.
Acked-by: Rob Herring (Arm) <robh@kernel.org>
Signed-off-by: WeiHao Li <cn.liweihao@gmail.com>
------------
(2) As can be seen in
https://lore.kernel.org/linux-rockchip/175690195013.3771488.435870786224873257.b4-ty@sntech.de/
I already applied the two clock patches, so in newer versions don't
send them anymore.
Just to keep in mind for next time.
Heiko
> ---
> include/dt-bindings/clock/rk3368-cru.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/dt-bindings/clock/rk3368-cru.h b/include/dt-bindings/clock/rk3368-cru.h
> index ebae3cbf8..b951e2906 100644
> --- a/include/dt-bindings/clock/rk3368-cru.h
> +++ b/include/dt-bindings/clock/rk3368-cru.h
> @@ -72,6 +72,7 @@
> #define SCLK_SFC 126
> #define SCLK_MAC 127
> #define SCLK_MACREF_OUT 128
> +#define SCLK_MIPIDSI_24M 129
> #define SCLK_TIMER10 133
> #define SCLK_TIMER11 134
> #define SCLK_TIMER12 135
>
next prev parent reply other threads:[~2025-09-05 7:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 2:56 [PATCH v2 0/8] drm/rockchip: Add MIPI DSI support for RK3368 WeiHao Li
2025-09-05 2:56 ` [PATCH v2 1/8] drm/rockchip: dsi: Add " WeiHao Li
2025-09-05 2:56 ` [PATCH v2 2/8] drm/rockchip: vop: add lut_size for RK3368 vop_data WeiHao Li
2025-09-05 2:56 ` [PATCH v2 3/8] dt-bindings: clock: rk3368: Add SCLK_MIPIDSI_24M WeiHao Li
2025-09-05 5:52 ` Heiko Stübner [this message]
2025-09-05 12:26 ` 李维豪
2025-09-05 2:56 ` [PATCH v2 4/8] clk: rockchip: use clock ids for SCLK_MIPIDSI_24M on rk3368 WeiHao Li
2025-09-05 2:56 ` [PATCH v2 5/8] arm64: dts: rockchip: Add display subsystem for RK3368 WeiHao Li
2025-09-05 2:56 ` [PATCH v2 6/8] arm64: dts: rockchip: Add D-PHY " WeiHao Li
2025-09-05 2:56 ` [PATCH v2 7/8] arm64: dts: rockchip: Add DSI " WeiHao Li
2025-09-05 2:56 ` [PATCH v2 8/8] dt-bindings: display: rockchip,dw-mipi-dsi: Document RK3368 DSI WeiHao Li
2025-09-05 20:45 ` Rob Herring (Arm)
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=2267196.NgBsaNRSFp@diego \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=cn.liweihao@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hjc@rock-chips.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=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).