From: Sandipan Patra <spatra@nvidia.com>
To: <treding@nvidia.com>, <jonathanh@nvidia.com>, <digetx@gmail.com>,
<ulf.hansson@linaro.org>, <andriy.shevchenko@linux.intel.com>,
<cai.huoqing@linux.dev>
Cc: <bbasu@nvidia.com>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Sandipan Patra <spatra@nvidia.com>
Subject: [PATCH] soc/tegra: pmc: update Tegra234 reset sources
Date: Wed, 30 Mar 2022 12:06:35 +0530 [thread overview]
Message-ID: <20220330063635.1689-1-spatra@nvidia.com> (raw)
Reset_sources list is updated to add all reset sources
and removing ones that do not actually exist.
Signed-off-by: Sandipan Patra <spatra@nvidia.com>
---
drivers/soc/tegra/pmc.c | 33 +++++++++++++++++++++++++--------
1 file changed, 25 insertions(+), 8 deletions(-)
diff --git a/drivers/soc/tegra/pmc.c b/drivers/soc/tegra/pmc.c
index fdf508e03400..d9129b940e3b 100644
--- a/drivers/soc/tegra/pmc.c
+++ b/drivers/soc/tegra/pmc.c
@@ -3766,7 +3766,7 @@ static const struct tegra_pmc_regs tegra234_pmc_regs = {
};
static const char * const tegra234_reset_sources[] = {
- "SYS_RESET_N",
+ "SYS_RESET_N", /*0*/
"AOWDT",
"BCCPLEXWDT",
"BPMPWDT",
@@ -3775,18 +3775,35 @@ static const char * const tegra234_reset_sources[] = {
"APEWDT",
"LCCPLEXWDT",
"SENSOR",
- "AOTAG",
- "VFSENSOR",
+ NULL,
+ NULL, /*10*/
"MAINSWRST",
"SC7",
"HSM",
- "CSITE",
+ NULL,
"RCEWDT",
- "PVA0WDT",
- "PVA1WDT",
- "L1A_ASYNC",
+ NULL,
+ NULL,
+ NULL,
"BPMPBOOT",
- "FUSECRC",
+ "FUSECRC", /*20*/
+ "DCEWDT",
+ "PSCWDT",
+ "PSC",
+ "CSITE_SW",
+ "POD",
+ "SCPM",
+ "VREFRO_POWERBAD",
+ "VMON",
+ "FMON",
+ "FSI_R5WDT", /*30*/
+ "FSI_THERM",
+ "FSI_R52C0WDT",
+ "FSI_R52C1WDT",
+ "FSI_R52C2WDT",
+ "FSI_R52C3WDT",
+ "FSI_FMON",
+ "FSI_VMON" /*37*/
};
static const struct tegra_wake_event tegra234_wake_events[] = {
--
2.17.1
next reply other threads:[~2022-03-30 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 6:36 Sandipan Patra [this message]
2022-03-30 9:16 ` [PATCH] soc/tegra: pmc: update Tegra234 reset sources Andy Shevchenko
2022-04-01 10:12 ` Sandipan Patra
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=20220330063635.1689-1-spatra@nvidia.com \
--to=spatra@nvidia.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bbasu@nvidia.com \
--cc=cai.huoqing@linux.dev \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=treding@nvidia.com \
--cc=ulf.hansson@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