public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Xu Yang <xu.yang_2@nxp.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	shawnguo@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com, abelvesa@kernel.org,
	peng.fan@nxp.com, mturquette@baylibre.com, sboyd@kernel.org,
	Frank.Li@nxp.com, hongxing.zhu@nxp.com
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev, jun.li@nxp.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: [PATCH 2/4] clk: imx95-blk-ctl: fix hsio_blk_ctl_clk_dev_data reg offset
Date: Tue, 18 Nov 2025 15:40:53 +0800	[thread overview]
Message-ID: <20251118074055.2523766-2-xu.yang_2@nxp.com> (raw)
In-Reply-To: <20251118074055.2523766-1-xu.yang_2@nxp.com>

The first item of hsio_blk_ctl_clk_dev_data is used to control PCIe
reference clock. The reg offset should be 0xc0 in HSIO block control
register map. Correct it so that other hsio block control items can
be added later. This will also rename the name to "hsio_pcie_clk_gate"
for better distinction.

Fixes: cf295252f0d8 ("clk: imx95-blk-ctl: Add one clock gate for HSIO block")
Cc: stable@vger.kernel.org
Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
---
 drivers/clk/imx/clk-imx95-blk-ctl.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/clk/imx/clk-imx95-blk-ctl.c b/drivers/clk/imx/clk-imx95-blk-ctl.c
index 56bed4471995..3c2019f428c9 100644
--- a/drivers/clk/imx/clk-imx95-blk-ctl.c
+++ b/drivers/clk/imx/clk-imx95-blk-ctl.c
@@ -285,10 +285,10 @@ static const struct imx95_blk_ctl_dev_data netcmix_dev_data = {
 
 static const struct imx95_blk_ctl_clk_dev_data hsio_blk_ctl_clk_dev_data[] = {
 	[0] = {
-		.name = "hsio_blk_ctl_clk",
+		.name = "hsio_pcie_clk_gate",
 		.parent_names = (const char *[]){ "hsio_pll", },
 		.num_parents = 1,
-		.reg = 0,
+		.reg = 0xc0,
 		.bit_idx = 6,
 		.bit_width = 1,
 		.type = CLK_GATE,
-- 
2.34.1



  reply	other threads:[~2025-11-18  7:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18  7:40 [PATCH 1/4] dt-bindings: clock: imx95: add PCIE and USB PHY clk Xu Yang
2025-11-18  7:40 ` Xu Yang [this message]
2025-11-18 15:45   ` [PATCH 2/4] clk: imx95-blk-ctl: fix hsio_blk_ctl_clk_dev_data reg offset Frank Li
2025-11-18  7:40 ` [PATCH 3/4] clk: imx95-blk-ctl: Add one clock mux for HSIO block Xu Yang
2025-11-18  7:40 ` [PATCH 4/4] arm64: dts: imx95: fix hsio_blk_ctl reg map Xu Yang
2025-11-19  7:44   ` Krzysztof Kozlowski
2025-11-25  7:08     ` Xu Yang
2025-11-19  7:44 ` [PATCH 1/4] dt-bindings: clock: imx95: add PCIE and USB PHY clk Krzysztof Kozlowski
2025-11-19 18:11 ` Stephen Boyd
2025-11-25  7:09   ` Xu Yang

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=20251118074055.2523766-2-xu.yang_2@nxp.com \
    --to=xu.yang_2@nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=abelvesa@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=hongxing.zhu@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=jun.li@nxp.com \
    --cc=kernel@pengutronix.de \
    --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=mturquette@baylibre.com \
    --cc=peng.fan@nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@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