From: Sameer Pujar <spujar@nvidia.com>
To: <linux@armlinux.org.uk>, <jhogan@kernel.org>
Cc: Sameer Pujar <spujar@nvidia.com>,
linux-kernel@vger.kernel.org, jonathanh@nvidia.com,
thierry.reding@gmail.com, linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: enforce PM requirement
Date: Tue, 5 Feb 2019 16:46:58 +0530 [thread overview]
Message-ID: <1549365418-26283-1-git-send-email-spujar@nvidia.com> (raw)
Drivers need to handle !PM case with work arounds for managing clocks
and power explicitly, which is not really necessary when PM support on
tegra is in good shape. In fact ARM 64-bit tegra platforms enforce PM
support and there is no reason why this cannot be done for 32-bit.
This patch selects PM unconditionally and drivers can rely on runtime
PM framework for clock and power management.
Signed-off-by: Sameer Pujar <spujar@nvidia.com>
Reviewed-by: Thierry Reding <treding@nvidia.com>
Reviewed-by: Jonathan Hunter <jonathanh@nvidia.com>
---
arch/arm/mach-tegra/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-tegra/Kconfig b/arch/arm/mach-tegra/Kconfig
index 7f3b83e..51a8fa3 100644
--- a/arch/arm/mach-tegra/Kconfig
+++ b/arch/arm/mach-tegra/Kconfig
@@ -10,6 +10,7 @@ menuconfig ARCH_TEGRA
select HAVE_ARM_SCU if SMP
select HAVE_ARM_TWD if SMP
select PINCTRL
+ select PM
select PM_OPP
select ARCH_HAS_RESET_CONTROLLER
select RESET_CONTROLLER
--
2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-02-05 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 11:16 Sameer Pujar [this message]
2019-02-11 13:59 ` [PATCH] ARM: tegra: enforce PM requirement Sameer Pujar
2019-02-25 15:13 ` Dmitry Osipenko
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=1549365418-26283-1-git-send-email-spujar@nvidia.com \
--to=spujar@nvidia.com \
--cc=jhogan@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=thierry.reding@gmail.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).