diff options
Diffstat (limited to 'include/linux/mtd/mtd.h')
| -rw-r--r-- | include/linux/mtd/mtd.h | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/include/linux/mtd/mtd.h b/include/linux/mtd/mtd.h index a86c4fa93115..cd0be91bdefa 100644 --- a/include/linux/mtd/mtd.h +++ b/include/linux/mtd/mtd.h | |||
| @@ -67,9 +67,11 @@ struct mtd_erase_region_info { | |||
| 67 | * @datbuf: data buffer - if NULL only oob data are read/written | 67 | * @datbuf: data buffer - if NULL only oob data are read/written |
| 68 | * @oobbuf: oob data buffer | 68 | * @oobbuf: oob data buffer |
| 69 | * | 69 | * |
| 70 | * Note, it is allowed to read more than one OOB area at one go, but not write. | 70 | * Note, some MTD drivers do not allow you to write more than one OOB area at |
| 71 | * The interface assumes that the OOB write requests program only one page's | 71 | * one go. If you try to do that on such an MTD device, -EINVAL will be |
| 72 | * OOB area. | 72 | * returned. If you want to make your implementation portable on all kind of MTD |
| 73 | * devices you should split the write request into several sub-requests when the | ||
| 74 | * request crosses a page boundary. | ||
| 73 | */ | 75 | */ |
| 74 | struct mtd_oob_ops { | 76 | struct mtd_oob_ops { |
| 75 | unsigned int mode; | 77 | unsigned int mode; |
