diff options
| author | Tudor Ambarus <tudor.ambarus@microchip.com> | 2019-11-02 11:23:25 +0000 |
|---|---|---|
| committer | Tudor Ambarus <tudor.ambarus@microchip.com> | 2019-11-07 08:16:07 +0200 |
| commit | f633ebe4879b4e9876a8835d90435d9250c65bf2 (patch) | |
| tree | c21ea85c8144c50b6eed00d952bee128956e2c47 /tools/perf/scripts/python | |
| parent | 3d63ee5deb466fd66ed6ffb164a87ce36425cf36 (diff) | |
mtd: spi-nor: Use dev_dbg insted of dev_err for low level info
What most users care about is "my dev is not working properly".
All low level information should be discovered when activating
the debug traces.
Keep error messages just for the following cases:
- when the SR/FSR report program or erase fails, or attempts of
modifying a protected sector,
- when the JEDEC ID is not recognized,
- when the resume() call fails,
- when the spi_nor_check() fails.
Suggested-by: Boris Brezillon <boris.brezillon@collabora.com>
Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
Reviewed-by: Vignesh Raghavendra <vigneshr@ti.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions