linux/mtd/ubi.h

29  * enum ubi_open_mode - UBI volume open mode constants.
34  * UBI_METAONLY: modify only the volume meta-data,
35  *  i.e. the data stored in the volume table, but not in any of volume LEBs.
45  * struct ubi_volume_info - UBI volume description data structure.
46  * @vol_id: volume ID
47  * @ubi_num: UBI device number this volume belongs to
48  * @size: how many physical eraseblocks are reserved for this volume
49  * @used_bytes: how many bytes of data this volume contains
50  * @used_ebs: how many physical eraseblocks of this volume actually contain any
52  * @vol_type: volume type (%UBI_DYNAMIC_VOLUME or %UBI_STATIC_VOLUME)
53  * @corrupted: non-zero if the volume is corrupted (static volumes only)
54  * @upd_marker: non-zero if the volume has update marker set
55  * @alignment: volume alignment
57  *                   this volume
58  * @name_len: volume name length
59  * @name: volume name
60  * @cdev: UBI volume character device major and minor numbers
63  * for dynamic ones. This is because UBI does not care about dynamic volume
64  * data protection and only cares about protecting static volume data.
66  * The @upd_marker flag is set if the volume update operation was interrupted.
67  * Before touching the volume data during the update operation, UBI first sets
68  * the update marker flag for this volume. If the volume update operation was
70  * is set, the contents of the volume is certainly damaged and a new volume
75  *     o the @corrupted flag means that this static volume is corrupted for some
76  *       reasons, but not because an interrupted volume update
77  *     o the @upd_marker field means that the volume is damaged because of an
83  * volumes and contain the number of bytes stored in this static volume and how
89  * of the UBI volume. Indeed, the logical eraseblock size depends on the
91  * because of the volume alignment (@alignment), the usable size of logical
92  * eraseblocks if a volume may be less. The following equation is true:
100  * volume logical eraseblock sizes.
194  * Volume notification types.
195  * @UBI_VOLUME_ADDED: a volume has been added (an UBI device was attached or a
196  *                    volume was created)
197  * @UBI_VOLUME_REMOVED: a volume has been removed (an UBI device was detached
198  *			or a volume was removed)
199  * @UBI_VOLUME_RESIZED: a volume has been re-sized
200  * @UBI_VOLUME_RENAMED: a volume has been re-named
201  * @UBI_VOLUME_UPDATED: data has been written to a volume
203  * These constants define which type of event has happened when a volume
217  * @vi: UBI volume description object
221  * UBI device and UBI volume the notification informs about.