1What: /sys/class/mtd/ 2Date: April 2009 3KernelVersion: 2.6.29 4Contact: linux-mtd@lists.infradead.org 5Description: 6 The mtd/ class subdirectory belongs to the MTD subsystem 7 (MTD core). 8 9What: /sys/class/mtd/mtdX/ 10Date: April 2009 11KernelVersion: 2.6.29 12Contact: linux-mtd@lists.infradead.org 13Description: 14 The /sys/class/mtd/mtd{0,1,2,3,...} directories correspond 15 to each /dev/mtdX character device. These may represent 16 physical/simulated flash devices, partitions on a flash 17 device, or concatenated flash devices. They exist regardless 18 of whether CONFIG_MTD_CHAR is actually enabled. 19 20What: /sys/class/mtd/mtdXro/ 21Date: April 2009 22KernelVersion: 2.6.29 23Contact: linux-mtd@lists.infradead.org 24Description: 25 These directories provide the corresponding read-only device 26 nodes for /sys/class/mtd/mtdX/ . They are only created 27 (for the benefit of udev) if CONFIG_MTD_CHAR is enabled. 28 29What: /sys/class/mtd/mtdX/dev 30Date: April 2009 31KernelVersion: 2.6.29 32Contact: linux-mtd@lists.infradead.org 33Description: 34 Major and minor numbers of the character device corresponding 35 to this MTD device (in <major>:<minor> format). This is the 36 read-write device so <minor> will be even. 37 38What: /sys/class/mtd/mtdXro/dev 39Date: April 2009 40KernelVersion: 2.6.29 41Contact: linux-mtd@lists.infradead.org 42Description: 43 Major and minor numbers of the character device corresponding 44 to the read-only variant of thie MTD device (in 45 <major>:<minor> format). In this case <minor> will be odd. 46 47What: /sys/class/mtd/mtdX/erasesize 48Date: April 2009 49KernelVersion: 2.6.29 50Contact: linux-mtd@lists.infradead.org 51Description: 52 "Major" erase size for the device. If numeraseregions is 53 zero, this is the eraseblock size for the entire device. 54 Otherwise, the MEMGETREGIONCOUNT/MEMGETREGIONINFO ioctls 55 can be used to determine the actual eraseblock layout. 56 57What: /sys/class/mtd/mtdX/flags 58Date: April 2009 59KernelVersion: 2.6.29 60Contact: linux-mtd@lists.infradead.org 61Description: 62 A hexadecimal value representing the device flags, ORed 63 together: 64 65 0x0400: MTD_WRITEABLE - device is writable 66 0x0800: MTD_BIT_WRITEABLE - single bits can be flipped 67 0x1000: MTD_NO_ERASE - no erase necessary 68 0x2000: MTD_POWERUP_LOCK - always locked after reset 69 70What: /sys/class/mtd/mtdX/name 71Date: April 2009 72KernelVersion: 2.6.29 73Contact: linux-mtd@lists.infradead.org 74Description: 75 A human-readable ASCII name for the device or partition. 76 This will match the name in /proc/mtd . 77 78What: /sys/class/mtd/mtdX/numeraseregions 79Date: April 2009 80KernelVersion: 2.6.29 81Contact: linux-mtd@lists.infradead.org 82Description: 83 For devices that have variable eraseblock sizes, this 84 provides the total number of erase regions. Otherwise, 85 it will read back as zero. 86 87What: /sys/class/mtd/mtdX/oobsize 88Date: April 2009 89KernelVersion: 2.6.29 90Contact: linux-mtd@lists.infradead.org 91Description: 92 Number of OOB bytes per page. 93 94What: /sys/class/mtd/mtdX/size 95Date: April 2009 96KernelVersion: 2.6.29 97Contact: linux-mtd@lists.infradead.org 98Description: 99 Total size of the device/partition, in bytes. 100 101What: /sys/class/mtd/mtdX/type 102Date: April 2009 103KernelVersion: 2.6.29 104Contact: linux-mtd@lists.infradead.org 105Description: 106 One of the following ASCII strings, representing the device 107 type: 108 109 absent, ram, rom, nor, nand, dataflash, ubi, unknown 110 111What: /sys/class/mtd/mtdX/writesize 112Date: April 2009 113KernelVersion: 2.6.29 114Contact: linux-mtd@lists.infradead.org 115Description: 116 Minimal writable flash unit size. This will always be 117 a positive integer. 118 119 In the case of NOR flash it is 1 (even though individual 120 bits can be cleared). 121 122 In the case of NAND flash it is one NAND page (or a 123 half page, or a quarter page). 124 125 In the case of ECC NOR, it is the ECC block size. 126