linux_dsm_epyc7002/include/linux/mtd
Vignesh Raghavendra dcc7d3446a mtd: Add support for HyperBus memory devices
Cypress' HyperBus is Low Signal Count, High Performance Double Data Rate
Bus interface between a host system master and one or more slave
interfaces. 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 HyperBus
specification[1].

HyperFlash follows CFI AMD/Fujitsu Extended Command Set (0x0002) similar
to that of existing parallel NORs. Since HyperBus is x8 DDR bus,
its equivalent to x16 parallel NOR flash with respect to bits per clock
cycle. But HyperBus operates at >166MHz frequencies.
HyperRAM provides direct random read/write access to flash memory
array.

But, HyperBus memory controllers seem to abstract implementation details
and expose a simple MMIO interface to access connected flash.

Add support for registering HyperFlash devices with MTD framework. MTD
maps framework along with CFI chip support framework are used to support
communicating with flash.

Framework is modelled along the lines of spi-nor framework. HyperBus
memory controller (HBMC) drivers calls hyperbus_register_device() to
register a single HyperFlash device. HyperFlash core parses MMIO access
information from DT, sets up the map_info struct, probes CFI flash and
registers it with MTD framework.

Some HBMC masters need calibration/training sequence[3] to be carried
out, in order for DLL inside the controller to lock, by reading a known
string/pattern. This is done by repeatedly reading CFI Query
Identification String. Calibration needs to be done before trying to detect
flash 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 Sequence

Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
2019-06-27 19:47:58 +02:00
..
bbm.h mtd: nand: Cleanup flags and fields for bad block marker position 2019-04-18 08:54:07 +02:00
blktrans.h
cfi_endian.h
cfi.h mtd: cfi_cmdset_0002: Add support for polling status register 2019-06-27 19:47:45 +02:00
concat.h
doc2000.h
flashchip.h
ftl.h
gen_probe.h
hyperbus.h mtd: Add support for HyperBus memory devices 2019-06-27 19:47:58 +02:00
inftl.h
jedec.h
latch-addr-flash.h
lpc32xx_mlc.h
lpc32xx_slc.h
map.h
mtd.h Char/Misc driver patches for 4.21-rc1 2018-12-28 20:54:57 -08:00
mtdram.h
nand_bch.h mtd: nand: Clarify Kconfig entry for software BCH ECC algorithm 2019-04-18 08:54:00 +02:00
nand_ecc.h
nand-gpio.h
nand.h mtd: nand: Add a helper to retrieve the number of pages per target 2019-04-08 10:21:09 +02:00
ndfc.h
nftl.h
onenand_regs.h
onenand.h mtd: onenand: Store bad block marker position in chip struct 2019-04-18 08:54:07 +02:00
onfi.h
partitions.h
pfow.h
physmap.h
pismo.h
plat-ram.h
platnand.h
qinfo.h
rawnand.h mtd: nand: Make flags for bad block marker position more granular 2019-04-18 08:54:07 +02:00
sh_flctl.h
sharpsl.h
spear_smi.h
spi-nor.h mtd: spi-nor: Fix wrong abbreviation HWCPAS 2019-02-21 08:58:40 +01:00
spinand.h mtd: spinand: Use the spi-mem dirmap API 2019-03-21 16:44:51 +01:00
super.h
ubi.h
xip.h