Lines Matching defs:data
65 * the data and want to write this VID header out. As we can only write in
92 * ubi_io_read - read data from a physical eraseblock.
94 * @buf: buffer where to store the read data
99 * This function reads data from offset @offset of physical eraseblock @pnum
100 * and stores the read data in the @buf buffer. The following return codes are
103 * o %0 if all the requested data were successfully read;
104 * o %UBI_IO_BITFLIPS if all the requested data were successfully read, but
107 * o %-EBADMSG if the MTD subsystem reported about data integrity problems, for
109 * that the data is corrupted;
133 * 1. The buffer contains data from previous operation, e.g., read from
134 * another PEB previously. The data looks like expected, e.g., if we
139 * -EUCLEAN, but it does not actually put any data to the buffer.
142 * contains valid data while in fact it is just old data. This is
144 * treats data as correct even in case of ECC errors if the CRC is
186 * all the requested data. But some buggy drivers might do
206 * ubi_io_write - write data to a physical eraseblock.
208 * @buf: buffer with the data to write
213 * This function writes @len bytes of data from buffer @buf to offset @offset
214 * of physical eraseblock @pnum. If all the data were successfully written,
252 * We write to the data area of the physical eraseblock. Make
418 * If a bit-flip or data integrity error was detected, the test
439 * This means that in case of a power cut we may end up with intact data at the
441 * EC and VID headers are OK, but a large chunk of data at the end of PEB is
454 uint32_t data = 0;
478 err = mtd_write(ubi->mtd, addr, 4, &written, (void *)&data);
490 err = mtd_write(ubi->mtd, addr, 4, &written, (void *)&data);
646 ubi_err(ubi, "bad data offset %d, expected %d",
683 * a data integrity error (uncorrectable ECC error in case of NAND);
702 * We read all the data, but either a correctable bit-flip
703 * occurred, or MTD reported a data integrity error
705 * harmless, the later may mean that the read data is
829 * This function checks that data stored in the volume identifier header
892 * contain zero bytes of data, but no VID headers can contain
921 ubi_err(ubi, "non-zero data CRC");
953 * @vidb: the volume identifier buffer to store data in
1280 * @buf: buffer with data which were written
1281 * @pnum: physical eraseblock number the data were written to
1282 * @offset: offset within the physical eraseblock the data were written to
1285 * This functions reads data which were recently written and compares it with
1286 * the original data buffer - the data have to match. Returns zero if the data
1320 ubi_msg(ubi, "data differ at position %d", i);