Skip to contentSkip to conversation

arm64: defconfig: Enable MTD support for Hyperbus

PATCH Applied Vaishnav Achath 3 participants 3 messages Jun 11, 2024 – Jun 13, 2024

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 arm64: defconfig: Enable MTD support for Hyperbus

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.

---

Tested on J721E EVM : https://gist.github.com/vaishnavachath/d8b2c6df43d8c809027d98087cdaa95f

 arch/arm64/configs/defconfig | 2 ++
 1 file changed, 2 insertions(+)
arch/arm64/configs/defconfig +2 -0
index 05abba0a0209..dfe62d645648 100644
@@ -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
Signature · 1 line
2.34.1
#1 lore raw
Quoted 6 lines · Vaishnav Achath

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.

Looks fine to me, I assume the K3 maintainers will apply this to their tree and forward it to [email protected] along with the other 6.11 material.

Arnd

#2 lore raw
In reply to Vaishnav Achath

Hi Vaishnav Achath,

Quoted 6 lines · Vaishnav Achath

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.

I have applied the following to branch ti-k3-config-next on [1]. Thank you!

[1/1] arm64: defconfig: Enable MTD support for Hyperbus

      commit: 74aa5704cf194441001f16dfd4d5d90f4d3bf413

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent up the chain during the next merge window (or sooner if it is a relevant bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh