devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Li <Frank.Li@nxp.com>
To: frank.li@nxp.com, shawnguo@kernel.org
Cc: clin@suse.com, conor+dt@kernel.org, devicetree@vger.kernel.org,
	eagle.zhou@nxp.com, festevam@gmail.com, imx@lists.linux.dev,
	joy.zou@nxp.com, kernel@pengutronix.de,
	krzysztof.kozlowski+dt@linaro.org, leoyang.li@nxp.com,
	linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com,
	linux-kernel@vger.kernel.org, pierre.gondois@arm.com,
	robh+dt@kernel.org, s.hauer@pengutronix.de, shenwei.wang@nxp.com,
	sherry.sun@nxp.com
Subject: [PATCH v2 1/7] genpd: imx: scu-pd: fixed dma2-ch domain defination
Date: Mon, 25 Sep 2023 16:49:07 -0400	[thread overview]
Message-ID: <20230925204913.3776656-2-Frank.Li@nxp.com> (raw)
In-Reply-To: <20230925204913.3776656-1-Frank.Li@nxp.com>

Split the 'dma2-ch' resource into two parts due to a gap between
IMX_SC_R_DMA_2_CH4(258) and IMX_SC_R_DMA_2_CH5(427).

Fixes: d4ea45e8a603 ("dt-bindings: imx: add scu resource id headfile")
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
 drivers/genpd/imx/scu-pd.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/genpd/imx/scu-pd.c b/drivers/genpd/imx/scu-pd.c
index 2f693b67ddb4..891c1d925a9d 100644
--- a/drivers/genpd/imx/scu-pd.c
+++ b/drivers/genpd/imx/scu-pd.c
@@ -150,7 +150,8 @@ static const struct imx_sc_pd_range imx8qxp_scu_pd_ranges[] = {
 	{ "mclk-out-1", IMX_SC_R_MCLK_OUT_1, 1, false, 0 },
 	{ "dma0-ch", IMX_SC_R_DMA_0_CH0, 32, true, 0 },
 	{ "dma1-ch", IMX_SC_R_DMA_1_CH0, 16, true, 0 },
-	{ "dma2-ch", IMX_SC_R_DMA_2_CH0, 32, true, 0 },
+	{ "dma2-ch-0", IMX_SC_R_DMA_2_CH0, 5, true, 0 },
+	{ "dma2-ch-1", IMX_SC_R_DMA_2_CH5, 27, true, 0 },
 	{ "dma3-ch", IMX_SC_R_DMA_3_CH0, 32, true, 0 },
 	{ "asrc0", IMX_SC_R_ASRC_0, 1, false, 0 },
 	{ "asrc1", IMX_SC_R_ASRC_1, 1, false, 0 },
-- 
2.34.1


  reply	other threads:[~2023-09-25 20:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25 20:49 [PATCH v2 0/7] arm64: dts: imx8qxp add emda support Frank Li
2023-09-25 20:49 ` Frank Li [this message]
2023-09-25 20:49 ` [PATCH v2 2/7] arm64: dts: imx8: add edma[0..3] Frank Li
2023-09-25 20:49 ` [PATCH v2 3/7] arm64: dts: imx8: add edma for uart[0..3] Frank Li
2023-09-25 20:49 ` [PATCH v2 4/7] arm64: dts: imx8qm: Update edma channel " Frank Li
2023-09-25 20:49 ` [PATCH v2 5/7] arm64: dts: imx8: update lpuart[0..3] irq number Frank Li
2023-09-25 20:49 ` [PATCH v2 6/7] arm64: dts: imx8qxp-mek: enable 8qxp lpuart2 and lpuart3 Frank Li
2023-09-25 20:49 ` [PATCH v2 7/7] arm64: dts: imx8qm-mek: enable 8qm " Frank Li
2023-10-09 13:28 ` [PATCH v2 0/7] arm64: dts: imx8qxp add emda support Shawn Guo

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=20230925204913.3776656-2-Frank.Li@nxp.com \
    --to=frank.li@nxp.com \
    --cc=clin@suse.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eagle.zhou@nxp.com \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=joy.zou@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre.gondois@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=shenwei.wang@nxp.com \
    --cc=sherry.sun@nxp.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;
as well as URLs for NNTP newsgroup(s).