2017-11-01 14:09:13 +00:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0+ WITH Linux-syscall-note */
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
2010-08-08 19:58:20 +00:00
|
|
|
* Copyright © 1999-2010 David Woodhouse <dwmw2@infradead.org> et al.
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
* the Free Software Foundation; either version 2 of the License, or
|
|
|
|
* (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
* along with this program; if not, write to the Free Software
|
|
|
|
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
|
|
|
|
*
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef __MTD_ABI_H__
|
|
|
|
#define __MTD_ABI_H__
|
|
|
|
|
2009-02-25 23:51:41 +00:00
|
|
|
#include <linux/types.h>
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
struct erase_info_user {
|
2009-02-25 23:51:41 +00:00
|
|
|
__u32 start;
|
|
|
|
__u32 length;
|
2005-04-16 22:20:36 +00:00
|
|
|
};
|
|
|
|
|
2009-04-09 05:52:28 +00:00
|
|
|
struct erase_info_user64 {
|
|
|
|
__u64 start;
|
|
|
|
__u64 length;
|
|
|
|
};
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
struct mtd_oob_buf {
|
2009-02-25 23:51:41 +00:00
|
|
|
__u32 start;
|
|
|
|
__u32 length;
|
2005-04-16 22:20:36 +00:00
|
|
|
unsigned char __user *ptr;
|
|
|
|
};
|
|
|
|
|
2009-04-09 05:53:49 +00:00
|
|
|
struct mtd_oob_buf64 {
|
|
|
|
__u64 start;
|
|
|
|
__u32 pad;
|
|
|
|
__u32 length;
|
|
|
|
__u64 usr_ptr;
|
|
|
|
};
|
|
|
|
|
2011-08-31 01:45:44 +00:00
|
|
|
/**
|
2011-08-31 01:45:40 +00:00
|
|
|
* MTD operation modes
|
2011-08-31 01:45:39 +00:00
|
|
|
*
|
2011-08-31 01:45:44 +00:00
|
|
|
* @MTD_OPS_PLACE_OOB: OOB data are placed at the given offset (default)
|
|
|
|
* @MTD_OPS_AUTO_OOB: OOB data are automatically placed at the free areas
|
2011-08-31 01:45:40 +00:00
|
|
|
* which are defined by the internal ecclayout
|
2011-08-31 01:45:44 +00:00
|
|
|
* @MTD_OPS_RAW: data are transferred as-is, with no error correction;
|
|
|
|
* this mode implies %MTD_OPS_PLACE_OOB
|
|
|
|
*
|
mtdchar: add MEMREAD ioctl
User-space applications making use of MTD devices via /dev/mtd*
character devices currently have limited capabilities for reading data:
- only deprecated methods of accessing OOB layout information exist,
- there is no way to explicitly specify MTD operation mode to use; it
is auto-selected based on the MTD file mode (MTD_FILE_MODE_*) set
for the character device; in particular, this prevents using
MTD_OPS_AUTO_OOB for reads,
- all existing user-space interfaces which cause mtd_read() or
mtd_read_oob() to be called (via mtdchar_read() and
mtdchar_read_oob(), respectively) return success even when those
functions return -EUCLEAN or -EBADMSG; this renders user-space
applications using these interfaces unaware of any corrected
bitflips or uncorrectable ECC errors detected during reads.
Note that the existing MEMWRITE ioctl allows the MTD operation mode to
be explicitly set, allowing user-space applications to write page data
and OOB data without requiring them to know anything about the OOB
layout of the MTD device they are writing to (MTD_OPS_AUTO_OOB). Also,
the MEMWRITE ioctl does not mangle the return value of mtd_write_oob().
Add a new ioctl, MEMREAD, which addresses the above issues. It is
intended to be a read-side counterpart of the existing MEMWRITE ioctl.
Similarly to the latter, the read operation is performed in a loop which
processes at most mtd->erasesize bytes in each iteration. This is done
to prevent unbounded memory allocations caused by calling kmalloc() with
the 'size' argument taken directly from the struct mtd_read_req provided
by user space. However, the new ioctl is implemented so that the values
it returns match those that would have been returned if just a single
mtd_read_oob() call was issued to handle the entire read operation in
one go.
Note that while just returning -EUCLEAN or -EBADMSG to user space would
already be a valid and useful indication of the ECC algorithm detecting
errors during a read operation, that signal would not be granular enough
to cover all use cases. For example, knowing the maximum number of
bitflips detected in a single ECC step during a read operation performed
on a given page may be useful when dealing with an MTD partition whose
ECC layout varies across pages (e.g. a partition consisting of a
bootloader area using a "custom" ECC layout followed by data pages using
a "standard" ECC layout). To address that, include ECC statistics in
the structure returned to user space by the new MEMREAD ioctl.
Link: https://www.infradead.org/pipermail/linux-mtd/2016-April/067085.html
Suggested-by: Boris Brezillon <boris.brezillon@collabora.com>
Signed-off-by: Michał Kępień <kernel@kempniu.pl>
Acked-by: Richard Weinberger <richard@nod.at>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20220629125737.14418-5-kernel@kempniu.pl
2022-06-29 12:57:37 +00:00
|
|
|
* These modes can be passed to ioctl(MEMWRITE) and ioctl(MEMREAD); they are
|
|
|
|
* also used internally. See notes on "MTD file modes" for discussion on
|
|
|
|
* %MTD_OPS_RAW vs. %MTD_FILE_MODE_RAW.
|
2011-08-31 01:45:39 +00:00
|
|
|
*/
|
|
|
|
enum {
|
2011-08-31 01:45:40 +00:00
|
|
|
MTD_OPS_PLACE_OOB = 0,
|
|
|
|
MTD_OPS_AUTO_OOB = 1,
|
|
|
|
MTD_OPS_RAW = 2,
|
2011-08-31 01:45:39 +00:00
|
|
|
};
|
|
|
|
|
2011-08-31 01:45:44 +00:00
|
|
|
/**
|
|
|
|
* struct mtd_write_req - data structure for requesting a write operation
|
|
|
|
*
|
|
|
|
* @start: start address
|
2022-05-16 07:06:00 +00:00
|
|
|
* @len: length of data buffer (only lower 32 bits are used)
|
|
|
|
* @ooblen: length of OOB buffer (only lower 32 bits are used)
|
2011-08-31 01:45:44 +00:00
|
|
|
* @usr_data: user-provided data buffer
|
|
|
|
* @usr_oob: user-provided OOB buffer
|
|
|
|
* @mode: MTD mode (see "MTD operation modes")
|
|
|
|
* @padding: reserved, must be set to 0
|
|
|
|
*
|
|
|
|
* This structure supports ioctl(MEMWRITE) operations, allowing data and/or OOB
|
|
|
|
* writes in various modes. To write to OOB-only, set @usr_data == NULL, and to
|
|
|
|
* write data-only, set @usr_oob == NULL. However, setting both @usr_data and
|
|
|
|
* @usr_oob to NULL is not allowed.
|
|
|
|
*/
|
2011-09-09 16:59:03 +00:00
|
|
|
struct mtd_write_req {
|
|
|
|
__u64 start;
|
|
|
|
__u64 len;
|
|
|
|
__u64 ooblen;
|
|
|
|
__u64 usr_data;
|
|
|
|
__u64 usr_oob;
|
|
|
|
__u8 mode;
|
|
|
|
__u8 padding[7];
|
|
|
|
};
|
|
|
|
|
mtdchar: add MEMREAD ioctl
User-space applications making use of MTD devices via /dev/mtd*
character devices currently have limited capabilities for reading data:
- only deprecated methods of accessing OOB layout information exist,
- there is no way to explicitly specify MTD operation mode to use; it
is auto-selected based on the MTD file mode (MTD_FILE_MODE_*) set
for the character device; in particular, this prevents using
MTD_OPS_AUTO_OOB for reads,
- all existing user-space interfaces which cause mtd_read() or
mtd_read_oob() to be called (via mtdchar_read() and
mtdchar_read_oob(), respectively) return success even when those
functions return -EUCLEAN or -EBADMSG; this renders user-space
applications using these interfaces unaware of any corrected
bitflips or uncorrectable ECC errors detected during reads.
Note that the existing MEMWRITE ioctl allows the MTD operation mode to
be explicitly set, allowing user-space applications to write page data
and OOB data without requiring them to know anything about the OOB
layout of the MTD device they are writing to (MTD_OPS_AUTO_OOB). Also,
the MEMWRITE ioctl does not mangle the return value of mtd_write_oob().
Add a new ioctl, MEMREAD, which addresses the above issues. It is
intended to be a read-side counterpart of the existing MEMWRITE ioctl.
Similarly to the latter, the read operation is performed in a loop which
processes at most mtd->erasesize bytes in each iteration. This is done
to prevent unbounded memory allocations caused by calling kmalloc() with
the 'size' argument taken directly from the struct mtd_read_req provided
by user space. However, the new ioctl is implemented so that the values
it returns match those that would have been returned if just a single
mtd_read_oob() call was issued to handle the entire read operation in
one go.
Note that while just returning -EUCLEAN or -EBADMSG to user space would
already be a valid and useful indication of the ECC algorithm detecting
errors during a read operation, that signal would not be granular enough
to cover all use cases. For example, knowing the maximum number of
bitflips detected in a single ECC step during a read operation performed
on a given page may be useful when dealing with an MTD partition whose
ECC layout varies across pages (e.g. a partition consisting of a
bootloader area using a "custom" ECC layout followed by data pages using
a "standard" ECC layout). To address that, include ECC statistics in
the structure returned to user space by the new MEMREAD ioctl.
Link: https://www.infradead.org/pipermail/linux-mtd/2016-April/067085.html
Suggested-by: Boris Brezillon <boris.brezillon@collabora.com>
Signed-off-by: Michał Kępień <kernel@kempniu.pl>
Acked-by: Richard Weinberger <richard@nod.at>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20220629125737.14418-5-kernel@kempniu.pl
2022-06-29 12:57:37 +00:00
|
|
|
/**
|
|
|
|
* struct mtd_read_req_ecc_stats - ECC statistics for a read operation
|
|
|
|
*
|
|
|
|
* @uncorrectable_errors: the number of uncorrectable errors that happened
|
|
|
|
* during the read operation
|
|
|
|
* @corrected_bitflips: the number of bitflips corrected during the read
|
|
|
|
* operation
|
|
|
|
* @max_bitflips: the maximum number of bitflips detected in any single ECC
|
|
|
|
* step for the data read during the operation; this information
|
|
|
|
* can be used to decide whether the data stored in a specific
|
|
|
|
* region of the MTD device should be moved somewhere else to
|
|
|
|
* avoid data loss.
|
|
|
|
*/
|
|
|
|
struct mtd_read_req_ecc_stats {
|
|
|
|
__u32 uncorrectable_errors;
|
|
|
|
__u32 corrected_bitflips;
|
|
|
|
__u32 max_bitflips;
|
|
|
|
};
|
|
|
|
|
|
|
|
/**
|
|
|
|
* struct mtd_read_req - data structure for requesting a read operation
|
|
|
|
*
|
|
|
|
* @start: start address
|
|
|
|
* @len: length of data buffer (only lower 32 bits are used)
|
|
|
|
* @ooblen: length of OOB buffer (only lower 32 bits are used)
|
|
|
|
* @usr_data: user-provided data buffer
|
|
|
|
* @usr_oob: user-provided OOB buffer
|
|
|
|
* @mode: MTD mode (see "MTD operation modes")
|
|
|
|
* @padding: reserved, must be set to 0
|
|
|
|
* @ecc_stats: ECC statistics for the read operation
|
|
|
|
*
|
|
|
|
* This structure supports ioctl(MEMREAD) operations, allowing data and/or OOB
|
|
|
|
* reads in various modes. To read from OOB-only, set @usr_data == NULL, and to
|
|
|
|
* read data-only, set @usr_oob == NULL. However, setting both @usr_data and
|
|
|
|
* @usr_oob to NULL is not allowed.
|
|
|
|
*/
|
|
|
|
struct mtd_read_req {
|
|
|
|
__u64 start;
|
|
|
|
__u64 len;
|
|
|
|
__u64 ooblen;
|
|
|
|
__u64 usr_data;
|
|
|
|
__u64 usr_oob;
|
|
|
|
__u8 mode;
|
|
|
|
__u8 padding[7];
|
|
|
|
struct mtd_read_req_ecc_stats ecc_stats;
|
|
|
|
};
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
#define MTD_ABSENT 0
|
2006-06-14 20:39:48 +00:00
|
|
|
#define MTD_RAM 1
|
|
|
|
#define MTD_ROM 2
|
2005-04-16 22:20:36 +00:00
|
|
|
#define MTD_NORFLASH 3
|
2013-09-25 06:58:16 +00:00
|
|
|
#define MTD_NANDFLASH 4 /* SLC NAND */
|
2005-02-09 09:17:45 +00:00
|
|
|
#define MTD_DATAFLASH 6
|
UBI: Unsorted Block Images
UBI (Latin: "where?") manages multiple logical volumes on a single
flash device, specifically supporting NAND flash devices. UBI provides
a flexible partitioning concept which still allows for wear-levelling
across the whole flash device.
In a sense, UBI may be compared to the Logical Volume Manager
(LVM). Whereas LVM maps logical sector numbers to physical HDD sector
numbers, UBI maps logical eraseblocks to physical eraseblocks.
More information may be found at
http://www.linux-mtd.infradead.org/doc/ubi.html
Partitioning/Re-partitioning
An UBI volume occupies a certain number of erase blocks. This is
limited by a configured maximum volume size, which could also be
viewed as the partition size. Each individual UBI volume's size can
be changed independently of the other UBI volumes, provided that the
sum of all volume sizes doesn't exceed a certain limit.
UBI supports dynamic volumes and static volumes. Static volumes are
read-only and their contents are protected by CRC check sums.
Bad eraseblocks handling
UBI transparently handles bad eraseblocks. When a physical
eraseblock becomes bad, it is substituted by a good physical
eraseblock, and the user does not even notice this.
Scrubbing
On a NAND flash bit flips can occur on any write operation,
sometimes also on read. If bit flips persist on the device, at first
they can still be corrected by ECC, but once they accumulate,
correction will become impossible. Thus it is best to actively scrub
the affected eraseblock, by first copying it to a free eraseblock
and then erasing the original. The UBI layer performs this type of
scrubbing under the covers, transparently to the UBI volume users.
Erase Counts
UBI maintains an erase count header per eraseblock. This frees
higher-level layers (like file systems) from doing this and allows
for centralized erase count management instead. The erase counts are
used by the wear-levelling algorithm in the UBI layer. The algorithm
itself is exchangeable.
Booting from NAND
For booting directly from NAND flash the hardware must at least be
capable of fetching and executing a small portion of the NAND
flash. Some NAND flash controllers have this kind of support. They
usually limit the window to a few kilobytes in erase block 0. This
"initial program loader" (IPL) must then contain sufficient logic to
load and execute the next boot phase.
Due to bad eraseblocks, which may be randomly scattered over the
flash device, it is problematic to store the "secondary program
loader" (SPL) statically. Also, due to bit-flips it may become
corrupted over time. UBI allows to solve this problem gracefully by
storing the SPL in a small static UBI volume.
UBI volumes vs. static partitions
UBI volumes are still very similar to static MTD partitions:
* both consist of eraseblocks (logical eraseblocks in case of UBI
volumes, and physical eraseblocks in case of static partitions;
* both support three basic operations - read, write, erase.
But UBI volumes have the following advantages over traditional
static MTD partitions:
* there are no eraseblock wear-leveling constraints in case of UBI
volumes, so the user should not care about this;
* there are no bit-flips and bad eraseblocks in case of UBI volumes.
So, UBI volumes may be considered as flash devices with relaxed
restrictions.
Where can it be found?
Documentation, kernel code and applications can be found in the MTD
gits.
What are the applications for?
The applications help to create binary flash images for two purposes: pfi
files (partial flash images) for in-system update of UBI volumes, and plain
binary images, with or without OOB data in case of NAND, for a manufacturing
step. Furthermore some tools are/and will be created that allow flash content
analysis after a system has crashed..
Who did UBI?
The original ideas, where UBI is based on, were developed by Andreas
Arnez, Frank Haverkamp and Thomas Gleixner. Josh W. Boyer and some others
were involved too. The implementation of the kernel layer was done by Artem
B. Bityutskiy. The user-space applications and tools were written by Oliver
Lohmann with contributions from Frank Haverkamp, Andreas Arnez, and Artem.
Joern Engel contributed a patch which modifies JFFS2 so that it can be run on
a UBI volume. Thomas Gleixner did modifications to the NAND layer. Alexander
Schmidt made some testing work as well as core functionality improvements.
Signed-off-by: Artem B. Bityutskiy <dedekind@linutronix.de>
Signed-off-by: Frank Haverkamp <haver@vnet.ibm.com>
2006-06-27 08:22:22 +00:00
|
|
|
#define MTD_UBIVOLUME 7
|
2013-09-25 06:58:16 +00:00
|
|
|
#define MTD_MLCNANDFLASH 8 /* MLC NAND (including TLC) */
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-05-22 21:17:23 +00:00
|
|
|
#define MTD_WRITEABLE 0x400 /* Device is writeable */
|
2006-05-22 21:18:29 +00:00
|
|
|
#define MTD_BIT_WRITEABLE 0x800 /* Single bits can be flipped */
|
2006-05-30 12:25:24 +00:00
|
|
|
#define MTD_NO_ERASE 0x1000 /* No erase necessary */
|
2008-01-30 18:25:49 +00:00
|
|
|
#define MTD_POWERUP_LOCK 0x2000 /* Always locked after reset */
|
2020-05-03 15:53:37 +00:00
|
|
|
#define MTD_SLC_ON_MLC_EMULATION 0x4000 /* Emulate SLC behavior on MLC NANDs */
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Some common devices / combinations of capabilities */
|
2005-04-16 22:20:36 +00:00
|
|
|
#define MTD_CAP_ROM 0
|
2006-05-30 12:25:24 +00:00
|
|
|
#define MTD_CAP_RAM (MTD_WRITEABLE | MTD_BIT_WRITEABLE | MTD_NO_ERASE)
|
2006-05-22 21:18:29 +00:00
|
|
|
#define MTD_CAP_NORFLASH (MTD_WRITEABLE | MTD_BIT_WRITEABLE)
|
2006-05-22 21:17:23 +00:00
|
|
|
#define MTD_CAP_NANDFLASH (MTD_WRITEABLE)
|
2014-05-15 21:19:32 +00:00
|
|
|
#define MTD_CAP_NVRAM (MTD_WRITEABLE | MTD_BIT_WRITEABLE | MTD_NO_ERASE)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Obsolete ECC byte placement modes (used with obsolete MEMGETOOBSEL) */
|
2019-06-27 07:07:45 +00:00
|
|
|
#define MTD_NANDECC_OFF 0 /* Switch off ECC (Not recommended) */
|
|
|
|
#define MTD_NANDECC_PLACE 1 /* Use the given placement in the structure (YAFFS1 legacy mode) */
|
|
|
|
#define MTD_NANDECC_AUTOPLACE 2 /* Use the default placement scheme */
|
|
|
|
#define MTD_NANDECC_PLACEONLY 3 /* Use the given placement in the structure (Do not store ecc result on read) */
|
|
|
|
#define MTD_NANDECC_AUTOPL_USR 4 /* Use the given autoplacement scheme rather than using the default */
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2005-02-08 17:45:55 +00:00
|
|
|
/* OTP mode selection */
|
|
|
|
#define MTD_OTP_OFF 0
|
|
|
|
#define MTD_OTP_FACTORY 1
|
|
|
|
#define MTD_OTP_USER 2
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
struct mtd_info_user {
|
2009-02-25 23:51:41 +00:00
|
|
|
__u8 type;
|
|
|
|
__u32 flags;
|
2011-08-31 01:45:44 +00:00
|
|
|
__u32 size; /* Total size of the MTD */
|
2009-02-25 23:51:41 +00:00
|
|
|
__u32 erasesize;
|
|
|
|
__u32 writesize;
|
2011-08-31 01:45:44 +00:00
|
|
|
__u32 oobsize; /* Amount of OOB data per block (e.g. 16) */
|
2011-08-31 01:45:46 +00:00
|
|
|
__u64 padding; /* Old obsolete field; do not use */
|
2005-04-16 22:20:36 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
struct region_info_user {
|
2009-02-25 23:51:41 +00:00
|
|
|
__u32 offset; /* At which this region starts,
|
2011-08-31 01:45:44 +00:00
|
|
|
* from the beginning of the MTD */
|
|
|
|
__u32 erasesize; /* For this region */
|
|
|
|
__u32 numblocks; /* Number of blocks in this region */
|
2009-02-25 23:51:41 +00:00
|
|
|
__u32 regionindex;
|
2005-04-16 22:20:36 +00:00
|
|
|
};
|
|
|
|
|
2005-02-08 17:11:19 +00:00
|
|
|
struct otp_info {
|
2009-02-25 23:51:41 +00:00
|
|
|
__u32 start;
|
|
|
|
__u32 length;
|
|
|
|
__u32 locked;
|
2005-02-08 17:11:19 +00:00
|
|
|
};
|
|
|
|
|
2011-08-24 00:17:34 +00:00
|
|
|
/*
|
|
|
|
* Note, the following ioctl existed in the past and was removed:
|
|
|
|
* #define MEMSETOOBSEL _IOW('M', 9, struct nand_oobinfo)
|
|
|
|
* Try to avoid adding a new ioctl with the same ioctl number.
|
|
|
|
*/
|
|
|
|
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Get basic MTD characteristics info (better to use sysfs) */
|
2006-05-27 20:16:10 +00:00
|
|
|
#define MEMGETINFO _IOR('M', 1, struct mtd_info_user)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Erase segment of MTD */
|
2006-05-27 20:16:10 +00:00
|
|
|
#define MEMERASE _IOW('M', 2, struct erase_info_user)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Write out-of-band data from MTD */
|
2006-05-27 20:16:10 +00:00
|
|
|
#define MEMWRITEOOB _IOWR('M', 3, struct mtd_oob_buf)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Read out-of-band data from MTD */
|
2006-05-27 20:16:10 +00:00
|
|
|
#define MEMREADOOB _IOWR('M', 4, struct mtd_oob_buf)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Lock a chip (for MTD that supports it) */
|
2006-05-27 20:16:10 +00:00
|
|
|
#define MEMLOCK _IOW('M', 5, struct erase_info_user)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Unlock a chip (for MTD that supports it) */
|
2006-05-27 20:16:10 +00:00
|
|
|
#define MEMUNLOCK _IOW('M', 6, struct erase_info_user)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Get the number of different erase regions */
|
2005-04-16 22:20:36 +00:00
|
|
|
#define MEMGETREGIONCOUNT _IOR('M', 7, int)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Get information about the erase region for a specific index */
|
2005-04-16 22:20:36 +00:00
|
|
|
#define MEMGETREGIONINFO _IOWR('M', 8, struct region_info_user)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Get info about OOB modes (e.g., RAW, PLACE, AUTO) - legacy interface */
|
2005-04-16 22:20:36 +00:00
|
|
|
#define MEMGETOOBSEL _IOR('M', 10, struct nand_oobinfo)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Check if an eraseblock is bad */
|
make exported headers use strict posix types
A number of standard posix types are used in exported headers, which
is not allowed if __STRICT_KERNEL_NAMES is defined. In order to
get rid of the non-__STRICT_KERNEL_NAMES part and to make sane headers
the default, we have to change them all to safe types.
There are also still some leftovers in reiserfs_fs.h, elfcore.h
and coda.h, but these files have not compiled in user space for
a long time.
This leaves out the various integer types ({u_,u,}int{8,16,32,64}_t),
which we take care of separately.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: David Airlie <airlied@linux.ie>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Cc: netdev@vger.kernel.org
Cc: linux-ppp@vger.kernel.org
Cc: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>
Cc: David Woodhouse <dwmw2@infradead.org>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-02-25 23:51:39 +00:00
|
|
|
#define MEMGETBADBLOCK _IOW('M', 11, __kernel_loff_t)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Mark an eraseblock as bad */
|
make exported headers use strict posix types
A number of standard posix types are used in exported headers, which
is not allowed if __STRICT_KERNEL_NAMES is defined. In order to
get rid of the non-__STRICT_KERNEL_NAMES part and to make sane headers
the default, we have to change them all to safe types.
There are also still some leftovers in reiserfs_fs.h, elfcore.h
and coda.h, but these files have not compiled in user space for
a long time.
This leaves out the various integer types ({u_,u,}int{8,16,32,64}_t),
which we take care of separately.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: David Airlie <airlied@linux.ie>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Cc: netdev@vger.kernel.org
Cc: linux-ppp@vger.kernel.org
Cc: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>
Cc: David Woodhouse <dwmw2@infradead.org>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-02-25 23:51:39 +00:00
|
|
|
#define MEMSETBADBLOCK _IOW('M', 12, __kernel_loff_t)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Set OTP (One-Time Programmable) mode (factory vs. user) */
|
2005-02-08 17:45:55 +00:00
|
|
|
#define OTPSELECT _IOR('M', 13, int)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Get number of OTP (One-Time Programmable) regions */
|
2005-02-08 17:45:55 +00:00
|
|
|
#define OTPGETREGIONCOUNT _IOW('M', 14, int)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Get all OTP (One-Time Programmable) info about MTD */
|
2005-02-08 17:45:55 +00:00
|
|
|
#define OTPGETREGIONINFO _IOW('M', 15, struct otp_info)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Lock a given range of user data (must be in mode %MTD_FILE_MODE_OTP_USER) */
|
2006-05-27 20:16:10 +00:00
|
|
|
#define OTPLOCK _IOR('M', 16, struct otp_info)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Get ECC layout (deprecated) */
|
2010-08-25 01:12:00 +00:00
|
|
|
#define ECCGETLAYOUT _IOR('M', 17, struct nand_ecclayout_user)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Get statistics about corrected/uncorrected errors */
|
2006-05-29 22:37:34 +00:00
|
|
|
#define ECCGETSTATS _IOR('M', 18, struct mtd_ecc_stats)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Set MTD mode on a per-file-descriptor basis (see "MTD file modes") */
|
2006-05-29 22:37:34 +00:00
|
|
|
#define MTDFILEMODE _IO('M', 19)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Erase segment of MTD (supports 64-bit address) */
|
2009-04-09 05:52:28 +00:00
|
|
|
#define MEMERASE64 _IOW('M', 20, struct erase_info_user64)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Write data to OOB (64-bit version) */
|
2009-04-09 05:53:49 +00:00
|
|
|
#define MEMWRITEOOB64 _IOWR('M', 21, struct mtd_oob_buf64)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Read data from OOB (64-bit version) */
|
2009-04-09 05:53:49 +00:00
|
|
|
#define MEMREADOOB64 _IOWR('M', 22, struct mtd_oob_buf64)
|
2011-08-31 01:45:44 +00:00
|
|
|
/* Check if chip is locked (for MTD that supports it) */
|
2010-06-14 16:10:33 +00:00
|
|
|
#define MEMISLOCKED _IOR('M', 23, struct erase_info_user)
|
2011-08-31 01:45:44 +00:00
|
|
|
/*
|
|
|
|
* Most generic write interface; can write in-band and/or out-of-band in various
|
2011-12-12 21:24:59 +00:00
|
|
|
* modes (see "struct mtd_write_req"). This ioctl is not supported for flashes
|
|
|
|
* without OOB, e.g., NOR flash.
|
2011-08-31 01:45:44 +00:00
|
|
|
*/
|
2011-09-09 16:59:03 +00:00
|
|
|
#define MEMWRITE _IOWR('M', 24, struct mtd_write_req)
|
2021-03-03 20:18:19 +00:00
|
|
|
/* Erase a given range of user data (must be in mode %MTD_FILE_MODE_OTP_USER) */
|
|
|
|
#define OTPERASE _IOW('M', 25, struct otp_info)
|
mtdchar: add MEMREAD ioctl
User-space applications making use of MTD devices via /dev/mtd*
character devices currently have limited capabilities for reading data:
- only deprecated methods of accessing OOB layout information exist,
- there is no way to explicitly specify MTD operation mode to use; it
is auto-selected based on the MTD file mode (MTD_FILE_MODE_*) set
for the character device; in particular, this prevents using
MTD_OPS_AUTO_OOB for reads,
- all existing user-space interfaces which cause mtd_read() or
mtd_read_oob() to be called (via mtdchar_read() and
mtdchar_read_oob(), respectively) return success even when those
functions return -EUCLEAN or -EBADMSG; this renders user-space
applications using these interfaces unaware of any corrected
bitflips or uncorrectable ECC errors detected during reads.
Note that the existing MEMWRITE ioctl allows the MTD operation mode to
be explicitly set, allowing user-space applications to write page data
and OOB data without requiring them to know anything about the OOB
layout of the MTD device they are writing to (MTD_OPS_AUTO_OOB). Also,
the MEMWRITE ioctl does not mangle the return value of mtd_write_oob().
Add a new ioctl, MEMREAD, which addresses the above issues. It is
intended to be a read-side counterpart of the existing MEMWRITE ioctl.
Similarly to the latter, the read operation is performed in a loop which
processes at most mtd->erasesize bytes in each iteration. This is done
to prevent unbounded memory allocations caused by calling kmalloc() with
the 'size' argument taken directly from the struct mtd_read_req provided
by user space. However, the new ioctl is implemented so that the values
it returns match those that would have been returned if just a single
mtd_read_oob() call was issued to handle the entire read operation in
one go.
Note that while just returning -EUCLEAN or -EBADMSG to user space would
already be a valid and useful indication of the ECC algorithm detecting
errors during a read operation, that signal would not be granular enough
to cover all use cases. For example, knowing the maximum number of
bitflips detected in a single ECC step during a read operation performed
on a given page may be useful when dealing with an MTD partition whose
ECC layout varies across pages (e.g. a partition consisting of a
bootloader area using a "custom" ECC layout followed by data pages using
a "standard" ECC layout). To address that, include ECC statistics in
the structure returned to user space by the new MEMREAD ioctl.
Link: https://www.infradead.org/pipermail/linux-mtd/2016-April/067085.html
Suggested-by: Boris Brezillon <boris.brezillon@collabora.com>
Signed-off-by: Michał Kępień <kernel@kempniu.pl>
Acked-by: Richard Weinberger <richard@nod.at>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20220629125737.14418-5-kernel@kempniu.pl
2022-06-29 12:57:37 +00:00
|
|
|
/*
|
|
|
|
* Most generic read interface; can read in-band and/or out-of-band in various
|
|
|
|
* modes (see "struct mtd_read_req"). This ioctl is not supported for flashes
|
|
|
|
* without OOB, e.g., NOR flash.
|
|
|
|
*/
|
|
|
|
#define MEMREAD _IOWR('M', 26, struct mtd_read_req)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-05-27 20:16:10 +00:00
|
|
|
/*
|
|
|
|
* Obsolete legacy interface. Keep it in order not to break userspace
|
|
|
|
* interfaces
|
|
|
|
*/
|
2005-04-16 22:20:36 +00:00
|
|
|
struct nand_oobinfo {
|
2009-02-25 23:51:41 +00:00
|
|
|
__u32 useecc;
|
|
|
|
__u32 eccbytes;
|
|
|
|
__u32 oobfree[8][2];
|
|
|
|
__u32 eccpos[32];
|
2005-04-16 22:20:36 +00:00
|
|
|
};
|
|
|
|
|
2006-05-27 20:16:10 +00:00
|
|
|
struct nand_oobfree {
|
2009-02-25 23:51:41 +00:00
|
|
|
__u32 offset;
|
|
|
|
__u32 length;
|
2006-05-27 20:16:10 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#define MTD_MAX_OOBFREE_ENTRIES 8
|
2010-09-20 06:57:12 +00:00
|
|
|
#define MTD_MAX_ECCPOS_ENTRIES 64
|
2006-05-27 20:16:10 +00:00
|
|
|
/*
|
2010-09-20 06:57:12 +00:00
|
|
|
* OBSOLETE: ECC layout control structure. Exported to user-space via ioctl
|
|
|
|
* ECCGETLAYOUT for backwards compatbility and should not be mistaken as a
|
|
|
|
* complete set of ECC information. The ioctl truncates the larger internal
|
|
|
|
* structure to retain binary compatibility with the static declaration of the
|
|
|
|
* ioctl. Note that the "MTD_MAX_..._ENTRIES" macros represent the max size of
|
2016-02-04 09:16:18 +00:00
|
|
|
* the user struct, not the MAX size of the internal OOB layout representation.
|
2006-05-27 20:16:10 +00:00
|
|
|
*/
|
2010-08-25 01:12:00 +00:00
|
|
|
struct nand_ecclayout_user {
|
2009-02-25 23:51:41 +00:00
|
|
|
__u32 eccbytes;
|
2010-09-20 06:57:12 +00:00
|
|
|
__u32 eccpos[MTD_MAX_ECCPOS_ENTRIES];
|
2009-02-25 23:51:41 +00:00
|
|
|
__u32 oobavail;
|
2006-05-27 20:16:10 +00:00
|
|
|
struct nand_oobfree oobfree[MTD_MAX_OOBFREE_ENTRIES];
|
|
|
|
};
|
|
|
|
|
2006-05-29 22:37:34 +00:00
|
|
|
/**
|
2006-06-29 04:48:38 +00:00
|
|
|
* struct mtd_ecc_stats - error correction stats
|
2006-05-29 22:37:34 +00:00
|
|
|
*
|
|
|
|
* @corrected: number of corrected bits
|
|
|
|
* @failed: number of uncorrectable errors
|
|
|
|
* @badblocks: number of bad blocks in this partition
|
|
|
|
* @bbtblocks: number of blocks reserved for bad block tables
|
|
|
|
*/
|
|
|
|
struct mtd_ecc_stats {
|
2009-02-25 23:51:41 +00:00
|
|
|
__u32 corrected;
|
|
|
|
__u32 failed;
|
|
|
|
__u32 badblocks;
|
|
|
|
__u32 bbtblocks;
|
2006-05-29 22:37:34 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
2011-08-31 01:45:44 +00:00
|
|
|
* MTD file modes - for read/write access to MTD
|
|
|
|
*
|
|
|
|
* @MTD_FILE_MODE_NORMAL: OTP disabled, ECC enabled
|
|
|
|
* @MTD_FILE_MODE_OTP_FACTORY: OTP enabled in factory mode
|
|
|
|
* @MTD_FILE_MODE_OTP_USER: OTP enabled in user mode
|
|
|
|
* @MTD_FILE_MODE_RAW: OTP disabled, ECC disabled
|
|
|
|
*
|
2020-07-19 00:32:08 +00:00
|
|
|
* These modes can be set via ioctl(MTDFILEMODE). The mode will be retained
|
2011-08-31 01:45:44 +00:00
|
|
|
* separately for each open file descriptor.
|
|
|
|
*
|
|
|
|
* Note: %MTD_FILE_MODE_RAW provides the same functionality as %MTD_OPS_RAW -
|
|
|
|
* raw access to the flash, without error correction or autoplacement schemes.
|
|
|
|
* Wherever possible, the MTD_OPS_* mode will override the MTD_FILE_MODE_* mode
|
mtdchar: add MEMREAD ioctl
User-space applications making use of MTD devices via /dev/mtd*
character devices currently have limited capabilities for reading data:
- only deprecated methods of accessing OOB layout information exist,
- there is no way to explicitly specify MTD operation mode to use; it
is auto-selected based on the MTD file mode (MTD_FILE_MODE_*) set
for the character device; in particular, this prevents using
MTD_OPS_AUTO_OOB for reads,
- all existing user-space interfaces which cause mtd_read() or
mtd_read_oob() to be called (via mtdchar_read() and
mtdchar_read_oob(), respectively) return success even when those
functions return -EUCLEAN or -EBADMSG; this renders user-space
applications using these interfaces unaware of any corrected
bitflips or uncorrectable ECC errors detected during reads.
Note that the existing MEMWRITE ioctl allows the MTD operation mode to
be explicitly set, allowing user-space applications to write page data
and OOB data without requiring them to know anything about the OOB
layout of the MTD device they are writing to (MTD_OPS_AUTO_OOB). Also,
the MEMWRITE ioctl does not mangle the return value of mtd_write_oob().
Add a new ioctl, MEMREAD, which addresses the above issues. It is
intended to be a read-side counterpart of the existing MEMWRITE ioctl.
Similarly to the latter, the read operation is performed in a loop which
processes at most mtd->erasesize bytes in each iteration. This is done
to prevent unbounded memory allocations caused by calling kmalloc() with
the 'size' argument taken directly from the struct mtd_read_req provided
by user space. However, the new ioctl is implemented so that the values
it returns match those that would have been returned if just a single
mtd_read_oob() call was issued to handle the entire read operation in
one go.
Note that while just returning -EUCLEAN or -EBADMSG to user space would
already be a valid and useful indication of the ECC algorithm detecting
errors during a read operation, that signal would not be granular enough
to cover all use cases. For example, knowing the maximum number of
bitflips detected in a single ECC step during a read operation performed
on a given page may be useful when dealing with an MTD partition whose
ECC layout varies across pages (e.g. a partition consisting of a
bootloader area using a "custom" ECC layout followed by data pages using
a "standard" ECC layout). To address that, include ECC statistics in
the structure returned to user space by the new MEMREAD ioctl.
Link: https://www.infradead.org/pipermail/linux-mtd/2016-April/067085.html
Suggested-by: Boris Brezillon <boris.brezillon@collabora.com>
Signed-off-by: Michał Kępień <kernel@kempniu.pl>
Acked-by: Richard Weinberger <richard@nod.at>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20220629125737.14418-5-kernel@kempniu.pl
2022-06-29 12:57:37 +00:00
|
|
|
* (e.g., when using ioctl(MEMWRITE) or ioctl(MEMREAD)), but in some cases, the
|
|
|
|
* MTD_FILE_MODE is used out of necessity (e.g., `write()',
|
|
|
|
* ioctl(MEMWRITEOOB64)).
|
2006-05-29 22:37:34 +00:00
|
|
|
*/
|
|
|
|
enum mtd_file_modes {
|
2011-08-31 01:45:41 +00:00
|
|
|
MTD_FILE_MODE_NORMAL = MTD_OTP_OFF,
|
|
|
|
MTD_FILE_MODE_OTP_FACTORY = MTD_OTP_FACTORY,
|
|
|
|
MTD_FILE_MODE_OTP_USER = MTD_OTP_USER,
|
|
|
|
MTD_FILE_MODE_RAW,
|
2006-05-29 22:37:34 +00:00
|
|
|
};
|
|
|
|
|
2013-09-25 06:58:18 +00:00
|
|
|
static inline int mtd_type_is_nand_user(const struct mtd_info_user *mtd)
|
|
|
|
{
|
|
|
|
return mtd->type == MTD_NANDFLASH || mtd->type == MTD_MLCNANDFLASH;
|
|
|
|
}
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
#endif /* __MTD_ABI_H__ */
|