From: Sameer Pujar <spujar@nvidia.com>
To: <catalin.marinas@arm.com>, <will.deacon@arm.com>,
<heiko@sntech.de>, <horms+renesas@verge.net.au>,
<andy.gross@linaro.org>, <maxime.ripard@bootlin.com>,
<olof@lixom.net>, <bjorn.andersson@linaro.org>,
<jagan@amarulasolutions.com>, <enric.balletbo@collabora.com>,
<ezequiel@collabora.com>, <stefan.wahren@i2se.com>,
<marc.w.gonzalez@free.fr>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <treding@nvidia.com>,
<jonathanh@nvidia.com>, Sameer Pujar <spujar@nvidia.com>
Subject: [PATCH] arm64: defconfig: build aconnect and adma drivers as modules
Date: Tue, 12 Mar 2019 19:51:34 +0530 [thread overview]
Message-ID: <1552400494-770-1-git-send-email-spujar@nvidia.com> (raw)
Following configs/drivers are enabled as modules,
- TEGRA_ACONNECT (drivers/bus/tegra-aconnect.c)
- TEGRA210_ADMA (drivers/dma/tegra210-adma.c)
Signed-off-by: Sameer Pujar <spujar@nvidia.com>
---
arch/arm64/configs/defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 2d9c390..e9d514c 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -203,6 +203,7 @@ CONFIG_DMA_CMA=y
CONFIG_CMA_SIZE_MBYTES=32
CONFIG_HISILICON_LPC=y
CONFIG_SIMPLE_PM_BUS=y
+CONFIG_TEGRA_ACONNECT=m
CONFIG_MTD=y
CONFIG_MTD_BLOCK=y
CONFIG_MTD_M25P80=y
@@ -622,6 +623,7 @@ CONFIG_K3_DMA=y
CONFIG_MV_XOR_V2=y
CONFIG_PL330_DMA=y
CONFIG_TEGRA20_APB_DMA=y
+CONFIG_TEGRA210_ADMA=m
CONFIG_QCOM_BAM_DMA=y
CONFIG_QCOM_HIDMA_MGMT=y
CONFIG_QCOM_HIDMA=y
--
2.7.4
reply other threads:[~2019-03-12 14:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1552400494-770-1-git-send-email-spujar@nvidia.com \
--to=spujar@nvidia.com \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=enric.balletbo@collabora.com \
--cc=ezequiel@collabora.com \
--cc=heiko@sntech.de \
--cc=horms+renesas@verge.net.au \
--cc=jagan@amarulasolutions.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=maxime.ripard@bootlin.com \
--cc=olof@lixom.net \
--cc=stefan.wahren@i2se.com \
--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).