From: Andy Yan <andy.yan@rock-chips.com>
To: arnd@arndb.de
Cc: srinivas.kandagatla@linaro.org, treding@nvidia.com,
kuninori.morimoto.gx@renesas.com, alim.akhtar@samsung.com,
linux-kernel@vger.kernel.org, krzk@kernel.org,
will.deacon@arm.com, catalin.marinas@arm.com,
riku.voipio@linaro.org, linux-arm-kernel@lists.infradead.org,
horms+renesas@verge.net.au, shawn.lin@rock-chips.com,
Andy Yan <andy.yan@rock-chips.com>
Subject: [PATCH 1/2] arm64: defconfig: enable I2C and DW MMC controller on rockchip platform
Date: Wed, 7 Sep 2016 19:46:30 +0800 [thread overview]
Message-ID: <1473248790-27101-1-git-send-email-andy.yan@rock-chips.com> (raw)
I2C and MMC are very basic modules for a board to bootup, as I2C always
used to configure PMIC and MMC devices often used to store filesytem.
So enable them here to let the rockchip based arm64 boards can bootup.
Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
---
arch/arm64/configs/defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index eadf485..427b6dc 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -222,6 +222,7 @@ CONFIG_I2C_QUP=y
CONFIG_I2C_TEGRA=y
CONFIG_I2C_UNIPHIER_F=y
CONFIG_I2C_RCAR=y
+CONFIG_I2C_RK3X=y
CONFIG_I2C_CROS_EC_TUNNEL=y
CONFIG_SPI=y
CONFIG_SPI_ORION=y
@@ -323,6 +324,7 @@ CONFIG_MMC_SPI=y
CONFIG_MMC_DW=y
CONFIG_MMC_DW_EXYNOS=y
CONFIG_MMC_DW_K3=y
+CONFIG_MMC_DW_ROCKCHIP=y
CONFIG_MMC_SUNXI=y
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
--
2.7.4
next reply other threads:[~2016-09-07 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 11:46 Andy Yan [this message]
2016-09-07 11:50 ` [PATCH 2/2] arm64: defconfig: enable MFD RK808 and RK808 regulator Andy Yan
2016-11-17 16:03 ` Heiko Stuebner
2016-09-19 10:10 ` [PATCH 1/2] arm64: defconfig: enable I2C and DW MMC controller on rockchip platform Andy Yan
2016-11-03 11:06 ` Andy Yan
2016-11-17 15:55 ` 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=1473248790-27101-1-git-send-email-andy.yan@rock-chips.com \
--to=andy.yan@rock-chips.com \
--cc=alim.akhtar@samsung.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=horms+renesas@verge.net.au \
--cc=krzk@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riku.voipio@linaro.org \
--cc=shawn.lin@rock-chips.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=treding@nvidia.com \
--cc=will.deacon@arm.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).