From: Marc Zyngier <marc.zyngier@arm.com>
To: linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Cc: Joerg Roedel <joro@8bytes.org>, Heiko Stuebner <heiko@sntech.de>,
Jeffy Chen <jeffy.chen@rock-chips.com>,
arm@kernel.org
Subject: [PATCH v2 2/4] arm64: rockchip: Force CONFIG_PM on Rockchip systems
Date: Fri, 24 Aug 2018 16:06:35 +0100 [thread overview]
Message-ID: <20180824150637.15316-3-marc.zyngier@arm.com> (raw)
In-Reply-To: <20180824150637.15316-1-marc.zyngier@arm.com>
A number of the Rockchip-specific drivers (IOMMU, display controllers)
are now assuming that CONFIG_PM is set, and may completely misbehave
if that's not the case.
Since there is hardly any reason for this configuration option not
to be selected anyway, let's require it (in the same way Tegra already
does).
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
---
arch/arm64/Kconfig.platforms | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
index d5aeac351fc3..21a715ad8222 100644
--- a/arch/arm64/Kconfig.platforms
+++ b/arch/arm64/Kconfig.platforms
@@ -151,6 +151,7 @@ config ARCH_ROCKCHIP
select GPIOLIB
select PINCTRL
select PINCTRL_ROCKCHIP
+ select PM
select ROCKCHIP_TIMER
help
This enables support for the ARMv8 based Rockchip chipsets,
--
2.18.0
next prev parent reply other threads:[~2018-08-24 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 15:06 [PATCH v2 0/4] iommu/rockchip: Runtime PM fixes Marc Zyngier
2018-08-24 15:06 ` [PATCH v2 1/4] ARM: rockchip: Force CONFIG_PM on Rockchip systems Marc Zyngier
2018-08-24 15:06 ` Marc Zyngier [this message]
2018-08-24 15:06 ` [PATCH v2 3/4] iommu/rockchip: Handle errors returned from PM framework Marc Zyngier
2018-08-24 15:06 ` [PATCH v2 4/4] iommu/rockchip: Move irq request past pm_runtime_enable Marc Zyngier
2018-08-24 15:50 ` [PATCH v2 0/4] iommu/rockchip: Runtime PM fixes Olof Johansson
2018-08-24 18:08 ` Heiko Stuebner
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=20180824150637.15316-3-marc.zyngier@arm.com \
--to=marc.zyngier@arm.com \
--cc=arm@kernel.org \
--cc=heiko@sntech.de \
--cc=iommu@lists.linux-foundation.org \
--cc=jeffy.chen@rock-chips.com \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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