mtd/ubi/io.c

98  * ubi_io_read - read data from a physical eraseblock.
101  * @pnum: physical eraseblock number to read from
102  * @offset: offset within the physical eraseblock from where to read
105  * This function reads data from offset @offset of physical eraseblock @pnum
212  * ubi_io_write - write data to a physical eraseblock.
215  * @pnum: physical eraseblock number to write to
216  * @offset: offset within the physical eraseblock where to write
220  * of physical eraseblock @pnum. If all the data were successfully written,
222  * error code. If %-EIO is returned, the physical eraseblock most probably went
258 		 * We write to the data area of the physical eraseblock. Make  in ubi_io_write()
317  * do_sync_erase - synchronously erase a physical eraseblock.
319  * @pnum: the physical eraseblock number to erase
321  * This function synchronously erases physical eraseblock @pnum and returns
323  * %-EIO is returned, the physical eraseblock most probably went bad.
393 /* Patterns to write to a physical eraseblock when torturing it */
397  * torture_peb - test a supposedly bad physical eraseblock.
399  * @pnum: the physical eraseblock number to test
401  * This function returns %-EIO if the physical eraseblock did not pass the
462 		 * physical eraseblock which means something is wrong with it.  in torture_peb()
474  * @pnum: physical eraseblock number to prepare
546  * ubi_io_sync_erase - synchronously erase a physical eraseblock.
548  * @pnum: physical eraseblock number to erase
549  * @torture: if this physical eraseblock has to be tortured
551  * This function synchronously erases physical eraseblock @pnum. If @torture
552  * flag is not zero, the physical eraseblock is checked by means of writing
554  * the physical eraseblock is erased more than once.
558  * codes in case of other errors. Note, %-EIO means that the physical
596  * ubi_io_is_bad - check if a physical eraseblock is bad.
598  * @pnum: the physical eraseblock number to check
600  * This function returns a positive number if the physical eraseblock is bad,
625  * ubi_io_mark_bad - mark a physical eraseblock as bad.
627  * @pnum: the physical eraseblock number to mark
706  * @pnum: physical eraseblock to read from
711  * This function reads erase counter header from physical eraseblock @pnum and
757 		 * 0xFF. If yes, this physical eraseblock is assumed to be  in ubi_io_read_ec_hdr()
761 			/* The physical eraseblock is supposedly empty */  in ubi_io_read_ec_hdr()
822  * @pnum: physical eraseblock to write to
825  * This function writes erase counter header described by @ec_hdr to physical
831  * case of failure. If %-EIO is returned, the physical eraseblock most probably
985  * @pnum: physical eraseblock number to read from
990  * This function reads the volume identifier header from physical eraseblock
1070  * @pnum: the physical eraseblock number to write to
1074  * physical eraseblock @pnum. This function automatically fills the
1079  * case of failure. If %-EIO is returned, the physical eraseblock probably went
1115  * self_check_not_bad - ensure that a physical eraseblock is not bad.
1117  * @pnum: physical eraseblock number to check
1119  * This function returns zero if the physical eraseblock is good, %-EINVAL if
1141  * @pnum: physical eraseblock number the erase counter header belongs to
1180  * @pnum: the physical eraseblock number to check
1224  * @pnum: physical eraseblock number the volume identifier header belongs to
1265  * @pnum: the physical eraseblock number to check
1313  * @pnum: physical eraseblock number the data were written to
1314  * @offset: offset within the physical eraseblock the data were written to
1379  * @pnum: the physical eraseblock number to check
1380  * @offset: the starting offset within the physical eraseblock to check
1384  * @offset of the physical eraseblock @pnum, and a negative error code if not