From: Anson Huang <Anson.Huang@nxp.com>
To: linux@armlinux.org.uk, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, catalin.marinas@arm.com, will@kernel.org,
linus.walleij@linaro.org, bgolaszewski@baylibre.com,
oleksandr.suvorov@toradex.com, peng.fan@nxp.com,
andreas@kemnade.info, hverkuil-cisco@xs4all.nl, olof@lixom.net,
krzk@kernel.org, geert+renesas@glider.be,
prabhakar.mahadev-lad.rj@bp.renesas.com, aisheng.dong@nxp.com,
lkundrak@v3.sk, joel@jms.id.au, bjorn.andersson@linaro.org,
leoyang.li@nxp.com, vkoul@kernel.org, michael@walle.cc,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Cc: Linux-imx@nxp.com
Subject: [PATCH V3 4/4] ARM: multi_v7_defconfig: Build in CONFIG_GPIO_MXC by default
Date: Thu, 17 Sep 2020 13:33:49 +0800 [thread overview]
Message-ID: <1600320829-1453-4-git-send-email-Anson.Huang@nxp.com> (raw)
In-Reply-To: <1600320829-1453-1-git-send-email-Anson.Huang@nxp.com>
i.MX SoC GPIO driver provides the basic functions of GPIO pin operations
and IRQ operations, it is now changed from "def_bool y" to "tristate", so
it should be explicitly enabled to make sure all consumers work normally.
Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
---
changes since V2:
- improve commit message to explain why CONFIG_GPIO_MXC needs to be enabled.
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
index bfaa38c..d2744ff 100644
--- a/arch/arm/configs/multi_v7_defconfig
+++ b/arch/arm/configs/multi_v7_defconfig
@@ -465,6 +465,7 @@ CONFIG_GPIO_PALMAS=y
CONFIG_GPIO_TPS6586X=y
CONFIG_GPIO_TPS65910=y
CONFIG_GPIO_TWL4030=y
+CONFIG_GPIO_MXC=y
CONFIG_POWER_AVS=y
CONFIG_ROCKCHIP_IODOMAIN=y
CONFIG_POWER_RESET_AS3722=y
--
2.7.4
_______________________________________________
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:[~2020-09-17 5:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 5:33 [PATCH V3 1/4] gpio: mxc: Support module build Anson Huang
2020-09-17 5:33 ` [PATCH V3 2/4] arm64: defconfig: Build in CONFIG_GPIO_MXC by default Anson Huang
2020-10-26 7:50 ` Shawn Guo
2020-09-17 5:33 ` [PATCH V3 3/4] ARM: imx_v6_v7_defconfig: " Anson Huang
2020-09-17 5:33 ` Anson Huang [this message]
2020-09-29 13:05 ` [PATCH V3 1/4] gpio: mxc: Support module build Linus Walleij
2020-10-12 11:35 ` Anson Huang
2020-10-13 13:04 ` Aisheng Dong
2020-10-11 19:03 ` Guenter Roeck
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=1600320829-1453-4-git-send-email-Anson.Huang@nxp.com \
--to=anson.huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=andreas@kemnade.info \
--cc=bgolaszewski@baylibre.com \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=festevam@gmail.com \
--cc=geert+renesas@glider.be \
--cc=hverkuil-cisco@xs4all.nl \
--cc=joel@jms.id.au \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkundrak@v3.sk \
--cc=michael@walle.cc \
--cc=oleksandr.suvorov@toradex.com \
--cc=olof@lixom.net \
--cc=peng.fan@nxp.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=vkoul@kernel.org \
--cc=will@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).