| /kernel/linux/linux-5.10/drivers/mtd/maps/ |
| D | plat-ram.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
2 /* drivers/mtd/maps/plat-ram.c
4 * (c) 2004-2005 Simtec Electronics
8 * Generic platform device based RAM map
20 #include <linux/mtd/mtd.h>
21 #include <linux/mtd/map.h>
22 #include <linux/mtd/partitions.h>
23 #include <linux/mtd/plat-ram.h>
27 /* private structure for each mtd platform ram device created */
31 struct mtd_info *mtd; member
[all …]
|
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 depends on MTD!=n
7 bool "Support non-linear mappings of flash chips"
21 with config options or at run-time.
74 and RAM driver code to communicate with chips which are mapped
79 bool "Baikal-T1 Boot ROMs OF-based physical memory map handling"
86 This provides some extra DT physmap parsing for the Baikal-T1
87 platforms, some detection and setting up ROMs-specific accessors.
90 bool "ARM Versatile OF-based physical memory map handling"
100 bool "Cortina Gemini OF-based physical memory map handling"
[all …]
|
| /kernel/linux/linux-4.19/drivers/mtd/maps/ |
| D | plat-ram.c | 1 /* drivers/mtd/maps/plat-ram.c
3 * (c) 2004-2005 Simtec Electronics
7 * Generic platform device based RAM map
21 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
33 #include <linux/mtd/mtd.h>
34 #include <linux/mtd/map.h>
35 #include <linux/mtd/partitions.h>
36 #include <linux/mtd/plat-ram.h>
40 /* private structure for each mtd platform ram device created */
44 struct mtd_info *mtd; member
[all …]
|
| D | Kconfig | 2 depends on MTD!=n
6 bool "Support non-linear mappings of flash chips"
20 with config options or at run-time.
73 and RAM driver code to communicate with chips which are mapped
78 bool "ARM Versatile OF-based physical memory map handling"
88 bool "Cortina Gemini OF-based physical memory map handling"
98 tristate "CFI Flash device mapped on PMC-Sierra MSP"
102 in which user-programmable flash chips are connected on the
103 PMC-Sierra MSP eval/demo boards.
125 which user-programmable flash chips are connected on various
[all …]
|
| /kernel/linux/linux-5.10/drivers/mtd/chips/ |
| D | map_ram.c | 2 * Common code to handle map devices which are simple RAM
14 #include <linux/mtd/mtd.h>
15 #include <linux/mtd/map.h>
23 static int mapram_point (struct mtd_info *mtd, loff_t from, size_t len,
25 static int mapram_unpoint(struct mtd_info *mtd, loff_t from, size_t len);
36 struct mtd_info *mtd; in map_ram_probe() local
38 /* Check the first byte is RAM */ in map_ram_probe()
48 /* Check the last byte is RAM */ in map_ram_probe()
49 map_write8(map, 0x55, map->size-1); in map_ram_probe()
50 if (map_read8(map, map->size-1) != 0x55) in map_ram_probe()
[all …]
|
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "RAM/ROM/Flash chip drivers"
3 depends on MTD!=n
13 support any device that is CFI-compliant, you need to enable this
18 tristate "Detect non-CFI AMD/JEDEC-compatible flash chips"
22 This option enables JEDEC-style probing of flash chips which are not
24 CFI-targeted flash drivers for any chips which are identified which
26 covers most AMD/Fujitsu-compatible chips and also non-CFI
53 are expected to be wired to the CPU in 'host-endian' form.
83 bool "Support 8-bit buswidth" if MTD_CFI_GEOMETRY
[all …]
|
| /kernel/linux/linux-4.19/drivers/mtd/chips/ |
| D | map_ram.c | 2 * Common code to handle map devices which are simple RAM
14 #include <linux/mtd/mtd.h>
15 #include <linux/mtd/map.h>
23 static int mapram_point (struct mtd_info *mtd, loff_t from, size_t len,
25 static int mapram_unpoint(struct mtd_info *mtd, loff_t from, size_t len);
36 struct mtd_info *mtd; in map_ram_probe() local
38 /* Check the first byte is RAM */ in map_ram_probe()
48 /* Check the last byte is RAM */ in map_ram_probe()
49 map_write8(map, 0x55, map->size-1); in map_ram_probe()
50 if (map_read8(map, map->size-1) != 0x55) in map_ram_probe()
[all …]
|
| D | Kconfig | 1 menu "RAM/ROM/Flash chip drivers"
2 depends on MTD!=n
12 support any device that is CFI-compliant, you need to enable this
17 tristate "Detect non-CFI AMD/JEDEC-compatible flash chips"
21 This option enables JEDEC-style probing of flash chips which are not
23 CFI-targeted flash drivers for any chips which are identified which
25 covers most AMD/Fujitsu-compatible chips and also non-CFI
52 are expected to be wired to the CPU in 'host-endian' form.
82 bool "Support 8-bit buswidth" if MTD_CFI_GEOMETRY
89 bool "Support 16-bit buswidth" if MTD_CFI_GEOMETRY
[all …]
|
| /kernel/linux/linux-5.10/drivers/mtd/devices/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "Self-contained MTD device drivers"
3 depends on MTD!=n
7 tristate "Ramix PMC551 PCI Mezzanine RAM card support"
10 This provides a MTD device driver for the Ramix PMC551 RAM PCI card
12 These devices come in memory configurations from 32M - 1G. If you
41 tristate "DEC MS02-NV NVRAM module support"
44 This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
45 backed-up NVRAM module. The module was originally meant as an NFS
52 The module will be called ms02-nv.
[all …]
|
| D | pmc551.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * PMC551 PCI Mezzanine Ram Device
10 * This driver is intended to support the PMC551 PCI Ram device
15 * implements this PCI Ram device as an MTD (Memory Technology
28 * of ram configured (making a grand total of 256MiB onboard).
34 * the ram will cause the driver to detect the onboard memory
49 * Most of the MTD code for this driver was originally written
50 * for the slram.o module in the MTD drivers package which
51 * allows the mapping of system memory into an MTD device.
93 #include <linux/mtd/mtd.h>
[all …]
|
| D | mchp23k256.c | 1 // SPDX-License-Identifier: GPL-2.0-only
5 * Driver for Microchip 23k256 SPI RAM chips
11 #include <linux/mtd/mtd.h>
12 #include <linux/mtd/partitions.h>
30 struct mtd_info mtd; member
39 #define to_mchp23k256_flash(x) container_of(x, struct mchp23k256_flash, mtd)
51 for (i = flash->caps->addr_width; i > 0; i--, addr >>= 8) in mchp23k256_addr2cmd()
57 return 1 + flash->caps->addr_width; in mchp23k256_cmdsz()
60 static int mchp23k256_write(struct mtd_info *mtd, loff_t to, size_t len, in mchp23k256_write() argument
63 struct mchp23k256_flash *flash = to_mchp23k256_flash(mtd); in mchp23k256_write()
[all …]
|
| D | ms02-nv.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
10 #include <linux/mtd/mtd.h>
22 #include "ms02-nv.h"
26 "ms02-nv.c: v.1.0.0 13 Aug 2001 Maciej W. Rozycki.\n";
28 MODULE_AUTHOR("Maciej W. Rozycki <macro@linux-mips.org>");
29 MODULE_DESCRIPTION("DEC MS02-NV NVRAM module driver");
34 * Addresses we probe for an MS02-NV at. Modules may be located
45 static const char ms02nv_name[] = "DEC MS02-NV NVRAM";
46 static const char ms02nv_res_diag_ram[] = "Diagnostic RAM";
47 static const char ms02nv_res_user_ram[] = "General-purpose RAM";
[all …]
|
| /kernel/linux/linux-4.19/drivers/mtd/devices/ |
| D | Kconfig | 1 menu "Self-contained MTD device drivers"
2 depends on MTD!=n
6 tristate "Ramix PMC551 PCI Mezzanine RAM card support"
9 This provides a MTD device driver for the Ramix PMC551 RAM PCI card
11 These devices come in memory configurations from 32M - 1G. If you
40 tristate "DEC MS02-NV NVRAM module support"
43 This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
44 backed-up NVRAM module. The module was originally meant as an NFS
51 The module will be called ms02-nv.
58 Sometimes DataFlash chips are packaged inside MMC-format
[all …]
|
| D | pmc551.c | 2 * PMC551 PCI Mezzanine Ram Device
14 * This driver is intended to support the PMC551 PCI Ram device
19 * implements this PCI Ram device as an MTD (Memory Technology
32 * of ram configured (making a grand total of 256MiB onboard).
38 * the ram will cause the driver to detect the onboard memory
53 * Most of the MTD code for this driver was originally written
54 * for the slram.o module in the MTD drivers package which
55 * allows the mapping of system memory into an MTD device.
97 #include <linux/mtd/mtd.h>
100 "Ramix PMC551 PCI Mezzanine Ram Driver. (C) 1999,2000 Nortel Networks.\n"
[all …]
|
| D | mchp23k256.c | 4 * Driver for Microchip 23k256 SPI RAM chips
15 #include <linux/mtd/mtd.h>
16 #include <linux/mtd/partitions.h>
34 struct mtd_info mtd; member
43 #define to_mchp23k256_flash(x) container_of(x, struct mchp23k256_flash, mtd)
55 for (i = flash->caps->addr_width; i > 0; i--, addr >>= 8) in mchp23k256_addr2cmd()
61 return 1 + flash->caps->addr_width; in mchp23k256_cmdsz()
64 static int mchp23k256_write(struct mtd_info *mtd, loff_t to, size_t len, in mchp23k256_write() argument
67 struct mchp23k256_flash *flash = to_mchp23k256_flash(mtd); in mchp23k256_write()
88 mutex_lock(&flash->lock); in mchp23k256_write()
[all …]
|
| D | ms02-nv.c | 14 #include <linux/mtd/mtd.h>
26 #include "ms02-nv.h"
30 "ms02-nv.c: v.1.0.0 13 Aug 2001 Maciej W. Rozycki.\n";
32 MODULE_AUTHOR("Maciej W. Rozycki <macro@linux-mips.org>");
33 MODULE_DESCRIPTION("DEC MS02-NV NVRAM module driver");
38 * Addresses we probe for an MS02-NV at. Modules may be located
49 static const char ms02nv_name[] = "DEC MS02-NV NVRAM";
50 static const char ms02nv_res_diag_ram[] = "Diagnostic RAM";
51 static const char ms02nv_res_user_ram[] = "General-purpose RAM";
57 static int ms02nv_read(struct mtd_info *mtd, loff_t from, in ms02nv_read() argument
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/mtd/ |
| D | mtd-physmap.txt | 1 CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
6 - compatible : should contain the specific model of mtd chip(s)
7 used, if known, followed by either "cfi-flash", "jedec-flash",
8 "mtd-ram" or "mtd-rom".
9 - reg : Address range(s) of the mtd chip(s)
11 non-identical chips can be described in one node.
12 - bank-width : Width (in bytes) of the bank. Equal to the
14 - device-width : (optional) Width of a single mtd chip. If
15 omitted, assumed to be equal to 'bank-width'.
16 - #address-cells, #size-cells : Must be present if the device has
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/ |
| D | mtd-physmap.txt | 1 CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
6 - compatible : should contain the specific model of mtd chip(s)
7 used, if known, followed by either "cfi-flash", "jedec-flash",
8 "mtd-ram" or "mtd-rom".
9 - reg : Address range(s) of the mtd chip(s)
11 non-identical chips can be described in one node.
12 - bank-width : Width (in bytes) of the bank. Equal to the
14 - device-width : (optional) Width of a single mtd chip. If
15 omitted, assumed to be equal to 'bank-width'.
16 - #address-cells, #size-cells : Must be present if the device has
[all …]
|
| /kernel/linux/linux-4.19/fs/cramfs/ |
| D | Kconfig | 7 file system for ROM based embedded systems. CramFs is read-only,
19 purpose to remain small and low on RAM usage. It is most suitable
20 for small embedded systems. If you have ample RAM to spare, you may
36 depends on CRAMFS && CRAMFS <= MTD
46 MTD device capable of direct memory mapping e.g. from
47 the 'physmap' map driver or a resulting MTD partition.
49 the MTD partition named "xip_fs" on the /mnt mountpoint:
51 mount -t cramfs mtd:xip_fs /mnt
|
| /kernel/linux/linux-5.10/fs/cramfs/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
8 file system for ROM based embedded systems. CramFs is read-only,
20 purpose to remain small and low on RAM usage. It is most suitable
21 for small embedded systems. If you have ample RAM to spare, you may
37 depends on CRAMFS && CRAMFS <= MTD
47 MTD device capable of direct memory mapping e.g. from
48 the 'physmap' map driver or a resulting MTD partition.
50 the MTD partition named "xip_fs" on the /mnt mountpoint:
52 mount -t cramfs mtd:xip_fs /mnt
|
| /kernel/linux/linux-5.10/drivers/mtd/ |
| D | Kconfig | 1 menuconfig MTD config
2 tristate "Memory Technology Device (MTD) support"
5 Memory Technology Devices are flash, RAM and similar chips, often
7 will provide the generic support for MTD drivers to register
8 themselves with the kernel and for potential users of MTD devices
11 particular hardware and users of MTD devices. If unsure, say N.
13 if MTD
16 tristate "MTD tests support (DANGEROUS)"
19 This option includes various MTD tests into compilation. The tests
23 WARNING: some of the tests will ERASE entire MTD device which they
[all …]
|
| D | mtdblock_ro.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * Simple read-only (writable only for RAM) mtdblock driver
5 * Copyright © 2001-2010 David Woodhouse <dwmw2@infradead.org>
10 #include <linux/mtd/mtd.h>
11 #include <linux/mtd/blktrans.h>
20 if (mtd_read(dev->mtd, (block * 512), 512, &retlen, buf)) in mtdblock_readsect()
30 if (mtd_write(dev->mtd, (block * 512), 512, &retlen, buf)) in mtdblock_writesect()
35 static void mtdblock_add_mtd(struct mtd_blktrans_ops *tr, struct mtd_info *mtd) in mtdblock_add_mtd() argument
42 dev->mtd = mtd; in mtdblock_add_mtd()
43 dev->devnum = mtd->index; in mtdblock_add_mtd()
[all …]
|
| /kernel/linux/linux-4.19/fs/romfs/ |
| D | Kconfig | 3 depends on BLOCK || MTD
4 ---help---
5 This is a very small read-only file system mainly intended for
6 initial ram disks of installation disks, but it could be used for
7 other read-only media as well. Read
29 bool "Block device-backed ROM file system support"
39 bool "MTD-backed ROM file system support"
40 depends on MTD=y || (ROMFS_FS=m && MTD)
42 This permits ROMFS to use MTD based devices directly, without the
44 also allows direct mapping of MTD devices through romfs files under
[all …]
|
| /kernel/linux/linux-5.10/fs/romfs/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
4 depends on BLOCK || MTD
6 This is a very small read-only file system mainly intended for
7 initial ram disks of installation disks, but it could be used for
8 other read-only media as well. Read
30 bool "Block device-backed ROM file system support"
40 bool "MTD-backed ROM file system support"
41 depends on MTD=y || (ROMFS_FS=m && MTD)
43 This permits ROMFS to use MTD based devices directly, without the
45 also allows direct mapping of MTD devices through romfs files under
[all …]
|
| /kernel/linux/linux-4.19/drivers/mtd/ |
| D | Kconfig | 1 menuconfig MTD config
2 tristate "Memory Technology Device (MTD) support"
4 Memory Technology Devices are flash, RAM and similar chips, often
6 will provide the generic support for MTD drivers to register
7 themselves with the kernel and for potential users of MTD devices
10 particular hardware and users of MTD devices. If unsure, say N.
12 if MTD
15 tristate "MTD tests support (DANGEROUS)"
18 This option includes various MTD tests into compilation. The tests
22 WARNING: some of the tests will ERASE entire MTD device which they
[all …]
|