summaryrefslogtreecommitdiffstats
path: root/drivers/mtd/onenand
diff options
context:
space:
mode:
authorBrian Norris <computersforpeace@gmail.com>2013-08-13 10:51:55 -0700
committerBrian Norris <computersforpeace@gmail.com>2013-10-27 16:27:03 -0700
commitc7f23a70635895b5125aeb5593aaf8cb44d3a088 (patch)
tree00577a372bd5928d27c8141d99a50f198afa215b /drivers/mtd/onenand
parent535ab9033433c00116e446beaac96503c7282fd1 (diff)
downloadop-kernel-dev-c7f23a70635895b5125aeb5593aaf8cb44d3a088.zip
op-kernel-dev-c7f23a70635895b5125aeb5593aaf8cb44d3a088.tar.gz
mtd: nand: cleanup ONFI printed errors, warnings
The ONFI detection routine is too verbose in some cases and not verbose enough in others. This patch refactors it to print only when there are significant warnings/errors. Probing in 16-bit mode: It is unnecessary to print until after the READID (address 20h) command. READID *has* to work properly in whatever bus width configuration we are in, or else no identification mode works. So we can silence some useless warnings on systems which come up in 16-bit mode and do not even respond with an O-N-F-I string. Valid parameter page: Nobody needs to see this. Do we inform the user every time other hardware responds properly? Instead, add an error message if *no* uncorrupted parameter pages are found. ONFI ECC: Most drivers don't yet use the reported minimum ECC values, so it shouldn't yet be a fatal condition if the extended parameter page is incorrect. But we should at least give a warning for the corner cases that we don't expect. ONFI flash detected: Nobody needs to see this. This is the expected case, that we detect ONFI properly, or else it wasn't ONFI-compliant and is detected by some other routine. Signed-off-by: Brian Norris <computersforpeace@gmail.com> Cc: Huang Shijie <b32955@freescale.com> Cc: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Diffstat (limited to 'drivers/mtd/onenand')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud