From: Vaishnav Achath <vaishnav.a@ti.com>
To: <will@kernel.org>, <catalin.marinas@arm.com>
Cc: <m.szyprowski@samsung.com>, <arnd@arndb.de>,
<neil.armstrong@linaro.org>, <dmitry.baryshkov@linaro.org>,
<konrad.dybcio@linaro.org>, <krzysztof.kozlowski@linaro.org>,
<geert+renesas@glider.be>, <quic_bjorande@quicinc.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <nfraprado@collabora.com>,
<u-kumar1@ti.com>, <vigneshr@ti.com>, <nm@ti.com>,
<vaishnav.a@ti.com>
Subject: [PATCH] arm64: defconfig: Enable MTD support for Hyperbus
Date: Tue, 11 Jun 2024 17:28:20 +0530 [thread overview]
Message-ID: <20240611115820.1269805-1-vaishnav.a@ti.com> (raw)
TI Jacinto 7 SoCs (J721E, J7200) have Hyperbus controllers present
which can be used to interface with Hyperflash and HyperRAM storage
devices. Enable the necessary configs for Hyperbus support within
the MTD subsystem and the specific Hyperbus controller as module.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
---
Tested on J721E EVM : https://gist.github.com/vaishnavachath/d8b2c6df43d8c809027d98087cdaa95f
arch/arm64/configs/defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 05abba0a0209..dfe62d645648 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -281,6 +281,8 @@ CONFIG_MTD_NAND_FSL_IFC=y
CONFIG_MTD_NAND_QCOM=y
CONFIG_MTD_SPI_NOR=y
CONFIG_MTD_UBI=m
+CONFIG_MTD_HYPERBUS=m
+CONFIG_HBMC_AM654=m
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_NBD=m
CONFIG_VIRTIO_BLK=y
--
2.34.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-06-11 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 11:58 Vaishnav Achath [this message]
2024-06-11 12:16 ` [PATCH] arm64: defconfig: Enable MTD support for Hyperbus Arnd Bergmann
2024-06-13 6:28 ` Vignesh Raghavendra
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=20240611115820.1269805-1-vaishnav.a@ti.com \
--to=vaishnav.a@ti.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=geert+renesas@glider.be \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=neil.armstrong@linaro.org \
--cc=nfraprado@collabora.com \
--cc=nm@ti.com \
--cc=quic_bjorande@quicinc.com \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
--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