Changes in Kconfig

5fc69b6e - mtd: hyperbus: HBMC_AM654 should depend on ARCH_K3

Mon, 07 Mar 2022 12:27:02 +0000

mtd: hyperbus: HBMC_AM654 should depend on ARCH_K3The AM65x HyperBus controller is only present on Texas Instruments AM65xSoCs. Hence add a dependency on ARCH_K3, to prevent asking the userabout this driver when configuring a kernel without support for theTexas Instruments Inc. K3 multicore SoC architecture.Signed-off-by: Geert Uytterhoeven Signed-off-by: Miquel Raynal Link: https://lore.kernel.org/linux-mtd/9fd6b975adba710158f28aa603cf87a6d189a418.1646655894.git.geert+renesas@glider.be List of files: /linux-6.15/drivers/mtd/hyperbus/Kconfig

6402f4ce - mtd: hyperbus: Fix build failure when only RPCIF_HYPERBUS is enabled

Mon, 12 Oct 2020 07:09:58 +0000

mtd: hyperbus: Fix build failure when only RPCIF_HYPERBUS is enabledcommit 5de15b610f78 ("mtd: hyperbus: add Renesas RPC-IF driver") leadsto build failure[1] with COMPILE_TEST and RPCIF_HYPERBUS enabled. Thisis because driver needs functions RENESAS_RPCIF which is only buildablefor CONFIG_ARCH_RENESAS.Fix this by dropping COMPILE_TEST from RPCIF_HYPERBUS Kconfig entry.This ensures driver can be built only when RENESAS_RPCIF is alsoselected.[1]:rpc-if.c:(.text+0x20): undefined reference to `rpcif_disable_rpm' ld:drivers/mtd/hyperbus/rpc-if.o: in function `rpcif_hb_prepare_read':rpc-if.c:(.text+0xd6): undefined reference to `rpcif_prepare' ld:drivers/mtd/hyperbus/rpc-if.o: in function `rpcif_hb_read16':[...]Fixes: 5de15b610f78 ("mtd: hyperbus: add Renesas RPC-IF driver") leadsReported-by: Richard Weinberger Signed-off-by: Vignesh Raghavendra Signed-off-by: Richard Weinberger List of files: /linux-6.15/drivers/mtd/hyperbus/Kconfig

5de15b61 - mtd: hyperbus: add Renesas RPC-IF driver

Sat, 03 Oct 2020 20:23:20 +0000

mtd: hyperbus: add Renesas RPC-IF driverAdd the HyperFLash driver for the Renesas RPC-IF. It's the "front end"driver using the "back end" APIs in the main driver to talk to the realhardware.Signed-off-by: Sergei Shtylyov Signed-off-by: Vignesh Raghavendra Link: https://lore.kernel.org/r/78abb851-2beb-fe7d-87e5-ce58ee877d35@gmail.com List of files: /linux-6.15/drivers/mtd/hyperbus/Kconfig

dc9cfd26 - mtd: hyperbus: fix dependency and build error

Tue, 13 Aug 2019 23:03:13 +0000

mtd: hyperbus: fix dependency and build errorlib/devres.c, which implements devm_ioremap_resource(), is only builtwhen CONFIG_HAS_IOMEM is set/enabled, so MTD_HYPERBUS should dependon HAS_IOMEM. Fixes a build error and a Kconfig warning (as seen onUML builds):WARNING: unmet direct dependencies detected for MTD_COMPLEX_MAPPINGS Depends on [n]: MTD [=m] && HAS_IOMEM [=n] Selected by [m]: - MTD_HYPERBUS [=m] && MTD [=m]ERROR: "devm_ioremap_resource" [drivers/mtd/hyperbus/hyperbus-core.ko] undefined!Fixes: dcc7d3446a0f ("mtd: Add support for HyperBus memory devices")Signed-off-by: Randy Dunlap Cc: Vignesh Raghavendra Cc: Miquel Raynal Cc: Geert Uytterhoeven Cc: linux-mtd@lists.infradead.orgAcked-by: Vignesh Raghavendra Signed-off-by: Miquel Raynal List of files: /linux-6.15/drivers/mtd/hyperbus/Kconfig

2b372a96 - mtd: hyperbus: Add hardware dependency to AM654 driver

Wed, 31 Jul 2019 08:07:06 +0000

mtd: hyperbus: Add hardware dependency to AM654 driverThe hbmc-am654 driver is for the TI AM654, which is an ARM64 SoC, sodon't propose this driver on other architectures unlessbuild-testing.Fixes: b07079f1642c ("mtd: hyperbus: Add driver for TI's HyperBus memory controller")Signed-off-by: Jean Delvare Cc: Vignesh Raghavendra Cc: Miquel Raynal Signed-off-by: Miquel Raynal List of files: /linux-6.15/drivers/mtd/hyperbus/Kconfig

2d75989d - mtd: hyperbus: Kconfig: Fix HBMC_AM654 dependencies

Fri, 19 Jul 2019 08:29:12 +0000

mtd: hyperbus: Kconfig: Fix HBMC_AM654 dependenciesOn x86_64, when CONFIG_OF is not disabled:WARNING: unmet direct dependencies detected for MUX_MMIO Depends on [n]: MULTIPLEXER [=y] && (OF [=n] || COMPILE_TEST [=n]) Selected by [y]: - HBMC_AM654 [=y] && MTD [=y] && MTD_HYPERBUS [=y]due toconfig HBMC_AM654 tristate "HyperBus controller driver for AM65x SoC" select MULTIPLEXER select MUX_MMIOFix this by making HBMC_AM654 imply MUX_MMIO instead of select sothat dependencies are taken care of. MUX_MMIO is optional forfunctioning of driver.Fixes: b07079f1642c ("mtd: hyperbus: Add driver for TI's HyperBus memory controller")Reported-by: Randy Dunlap Signed-off-by: Vignesh Raghavendra Acked-by: Randy Dunlap # build-testedSigned-off-by: Miquel Raynal List of files: /linux-6.15/drivers/mtd/hyperbus/Kconfig

b07079f1 - mtd: hyperbus: Add driver for TI's HyperBus memory controller

Tue, 25 Jun 2019 07:57:46 +0000

mtd: hyperbus: Add driver for TI's HyperBus memory controllerAdd driver for HyperBus memory controller on TI's AM654 SoC. ProgrammingIP is pretty simple and provides direct memory mapped access toconnected Flash devices.Add basic support for the IP without DMA. Second chip-select is notsupported for now.Signed-off-by: Vignesh Raghavendra Signed-off-by: Miquel Raynal List of files: /linux-6.15/drivers/mtd/hyperbus/Kconfig

dcc7d344 - mtd: Add support for HyperBus memory devices

Tue, 25 Jun 2019 07:57:44 +0000

mtd: Add support for HyperBus memory devicesCypress' HyperBus is Low Signal Count, High Performance Double Data RateBus interface between a host system master and one or more slaveinterfaces. HyperBus is used to connect microprocessor, microcontroller,or ASIC devices with random access NOR flash memory (called HyperFlash)or self refresh DRAM (called HyperRAM).Its a 8-bit data bus (DQ[7:0]) with Read-Write Data Strobe (RWDS)signal and either Single-ended clock(3.0V parts) or Differential clock(1.8V parts). It uses ChipSelect lines to select b/w multiple slaves.At bus level, it follows a separate protocol described in HyperBusspecification[1].HyperFlash follows CFI AMD/Fujitsu Extended Command Set (0x0002) similarto that of existing parallel NORs. Since HyperBus is x8 DDR bus,its equivalent to x16 parallel NOR flash with respect to bits per clockcycle. But HyperBus operates at >166MHz frequencies.HyperRAM provides direct random read/write access to flash memoryarray.But, HyperBus memory controllers seem to abstract implementation detailsand expose a simple MMIO interface to access connected flash.Add support for registering HyperFlash devices with MTD framework. MTDmaps framework along with CFI chip support framework are used to supportcommunicating with flash.Framework is modelled along the lines of spi-nor framework. HyperBusmemory controller (HBMC) drivers calls hyperbus_register_device() toregister a single HyperFlash device. HyperFlash core parses MMIO accessinformation from DT, sets up the map_info struct, probes CFI flash andregisters it with MTD framework.Some HBMC masters need calibration/training sequence[3] to be carriedout, in order for DLL inside the controller to lock, by reading a knownstring/pattern. This is done by repeatedly reading CFI QueryIdentification String. Calibration needs to be done before trying to detectflash as part of CFI flash probe.HyperRAM is not supported at the moment.HyperBus specification can be found at[1]HyperFlash datasheet can be found at[2][1] https://www.cypress.com/file/213356/download[2] https://www.cypress.com/file/213346/download[3] http://www.ti.com/lit/ug/spruid7b/spruid7b.pdf Table 12-5741. HyperFlash Access SequenceSigned-off-by: Vignesh Raghavendra Signed-off-by: Miquel Raynal List of files: /linux-6.15/drivers/mtd/hyperbus/Kconfig