From: "Heiko Stübner" <heiko@sntech.de>
To: Val Packett <val@packett.cool>
Cc: Val Packett <val@packett.cool>,
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>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] clk: rockchip: add clock ID for CIF0/1 on RK3066
Date: Thu, 05 Dec 2024 09:48:17 +0100 [thread overview]
Message-ID: <5336726.6fTUFtlzNn@diego> (raw)
In-Reply-To: <20241205055122.11613-1-val@packett.cool>
Hi Val,
Am Donnerstag, 5. Dezember 2024, 06:50:46 CET schrieb Val Packett:
> RK3066 does have two "CIF" video capture interface blocks, add their
> corresponding clock IDs so that they could be used.
>
> Signed-off-by: Val Packett <val@packett.cool>
please split this into two patches
- addition of the clock-ids to the dt-binding header
- setting the clock-ids in the clock driver
Thanks
Heiko
> ---
> drivers/clk/rockchip/clk-rk3188.c | 4 ++--
> include/dt-bindings/clock/rk3188-cru-common.h | 2 ++
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/clk/rockchip/clk-rk3188.c b/drivers/clk/rockchip/clk-rk3188.c
> index 684233e72105..81e94b338d0f 100644
> --- a/drivers/clk/rockchip/clk-rk3188.c
> +++ b/drivers/clk/rockchip/clk-rk3188.c
> @@ -344,7 +344,7 @@ static struct rockchip_clk_branch common_clk_branches[] __initdata = {
>
> GATE(0, "pclkin_cif0", "ext_cif0", 0,
> RK2928_CLKGATE_CON(3), 3, GFLAGS),
> - INVERTER(0, "pclk_cif0", "pclkin_cif0",
> + INVERTER(PCLK_CIF0, "pclk_cif0", "pclkin_cif0",
> RK2928_CLKSEL_CON(30), 8, IFLAGS),
>
> FACTOR(0, "xin12m", "xin24m", 0, 1, 2),
> @@ -602,7 +602,7 @@ static struct rockchip_clk_branch rk3066a_clk_branches[] __initdata = {
>
> GATE(0, "pclkin_cif1", "ext_cif1", 0,
> RK2928_CLKGATE_CON(3), 4, GFLAGS),
> - INVERTER(0, "pclk_cif1", "pclkin_cif1",
> + INVERTER(PCLK_CIF1, "pclk_cif1", "pclkin_cif1",
> RK2928_CLKSEL_CON(30), 12, IFLAGS),
>
> COMPOSITE(0, "aclk_gpu_src", mux_pll_src_cpll_gpll_p, 0,
> diff --git a/include/dt-bindings/clock/rk3188-cru-common.h b/include/dt-bindings/clock/rk3188-cru-common.h
> index 01e14ab252a7..dd988cc9d582 100644
> --- a/include/dt-bindings/clock/rk3188-cru-common.h
> +++ b/include/dt-bindings/clock/rk3188-cru-common.h
> @@ -103,6 +103,8 @@
> #define PCLK_PERI 351
> #define PCLK_DDRUPCTL 352
> #define PCLK_PUBL 353
> +#define PCLK_CIF0 354
> +#define PCLK_CIF1 355
>
> /* hclk gates */
> #define HCLK_SDMMC 448
>
next prev parent reply other threads:[~2024-12-05 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 5:50 [PATCH] clk: rockchip: add clock ID for CIF0/1 on RK3066 Val Packett
2024-12-05 8:48 ` Heiko Stübner [this message]
2024-12-05 10:25 ` Krzysztof Kozlowski
2024-12-05 12:29 ` Heiko Stübner
2024-12-05 13:45 ` Krzysztof Kozlowski
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=5336726.6fTUFtlzNn@diego \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=val@packett.cool \
/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