From: peng.fan@nxp.com
To: shawnguo@kernel.org, s.hauer@pengutronix.de
Cc: aisheng.dong@nxp.com, Peng Fan <peng.fan@nxp.com>,
festevam@gmail.com, qiangqing.zhang@nxp.com,
linux@rempel-privat.de, linux-arm-kernel@lists.infradead.org,
kernel@pengutronix.de, leonard.crestez@nxp.com,
daniel.baluta@nxp.com, linux-kernel@vger.kernel.org,
linux-imx@nxp.com
Subject: [PATCH 4/4] firmware: imx: scu-pd: add more cm4 resources
Date: Thu, 23 Apr 2020 14:59:34 +0800 [thread overview]
Message-ID: <1587625174-32668-5-git-send-email-peng.fan@nxp.com> (raw)
In-Reply-To: <1587625174-32668-1-git-send-email-peng.fan@nxp.com>
From: Peng Fan <peng.fan@nxp.com>
Add more cm4 resources, then linux could use cm4's i2c/lpuart and
could kick cm4 core.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
drivers/firmware/imx/scu-pd.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/firmware/imx/scu-pd.c b/drivers/firmware/imx/scu-pd.c
index 7b43bd63cc1e..2fa86be2027a 100644
--- a/drivers/firmware/imx/scu-pd.c
+++ b/drivers/firmware/imx/scu-pd.c
@@ -170,6 +170,16 @@ static const struct imx_sc_pd_range imx8qxp_scu_pd_ranges[] = {
/* CM40 SS */
{ "cm40_i2c", IMX_SC_R_M4_0_I2C, 1, false, 0 },
{ "cm40_intmux", IMX_SC_R_M4_0_INTMUX, 1, false, 0 },
+ { "cm40_pid", IMX_SC_R_M4_0_PID0, 5, true, 0},
+ { "cm40_mu1a", IMX_SC_R_M4_0_MU_1A, 1, false, 0},
+ { "cm40_lpuart", IMX_SC_R_M4_0_UART, 1, false, 0},
+
+ /* CM41 SS */
+ { "cm41_i2c", IMX_SC_R_M4_1_I2C, 1, false, 0 },
+ { "cm41_intmux", IMX_SC_R_M4_1_INTMUX, 1, false, 0 },
+ { "cm41_pid", IMX_SC_R_M4_1_PID0, 5, true, 0},
+ { "cm41_mu1a", IMX_SC_R_M4_1_MU_1A, 1, false, 0},
+ { "cm41_lpuart", IMX_SC_R_M4_1_UART, 1, false, 0},
};
static const struct imx_sc_pd_soc imx8qxp_scu_pd = {
--
2.16.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-23 7:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 6:59 [PATCH 0/4] firmware: imx: fix/update cm4 and add resource check peng.fan
2020-04-23 6:59 ` [PATCH 1/4] firmware: imx: scu-pd: fix cm40 power domain peng.fan
2020-04-23 10:02 ` Aisheng Dong
2020-04-23 6:59 ` [PATCH 2/4] firmware: imx: add resource management api peng.fan
2020-04-23 10:04 ` Aisheng Dong
2020-04-23 10:57 ` Peng Fan
2020-04-23 14:04 ` Aisheng Dong
2020-04-24 1:11 ` Peng Fan
2020-04-24 2:04 ` Aisheng Dong
2020-06-01 12:40 ` Peng Fan
2020-06-02 2:41 ` Aisheng Dong
2020-06-02 4:50 ` Peng Fan
2020-06-02 7:28 ` Aisheng Dong
2020-06-02 7:47 ` Peng Fan
2020-06-02 9:07 ` Aisheng Dong
2020-06-02 3:07 ` Aisheng Dong
2020-06-02 5:23 ` Peng Fan
2020-06-02 7:12 ` Aisheng Dong
2020-04-23 6:59 ` [PATCH 3/4] firmware: imx: scu-pd: ignore power domain not owned peng.fan
2020-04-23 10:06 ` Aisheng Dong
2020-04-23 6:59 ` peng.fan [this message]
2020-04-23 10:33 ` [PATCH 4/4] firmware: imx: scu-pd: add more cm4 resources Aisheng Dong
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=1587625174-32668-5-git-send-email-peng.fan@nxp.com \
--to=peng.fan@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=daniel.baluta@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=qiangqing.zhang@nxp.com \
--cc=s.hauer@pengutronix.de \
--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