From: Jonas Karlman <jonas@kwiboo.se>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: heiko@sntech.de, linux-rockchip@lists.infradead.org,
Finley Xiao <finley.xiao@rock-chips.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH v2 3/3] nvmem: rockchip-otp: Add support for rk3562
Date: Sun, 16 Mar 2025 22:25:53 +0100 [thread overview]
Message-ID: <7e5ff689-c013-47c2-982b-e7f4c1d233ca@kwiboo.se> (raw)
In-Reply-To: <20250227110804.2342976-3-kever.yang@rock-chips.com>
Hi Kever,
On 2025-02-27 12:08, Kever Yang wrote:
> From: Finley Xiao <finley.xiao@rock-chips.com>
>
> This adds the necessary data for handling otp on the rk3562.
>
> Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> ---
>
> Changes in v2: None
>
> drivers/nvmem/rockchip-otp.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/nvmem/rockchip-otp.c b/drivers/nvmem/rockchip-otp.c
> index a04bce89ecc8..6f86cf8ec390 100644
> --- a/drivers/nvmem/rockchip-otp.c
> +++ b/drivers/nvmem/rockchip-otp.c
> @@ -341,6 +341,17 @@ static const struct rockchip_data px30_data = {
> .reg_read = px30_otp_read,
> };
>
> +static const char * const rk3562_otp_clocks[] = {
> + "usr", "sbpi", "apb_pclk", "phy",
> +};
These are the same clocks as used for rk3568 below.
> +
> +static const struct rockchip_data rk3562_data = {
> + .size = 0x80,
> + .clks = rk3562_otp_clocks,
> + .num_clks = ARRAY_SIZE(rk3562_otp_clocks),
> + .reg_read = rk3568_otp_read,
> +};
> +
> static const char * const rk3568_otp_clocks[] = {
> "usr", "sbpi", "apb_pclk", "phy",
> };
> @@ -372,6 +383,10 @@ static const struct of_device_id rockchip_otp_match[] = {
> .compatible = "rockchip,rk3308-otp",
> .data = &px30_data,
> },
> + {
> + .compatible = "rockchip,rk3562-otp",
> + .data = &rk3562_data,
Here we can use rk3568_data directly without having to add a new
rk3562_data struct.
Regards,
Jonas
> + },
> {
> .compatible = "rockchip,rk3568-otp",
> .data = &rk3568_data,
next prev parent reply other threads:[~2025-03-16 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 11:08 [PATCH v2 1/3] dt-bindings: nvmem: rockchip,otp: Add support for rk3562 and rk3568 Kever Yang
2025-02-27 11:08 ` [PATCH v2 2/3] nvmem: rockchip-otp: Add support for rk3568-otp Kever Yang
2025-03-16 21:52 ` Jonas Karlman
2025-04-15 9:21 ` Kever Yang
2025-02-27 11:08 ` [PATCH v2 3/3] nvmem: rockchip-otp: Add support for rk3562 Kever Yang
2025-03-16 21:25 ` Jonas Karlman [this message]
2025-02-28 20:09 ` [PATCH v2 1/3] dt-bindings: nvmem: rockchip,otp: Add support for rk3562 and rk3568 Rob Herring (Arm)
2025-03-07 17:22 ` Srinivas Kandagatla
2025-03-17 0:00 ` Jonas Karlman
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=7e5ff689-c013-47c2-982b-e7f4c1d233ca@kwiboo.se \
--to=jonas@kwiboo.se \
--cc=finley.xiao@rock-chips.com \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=srinivas.kandagatla@linaro.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
all inboxes | Powered by JetHome®