mtd: nand: gpmi: need to use {read,write}_oob_raw
This patch is simply an added warning in the comments. Ideally, this patch need not be merged, but rather, a developer will write a proper solution that can use the ecc.read_oob_raw and ecc.write_oob_raw interfaces. Signed-off-by: Brian Norris <computersforpeace@gmail.com> Cc: Huang Shijie <b32955@freescale.com> Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
This commit is contained in:
parent
b9bc815c2c
commit
271b874ba1
|
@ -1064,6 +1064,9 @@ exit_auxiliary:
|
||||||
* ECC-based or raw view of the page is implicit in which function it calls
|
* ECC-based or raw view of the page is implicit in which function it calls
|
||||||
* (there is a similar pair of ECC-based/raw functions for writing).
|
* (there is a similar pair of ECC-based/raw functions for writing).
|
||||||
*
|
*
|
||||||
|
* FIXME: The following paragraph is incorrect, now that there exist
|
||||||
|
* ecc.read_oob_raw and ecc.write_oob_raw functions.
|
||||||
|
*
|
||||||
* Since MTD assumes the OOB is not covered by ECC, there is no pair of
|
* Since MTD assumes the OOB is not covered by ECC, there is no pair of
|
||||||
* ECC-based/raw functions for reading or or writing the OOB. The fact that the
|
* ECC-based/raw functions for reading or or writing the OOB. The fact that the
|
||||||
* caller wants an ECC-based or raw view of the page is not propagated down to
|
* caller wants an ECC-based or raw view of the page is not propagated down to
|
||||||
|
|
Loading…
Reference in a new issue