On 11/05/2019 02:12 PM, Vignesh Raghavendra wrote:
> External E-Mail
>
>
> Hi,
>
> On 02/11/19 4:53 PM, Tudor.Ambarus@xxxxxxxxxxxxx wrote:
>> From: Tudor Ambarus <tudor.ambarus@xxxxxxxxxxxxx>
>>
>> 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 for just three cases:
>> - when the JEDEC ID is not recognized
>> - when the resume() call fails
>> - when the spi_nor_check() fails.
>>
>> Suggested-by: Boris Brezillon <boris.brezillon@xxxxxxxxxxxxx>
>> Signed-off-by: Tudor Ambarus <tudor.ambarus@xxxxxxxxxxxxx>
>> ---
>> drivers/mtd/spi-nor/spi-nor.c | 52 +++++++++++++++++++++----------------------
>> 1 file changed, 26 insertions(+), 26 deletions(-)
>>
> [...]
>>
>> @@ -679,9 +679,9 @@ static int spi_nor_sr_ready(struct spi_nor *nor)
>> if (nor->flags & SNOR_F_USE_CLSR &&
>> nor->bouncebuf[0] & (SR_E_ERR | SR_P_ERR)) {
>> if (nor->bouncebuf[0] & SR_E_ERR)
>> - dev_err(nor->dev, "Erase Error occurred\n");
>> + dev_dbg(nor->dev, "Erase Error occurred\n");
>> else
>> - dev_err(nor->dev, "Programming Error occurred\n");
>> + dev_dbg(nor->dev, "Programming Error occurred\n");
>>
>> spi_nor_clear_sr(nor);
>> return -EIO;
>> @@ -714,12 +714,12 @@ static int spi_nor_fsr_ready(struct spi_nor *nor)
>>
>> if (nor->bouncebuf[0] & (FSR_E_ERR | FSR_P_ERR)) {
>> if (nor->bouncebuf[0] & FSR_E_ERR)
>> - dev_err(nor->dev, "Erase operation failed.\n");
>> + dev_dbg(nor->dev, "Erase operation failed.\n");
>> else
>> - dev_err(nor->dev, "Program operation failed.\n");
>> + dev_dbg(nor->dev, "Program operation failed.\n");
>>
>> if (nor->bouncebuf[0] & FSR_PT_ERR)
>> - dev_err(nor->dev,
>> + dev_dbg(nor->dev,
>> "Attempted to modify a protected sector.\n");
>>
>
> Since, we are specifically parsing FSR bits to know the reason for
> failure, I think we should use dev_err()s here.
> I specifically like the last one which informs the user that
> program/erase operation failed as sector was write protected.
>
Yep, will use dev_err to report erase/program errors in both spi_nor_sr_ready()
and spi_nor_fsr_ready(), together with the attempt of modifying a protected sector.
Thanks!
> Rest looks fine to me:
>
> Reviewed-by: Vignesh Raghavendra <vigneshr@xxxxxx>
>
> Regards
> Vignesh
>
>> spi_nor_clear_fsr(nor);
>> @@ -770,7 +770,7 @@ static int spi_nor_wait_till_ready_with_timeout(struct spi_nor *nor,
>> cond_resched();
>> }
>>
>> - dev_err(nor->dev, "flash operation timed out\n");
>> + dev_dbg(nor->dev, "flash operation timed out\n");
>>
>> return -ETIMEDOUT;
>> }
>> @@ -807,7 +807,7 @@ static int spi_nor_write_sr_cr(struct spi_nor *nor, const u8 *sr_cr)
>> }
>>
>> if (ret) {
>> - dev_err(nor->dev,
>> + dev_dbg(nor->dev,
>> "error while writing configuration register\n");
>> return -EINVAL;
>> }
>> @@ -1771,7 +1771,7 @@ static int macronix_quad_enable(struct spi_nor *nor)
>> return ret;
>>
>> if (!(nor->bouncebuf[0] & SR_QUAD_EN_MX)) {
>> - dev_err(nor->dev, "Macronix Quad bit not set\n");
>> + dev_dbg(nor->dev, "Macronix Quad bit not set\n");
>> return -EINVAL;
>> }
>>
>> @@ -1819,7 +1819,7 @@ static int spansion_quad_enable(struct spi_nor *nor)
>> return ret;
>>
>> if (!(nor->bouncebuf[0] & CR_QUAD_EN_SPAN)) {
>> - dev_err(nor->dev, "Spansion Quad bit not set\n");
>> + dev_dbg(nor->dev, "Spansion Quad bit not set\n");
>> return -EINVAL;
>> }
>>
>> @@ -1897,7 +1897,7 @@ static int spansion_read_cr_quad_enable(struct spi_nor *nor)
>> return ret;
>>
>> if (!(sr_cr[1] & CR_QUAD_EN_SPAN)) {
>> - dev_err(nor->dev, "Spansion Quad bit not set\n");
>> + dev_dbg(nor->dev, "Spansion Quad bit not set\n");
>> return -EINVAL;
>> }
>>
>> @@ -1935,7 +1935,7 @@ static int sr2_bit7_quad_enable(struct spi_nor *nor)
>>
>> ret = spi_nor_write_sr2(nor, sr2);
>> if (ret) {
>> - dev_err(nor->dev, "error while writing status register 2\n");
>> + dev_dbg(nor->dev, "error while writing status register 2\n");
>> return ret;
>> }
>>
>> @@ -1949,7 +1949,7 @@ static int sr2_bit7_quad_enable(struct spi_nor *nor)
>> return ret;
>>
>> if (!(*sr2 & SR2_QUAD_EN_BIT7)) {
>> - dev_err(nor->dev, "SR2 Quad bit not set\n");
>> + dev_dbg(nor->dev, "SR2 Quad bit not set\n");
>> return -EINVAL;
>> }
>>
>> @@ -1978,7 +1978,7 @@ static int spi_nor_clear_sr_bp(struct spi_nor *nor)
>>
>> ret = spi_nor_write_sr(nor, nor->bouncebuf[0] & ~mask);
>> if (ret) {
>> - dev_err(nor->dev, "write to status register failed\n");
>> + dev_dbg(nor->dev, "write to status register failed\n");
>> return ret;
>> }
>>
>> @@ -2525,7 +2525,7 @@ static const struct flash_info *spi_nor_read_id(struct spi_nor *nor)
>> SPI_NOR_MAX_ID_LEN);
>> }
>> if (tmp) {
>> - dev_err(nor->dev, "error %d reading JEDEC ID\n", tmp);
>> + dev_dbg(nor->dev, "error %d reading JEDEC ID\n", tmp);
>> return ERR_PTR(tmp);
>> }
>>
>> @@ -2740,7 +2740,7 @@ static int s3an_nor_setup(struct spi_nor *nor,
>>
>> ret = spi_nor_xread_sr(nor, nor->bouncebuf);
>> if (ret) {
>> - dev_err(nor->dev, "error %d reading XRDSR\n", ret);
>> + dev_dbg(nor->dev, "error %d reading XRDSR\n", ret);
>> return ret;
>> }
>>
>> @@ -4102,7 +4102,7 @@ static int spi_nor_parse_sfdp(struct spi_nor *nor,
>> err = spi_nor_read_sfdp(nor, sizeof(header),
>> psize, param_headers);
>> if (err < 0) {
>> - dev_err(dev, "failed to read SFDP parameter headers\n");
>> + dev_dbg(dev, "failed to read SFDP parameter headers\n");
>> goto exit;
>> }
>> }
>> @@ -4349,7 +4349,7 @@ static int spi_nor_default_setup(struct spi_nor *nor,
>> /* Select the (Fast) Read command. */
>> err = spi_nor_select_read(nor, shared_mask);
>> if (err) {
>> - dev_err(nor->dev,
>> + dev_dbg(nor->dev,
>> "can't select read settings supported by both the SPI controller and memory.\n");
>> return err;
>> }
>> @@ -4357,7 +4357,7 @@ static int spi_nor_default_setup(struct spi_nor *nor,
>> /* Select the Page Program command. */
>> err = spi_nor_select_pp(nor, shared_mask);
>> if (err) {
>> - dev_err(nor->dev,
>> + dev_dbg(nor->dev,
>> "can't select write settings supported by both the SPI controller and memory.\n");
>> return err;
>> }
>> @@ -4365,7 +4365,7 @@ static int spi_nor_default_setup(struct spi_nor *nor,
>> /* Select the Sector Erase command. */
>> err = spi_nor_select_erase(nor);
>> if (err) {
>> - dev_err(nor->dev,
>> + dev_dbg(nor->dev,
>> "can't select erase settings supported by both the SPI controller and memory.\n");
>> return err;
>> }
>> @@ -4686,7 +4686,7 @@ static int spi_nor_init(struct spi_nor *nor)
>>
>> err = nor->clear_sr_bp(nor);
>> if (err) {
>> - dev_err(nor->dev,
>> + dev_dbg(nor->dev,
>> "fail to clear block protection bits\n");
>> return err;
>> }
>> @@ -4694,7 +4694,7 @@ static int spi_nor_init(struct spi_nor *nor)
>>
>> err = spi_nor_quad_enable(nor);
>> if (err) {
>> - dev_err(nor->dev, "quad mode not supported\n");
>> + dev_dbg(nor->dev, "quad mode not supported\n");
>> return err;
>> }
>>
>> @@ -4762,7 +4762,7 @@ static int spi_nor_set_addr_width(struct spi_nor *nor)
>> }
>>
>> if (nor->addr_width > SPI_NOR_MAX_ADDR_WIDTH) {
>> - dev_err(nor->dev, "address width is too large: %u\n",
>> + dev_dbg(nor->dev, "address width is too large: %u\n",
>> nor->addr_width);
>> return -EINVAL;
>> }
>>
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Re: [PATCH v4 01/20] mtd: spi-nor: Use dev_dbg insted of dev_err for low level info
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH v4 01/20] mtd: spi-nor: Use dev_dbg insted of dev_err for low level info
- From: <Tudor.Ambarus@xxxxxxxxxxxxx>
- Date: Wed, 6 Nov 2019 07:07:21 +0000
- Accept-language: en-US
- Cc: richard@xxxxxx, linux-mtd@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, miquel.raynal@xxxxxxxxxxx
- In-reply-to: <bc98d845-1994-69a8-a655-81ba1bb9253f@ti.com>
- References: <20191102112316.20715-1-tudor.ambarus@microchip.com> <20191102112316.20715-2-tudor.ambarus@microchip.com> <bc98d845-1994-69a8-a655-81ba1bb9253f@ti.com>
- References:
- [PATCH v4 00/20] mtd: spi-nor: Quad Enable and (un)lock methods
- From: Tudor.Ambarus
- [PATCH v4 01/20] mtd: spi-nor: Use dev_dbg insted of dev_err for low level info
- From: Tudor.Ambarus
- Re: [PATCH v4 01/20] mtd: spi-nor: Use dev_dbg insted of dev_err for low level info
- From: Vignesh Raghavendra
- [PATCH v4 00/20] mtd: spi-nor: Quad Enable and (un)lock methods
- Prev by Date: Re: [PATCH v4 18/20] mtd: spi-nor: Rename macronix_quad_enable to spi_nor_sr1_bit6_quad_enable
- Next by Date: Re: [PATCH v4 12/20] mtd: spi-nor: Print debug message when the read back test fails
- Previous by thread: Re: [PATCH v4 01/20] mtd: spi-nor: Use dev_dbg insted of dev_err for low level info
- Next by thread: [PATCH v4 02/20] mtd: spi-nor: Print debug info inside Reg Ops methods
- Index(es):
 |