Home
last modified time | relevance | path

Searched full:mtd (Results 1 – 25 of 97) sorted by relevance

1234

/Documentation/ABI/testing/
Dsysfs-class-mtd1 What: /sys/class/mtd/
4 Contact: linux-mtd@lists.infradead.org
6 The mtd/ class subdirectory belongs to the MTD subsystem
7 (MTD core).
9 What: /sys/class/mtd/mtdX/
12 Contact: linux-mtd@lists.infradead.org
14 The /sys/class/mtd/mtd{0,1,2,3,...} directories correspond
19 What: /sys/class/mtd/mtdXro/
22 Contact: linux-mtd@lists.infradead.org
25 nodes for /sys/class/mtd/mtdX/ .
[all …]
Dsysfs-bus-spi-devices-spi-nor4 Contact: linux-mtd@lists.infradead.org
15 Contact: linux-mtd@lists.infradead.org
25 Contact: linux-mtd@lists.infradead.org
35 Contact: linux-mtd@lists.infradead.org
Dsysfs-fs-ubifs4 Contact: linux-mtd@lists.infradead.org
16 Contact: linux-mtd@lists.infradead.org
28 Contact: linux-mtd@lists.infradead.org
/Documentation/devicetree/bindings/reserved-memory/
Dphram.yaml7 title: MTD/block device in RAM
10 Specifies that the reserved memory region can be used as an MTD or block
13 The "phram" node is named after the "MTD in PHysical RAM" driver which
21 - $ref: /schemas/mtd/mtd.yaml
28 description: region of memory that can be used as an MTD/block device
/Documentation/devicetree/bindings/mtd/
Dmtd-physmap.yaml4 $id: http://devicetree.org/schemas/mtd/mtd-physmap.yaml#
7 title: CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
17 - $ref: mtd.yaml#
58 - const: mtd-ram
62 - mtd-ram
63 - mtd-rom
80 Width of a single mtd chip. If omitted, assumed to be equal to 'bank-width'.
93 the MTD users (e.g. JFFS2) any more.
95 linux,mtd-name:
97 Allows specifying the mtd name for retro capability with physmap-flash
[all …]
Dmtd.yaml4 $id: http://devicetree.org/schemas/mtd/mtd.yaml#
7 title: MTD (Memory Technology Device)
21 User-defined MTD device name. Can be used to assign user friendly
22 names to MTD devices (instead of the flash model or flash controller
33 $ref: /schemas/mtd/partitions/partitions.yaml
Dlpc32xx-mlc.txt22 - Partitions, see Documentation/devicetree/bindings/mtd/mtd.yaml
Dlpc32xx-slc.txt23 - Partitions, see Documentation/devicetree/bindings/mtd/mtd.yaml
Dti,am654-hbmc.yaml4 $id: http://devicetree.org/schemas/mtd/ti,am654-hbmc.yaml#
33 $ref: mtd-physmap.yaml
Dnand-chip.yaml4 $id: http://devicetree.org/schemas/mtd/nand-chip.yaml#
13 - $ref: mtd.yaml#
Dti,gpmc-onenand.yaml4 $id: http://devicetree.org/schemas/mtd/ti,gpmc-onenand.yaml#
39 $ref: /schemas/mtd/partitions/partition.yaml
Dmicrochip,mchp23k256.txt1 * MTD SPI driver for Microchip 23K256 (and similar) serial SRAM
Dspi-nand.yaml4 $id: http://devicetree.org/schemas/mtd/spi-nand.yaml#
/Documentation/filesystems/
Dubifs.rst15 which work with MTD devices, not block devices. The other Linux
18 To make it more clear, here is a small comparison of MTD devices and
21 1 MTD devices represent flash devices and they consist of eraseblocks of
24 2 MTD devices support 3 main operations - read from some offset within an
42 found in drivers/mtd/ubi. UBI is basically a volume management and
44 level abstraction than a MTD device. The programming model of UBI devices
45 is very similar to MTD devices - they still consist of large eraseblocks,
53 * JFFS2 works on top of MTD devices, UBIFS depends on UBI and works on
129 ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs
134 UBIFS documentation and FAQ/HOWTO at the MTD web site:
[all …]
Dcramfs.rst70 configure an MTD device for it. Also, that MTD device must be supported
72 MTD drivers are cfi_cmdset_0001 (Intel/Sharp CFI flash) or physmap
73 (Flash device in physical memory map). MTD partitions based on such devices
74 are fine too. Then that device should be specified with the "mtd:" prefix
75 as the mount device argument. For example, to mount the MTD device named
78 $ mount -t cramfs mtd:fs_partition /mnt
81 something like "root=mtd:fs_partition" on the kernel command line.
/Documentation/driver-api/mtd/
Dspi-intel.rst16 any of them set, the whole MTD device is made read-only to prevent
31 2) Install mtd-utils package [2]. We need this in order to erase the SPI
33 name "mtd-utils".
39 4) Once the board is up and running again, find the right MTD partition
42 # cat /proc/mtd
90 [2] http://www.linux-mtd.infradead.org/
Dspi-nor.rst151 4) Use `mtd-utils <https://git.infradead.org/mtd-utils.git>`__
199 mtd.type = MTD_NORFLASH
200 mtd.flags = MTD_CAP_NORFLASH
201 mtd.size = 8388608 (8M)
202 mtd.erasesize = 4096 (4K)
203 mtd.writesize = 1
204 mtd.oobsize = 0
Dindex.rst4 Memory Technology Device (MTD)
/Documentation/driver-api/
Dmtdnand.rst2 MTD NAND Driver Programming Interface
11 and connects them to the Memory Technology Devices (MTD) subsystem of
37 - [MTD Interface]
39 These functions provide the interface to the MTD kernel API. They are
110 embeds an mtd structure which will be registered to the MTD subsystem.
111 You can extract a pointer to the mtd structure from a nand_chip pointer
161 static void board_hwcontrol(struct mtd_info *mtd, int cmd)
179 static void board_hwcontrol(struct mtd_info *mtd, int cmd)
181 struct nand_chip *this = mtd_to_nand(mtd);
219 /* Allocate memory for MTD device structure and private data */
[all …]
/Documentation/devicetree/bindings/mtd/partitions/
Dbinman.yaml4 $id: http://devicetree.org/schemas/mtd/partitions/binman.yaml#
21 - $ref: /schemas/mtd/partitions/partition.yaml#
Dlinux,ubi.yaml4 $id: http://devicetree.org/schemas/mtd/partitions/linux,ubi.yaml#
31 $ref: /schemas/mtd/partitions/ubi-volume.yaml#
Dnvmem-cells.yaml4 $id: http://devicetree.org/schemas/mtd/partitions/nvmem-cells.yaml#
20 - $ref: /schemas/mtd/partitions/partition.yaml#
/Documentation/arch/arm/sa1100/
Dassabet.rst130 conjunction with the MTD layer which is responsible for low-level flash
131 management. More information on the Linux MTD can be found on-line at:
132 http://www.linux-mtd.infradead.org/. A JFFS howto with some infos about
173 Now the filesystem is associated to a MTD "partition" once Linux has discovered
190 Creating 5 MTD partitions on "SA1100 flash":
208 within Linux while booted from a ramdisk or NFS. The Linux MTD repository has
/Documentation/ABI/stable/
Dsysfs-class-ubi47 Count of bad physical eraseblocks on the underlying MTD device.
101 Number of the underlying MTD device.
113 Contact: linux-mtd@lists.infradead.org
125 the underlying MTD device.
/Documentation/devicetree/bindings/net/wireless/
Dmediatek,mt76.yaml90 mediatek,mtd-eeprom:
94 - description: phandle to MTD partition
97 Phandle to a MTD partition + offset containing EEPROM data
251 mediatek,mtd-eeprom = <&factory 0x8000>;

1234