From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: <linux-tegra@vger.kernel.org>,
Petlozu Pravareshwar <petlozup@nvidia.com>,
Viswanath L <viswanathl@nvidia.com>, Kartik <kkartik@nvidia.com>,
Jon Hunter <jonathanh@nvidia.com>
Subject: [PATCH 2/3] soc/tegra: pmc: Add AON SW Wake support for Tegra234
Date: Tue, 6 Jun 2023 16:36:07 +0100 [thread overview]
Message-ID: <20230606153608.94289-2-jonathanh@nvidia.com> (raw)
In-Reply-To: <20230606153608.94289-1-jonathanh@nvidia.com>
From: Viswanath L <viswanathl@nvidia.com>
Wake-up signal 83 on Tegra234 is triggered by software writing to
WAKE_AOWAKE_SW_WAKE_TIER0_TRIGGER_0 register. This wake-up is mapped
to CPU interrupt 179 and is used by the Sensor Processing Engine (SPE)
in the Always-on (AON) power domain for waking up the system.
Signed-off-by: Viswanath L <viswanathl@nvidia.com>
Signed-off-by: Kartik <kkartik@nvidia.com>
Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
---
drivers/soc/tegra/pmc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/soc/tegra/pmc.c b/drivers/soc/tegra/pmc.c
index 12e852a8a609..c77ce91a369a 100644
--- a/drivers/soc/tegra/pmc.c
+++ b/drivers/soc/tegra/pmc.c
@@ -4250,6 +4250,7 @@ static const struct tegra_wake_event tegra234_wake_events[] = {
TEGRA_WAKE_GPIO("power", 29, 1, TEGRA234_AON_GPIO(EE, 4)),
TEGRA_WAKE_GPIO("mgbe", 56, 0, TEGRA234_MAIN_GPIO(Y, 3)),
TEGRA_WAKE_IRQ("rtc", 73, 10),
+ TEGRA_WAKE_IRQ("sw-wake", SW_WAKE_ID, 179),
};
static const struct tegra_pmc_soc tegra234_pmc_soc = {
--
2.34.1
next prev parent reply other threads:[~2023-06-06 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 15:36 [PATCH 1/3] soc/tegra: pmc: Use debugfs_initialized() Jon Hunter
2023-06-06 15:36 ` Jon Hunter [this message]
2023-06-06 15:36 ` [PATCH 3/3] soc/tegra: fuse: Fix Tegra234 fuse size Jon Hunter
2023-06-08 16:33 ` [PATCH 1/3] soc/tegra: pmc: Use debugfs_initialized() Thierry Reding
2023-06-08 16:36 ` (subset) " Thierry Reding
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=20230606153608.94289-2-jonathanh@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=kkartik@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=petlozup@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=viswanathl@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.