From: Lucas Stach <l.stach@pengutronix.de>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
patchwork-lst@pengutronix.de, NXP Linux Team <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de
Subject: [PATCH v2 2/2] arm64: imx8mq: select PM support
Date: Tue, 15 Jan 2019 12:01:45 +0100 [thread overview]
Message-ID: <20190115110145.11017-2-l.stach@pengutronix.de> (raw)
In-Reply-To: <20190115110145.11017-1-l.stach@pengutronix.de>
The ATF on the i.MX8MQ device disables all non-essential power
domains. For correct on-SoC peripheral operation we need both
the power domain driver and generic domains, so device driver
probe gets ordered behind the power domain controller driver.
Select those options, as those being absent can lead to very
hard to debug failures.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
arch/arm64/Kconfig.platforms | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
index 251ecf34cb02..bb0d78d1ca4d 100644
--- a/arch/arm64/Kconfig.platforms
+++ b/arch/arm64/Kconfig.platforms
@@ -146,6 +146,9 @@ config ARCH_MXC
bool "ARMv8 based NXP i.MX SoC family"
select ARM64_ERRATUM_843419
select ARM64_ERRATUM_845719
+ select CONFIG_PM
+ select PM_GENERIC_DOMAINS
+ select IMX_GPCV2_PM_DOMAINS
help
This enables support for the ARMv8 based SoCs in the
NXP i.MX family.
--
2.20.1
_______________________________________________
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:[~2019-01-15 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 11:01 [PATCH v2 1/2] arm64: dts: imx8mq: add GPC power domains Lucas Stach
2019-01-15 11:01 ` Lucas Stach [this message]
2019-01-16 3:17 ` [PATCH v2 2/2] arm64: imx8mq: select PM support Shawn Guo
2019-01-16 7:00 ` Aisheng Dong
2019-01-16 3:16 ` [PATCH v2 1/2] arm64: dts: imx8mq: add GPC power domains Shawn Guo
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=20190115110145.11017-2-l.stach@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=patchwork-lst@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;
as well as URLs for NNTP newsgroup(s).