| Message ID | ebc73cabe3dbfc517883c605cad2178b00d010dc.1654855135.git.geert+renesas@glider.be (mailing list archive) |
|---|---|
| State | Under Review |
| Delegated to: | Geert Uytterhoeven |
| Headers | show |
| Series | [PATCH/RFC] arm64: defconfig: Enable HyperBus support | expand |
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index c8cbb98ea6bc4d21..afda8325ca9b675a 100644 --- a/arch/arm64/configs/defconfig +++ b/arch/arm64/configs/defconfig @@ -270,6 +270,7 @@ CONFIG_MTD_NAND_MARVELL=y CONFIG_MTD_NAND_FSL_IFC=y CONFIG_MTD_NAND_QCOM=y CONFIG_MTD_SPI_NOR=y +CONFIG_MTD_HYPERBUS=m CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_NBD=m CONFIG_VIRTIO_BLK=y
Enable modular support for HyperBus, which is used on R-Car Gen3 and Gen4 platforms. Note that the actual Renesas RPC-IF HyperBus driver (RPCIF_HYPERBUS) is not enabled, as it depends on MTD_CFI_BE_BYTE_SWAP. Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> --- I think we cannot just enable MTD_CFI_BE_BYTE_SWAP in a generic kernel, as that may break other platforms. Is that correct? To be queued in renesas-devel for v5.20, after the above has been resolved. --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+)