All of lore.kernel.org
 help / color / mirror / Atom feed
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 2/2] arm64: imx8mq: select GPCv2 irqchip driver
Date: Tue, 15 Jan 2019 12:04:46 +0100	[thread overview]
Message-ID: <20190115110446.19077-2-l.stach@pengutronix.de> (raw)
In-Reply-To: <20190115110446.19077-1-l.stach@pengutronix.de>

The system is unable to boot without this driver being present,
as most of the peripherals are connected to this IRQ controller.

Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
 arch/arm64/Kconfig.platforms | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
index bb0d78d1ca4d..e9ce095af6c7 100644
--- a/arch/arm64/Kconfig.platforms
+++ b/arch/arm64/Kconfig.platforms
@@ -149,6 +149,7 @@ config ARCH_MXC
 	select CONFIG_PM
 	select PM_GENERIC_DOMAINS
 	select IMX_GPCV2_PM_DOMAINS
+	select IMX_GPCV2
 	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

  reply	other threads:[~2019-01-15 11:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15 11:04 [PATCH 1/2] arm64: dts: imx8mq: properly describe IRQ hierarchy Lucas Stach
2019-01-15 11:04 ` Lucas Stach [this message]
2019-01-21 17:45   ` [PATCH 2/2] arm64: imx8mq: select GPCv2 irqchip driver Fabio Estevam
2019-01-16 10:51 ` [PATCH 1/2] arm64: dts: imx8mq: properly describe IRQ hierarchy Shawn Guo
2019-01-22  6:29   ` Shawn Guo
     [not found] ` <VI1PR0402MB3357FAB48888D99A809F41AEF99F0@VI1PR0402MB3357.eurprd04.prod.outlook.com>
     [not found]   ` <AM6PR04MB51581FBD4D21FEFDCAC2B27FE39F0@AM6PR04MB5158.eurprd04.prod.outlook.com>
     [not found]     ` <7f92c150219832eb9fb54e72021116ad78ae71c3.camel@nxp.com>
2019-01-21 17:30       ` Fabio Estevam
2019-01-21 17:31         ` Lucas Stach
2019-01-21 17:34           ` Fabio Estevam
2019-01-21 17:42             ` Lucas Stach
2019-01-21 17:59           ` Daniel Baluta
2019-01-21 18:03             ` Daniel Baluta
2019-01-22  3:41             ` Manivannan Sadhasivam
2019-01-22  7:22               ` Manivannan Sadhasivam

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=20190115110446.19077-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 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.