mtd/ubi/io.c

92  * ubi_io_read - read data from a physical eraseblock.
95  * @pnum: physical eraseblock number to read from
96  * @offset: offset within the physical eraseblock from where to read
99  * This function reads data from offset @offset of physical eraseblock @pnum
218  * ubi_io_write - write data to a physical eraseblock.
221  * @pnum: physical eraseblock number to write to
222  * @offset: offset within the physical eraseblock where to write
226  * of physical eraseblock @pnum. If all the data were successfully written,
228  * error code. If %-EIO is returned, the physical eraseblock most probably went
264 		 * We write to the data area of the physical eraseblock. Make  in ubi_io_write()
311  * do_sync_erase - synchronously erase a physical eraseblock.
313  * @pnum: the physical eraseblock number to erase
315  * This function synchronously erases physical eraseblock @pnum and returns
317  * %-EIO is returned, the physical eraseblock most probably went bad.
363 /* Patterns to write to a physical eraseblock when torturing it */
367  * torture_peb - test a supposedly bad physical eraseblock.
369  * @pnum: the physical eraseblock number to test
371  * This function returns %-EIO if the physical eraseblock did not pass the
432 		 * physical eraseblock which means something is wrong with it.  in torture_peb()
444  * @pnum: physical eraseblock number to prepare
520  * ubi_io_sync_erase - synchronously erase a physical eraseblock.
522  * @pnum: physical eraseblock number to erase
523  * @torture: if this physical eraseblock has to be tortured
525  * This function synchronously erases physical eraseblock @pnum. If @torture
526  * flag is not zero, the physical eraseblock is checked by means of writing
528  * the physical eraseblock is erased more than once.
532  * codes in case of other errors. Note, %-EIO means that the physical
577  * ubi_io_is_bad - check if a physical eraseblock is bad.
579  * @pnum: the physical eraseblock number to check
581  * This function returns a positive number if the physical eraseblock is bad,
606  * ubi_io_mark_bad - mark a physical eraseblock as bad.
608  * @pnum: the physical eraseblock number to mark
687  * @pnum: physical eraseblock to read from
692  * This function reads erase counter header from physical eraseblock @pnum and
738 		 * 0xFF. If yes, this physical eraseblock is assumed to be  in ubi_io_read_ec_hdr()
742 			/* The physical eraseblock is supposedly empty */  in ubi_io_read_ec_hdr()
832  * @pnum: physical eraseblock to write to
835  * This function writes erase counter header described by @ec_hdr to physical
841  * case of failure. If %-EIO is returned, the physical eraseblock most probably
998  * @pnum: physical eraseblock number to read from
1002  * This function reads the volume identifier header from physical eraseblock
1111  * @pnum: the physical eraseblock number to write to
1115  * physical eraseblock @pnum. This function automatically fills the
1120  * case of failure. If %-EIO is returned, the physical eraseblock probably went
1159  * self_check_not_bad - ensure that a physical eraseblock is not bad.
1161  * @pnum: physical eraseblock number to check
1163  * This function returns zero if the physical eraseblock is good, %-EINVAL if
1185  * @pnum: physical eraseblock number the erase counter header belongs to
1224  * @pnum: the physical eraseblock number to check
1268  * @pnum: physical eraseblock number the volume identifier header belongs to
1309  * @pnum: the physical eraseblock number to check
1359  * @pnum: physical eraseblock number the data were written to
1360  * @offset: offset within the physical eraseblock the data were written to
1424  * @pnum: the physical eraseblock number to check
1425  * @offset: the starting offset within the physical eraseblock to check
1429  * @offset of the physical eraseblock @pnum, and a negative error code if not