From: Roger Quadros <rogerq@ti.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Brian Norris <computersforpeace@gmail.com>
Cc: "Tony Lindgren" <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org,
"Guido Martínez" <guido@vanguardiasur.com.ar>
Subject: Re: [PATCH v2 3/3] nand: omap2: Replace pr_err with dev_err
Date: Mon, 8 Sep 2014 14:57:48 +0300 [thread overview]
Message-ID: <540D99BC.5040209@ti.com> (raw)
In-Reply-To: <1410175636-4036-4-git-send-email-ezequiel@vanguardiasur.com.ar>
Hi Ezequiel,
On 09/08/2014 02:27 PM, Ezequiel Garcia wrote:
> Usage of pr_err is frowned upon, so replace it with dev_err.
> Aditionally, the message on nand_bch_init() error is redundant,
> since proper error is showed if the function fails.
>
> Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> ---
> drivers/mtd/nand/omap2.c | 26 ++++++++++++++------------
> 1 file changed, 14 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
> index f97a4ff..eb5e898 100644
> --- a/drivers/mtd/nand/omap2.c
> +++ b/drivers/mtd/nand/omap2.c
> @@ -1375,7 +1375,7 @@ static int omap_elm_correct_data(struct mtd_info *mtd, u_char *data,
> erased_ecc_vec = bch16_vector;
> break;
> default:
> - pr_err("invalid driver configuration\n");
> + dev_err(&info->pdev->dev, "invalid driver configuration\n");
> return -EINVAL;
> }
>
> @@ -1446,7 +1446,8 @@ static int omap_elm_correct_data(struct mtd_info *mtd, u_char *data,
> err = 0;
> for (i = 0; i < eccsteps; i++) {
> if (err_vec[i].error_uncorrectable) {
> - pr_err("nand: uncorrectable bit-flips found\n");
> + dev_err(&info->pdev->dev,
> + "uncorrectable bit-flips found\n");
> err = -EBADMSG;
> } else if (err_vec[i].error_reported) {
> for (j = 0; j < err_vec[i].error_count; j++) {
> @@ -1483,8 +1484,9 @@ static int omap_elm_correct_data(struct mtd_info *mtd, u_char *data,
> 1 << bit_pos;
> }
> } else {
> - pr_err("invalid bit-flip @ %d:%d\n",
> - byte_pos, bit_pos);
> + dev_err(&info->pdev->dev,
> + "invalid bit-flip @ %d:%d\n",
> + byte_pos, bit_pos);
> err = -EBADMSG;
> }
> }
> @@ -1598,13 +1600,13 @@ static bool is_elm_present(struct omap_nand_info *info,
>
> /* check whether elm-id is passed via DT */
> if (!elm_node) {
> - pr_err("nand: error: ELM DT node not found\n");
> + dev_err(&info->pdev->dev, "ELM devicetree node not found\n");
> return false;
> }
> pdev = of_find_device_by_node(elm_node);
> /* check whether ELM device is registered */
> if (!pdev) {
> - pr_err("nand: error: ELM device not found\n");
> + dev_err(&info->pdev->dev, "ELM device not found\n");
> return false;
> }
> /* ELM module available, now configure it */
> @@ -1734,14 +1736,14 @@ static int omap_nand_probe(struct platform_device *pdev)
> /* scan NAND device connected to chip controller */
> nand_chip->options |= pdata->devsize & NAND_BUSWIDTH_16;
> if (nand_scan_ident(mtd, 1, NULL)) {
> - pr_err("nand device scan failed, may be bus-width mismatch\n");
> + dev_err(&info->pdev->dev, "scan failed, may be bus-width mismatch\n");
> err = -ENXIO;
> goto return_error;
> }
>
> /* check for small page devices */
> if ((mtd->oobsize < 64) && (pdata->ecc_opt != OMAP_ECC_HAM1_CODE_HW)) {
> - pr_err("small page devices are not supported\n");
> + dev_err(&info->pdev->dev, "small page devices are not supported\n");
> err = -EINVAL;
> goto return_error;
> }
> @@ -1959,7 +1961,6 @@ static int omap_nand_probe(struct platform_device *pdev)
> nand_chip->ecc.bytes,
> &ecclayout);
> if (!nand_chip->ecc.priv) {
> - pr_err("nand: error: unable to use s/w BCH library\n");
Where would the error be printed in this case?
I also noticed a similar message in the OMAP_ECC_BCH4_CODE_HW_DETECTION_SW case.
And it seems to be missing a "goto return_error" there.
> err = -EINVAL;
> goto return_error;
> }
> @@ -2026,7 +2027,7 @@ static int omap_nand_probe(struct platform_device *pdev)
> ecclayout->eccpos[ecclayout->eccbytes - 1] + 1;
> break;
> default:
> - pr_err("nand: error: invalid or unsupported ECC scheme\n");
> + dev_err(&info->pdev->dev, "invalid or unsupported ECC scheme\n");
> err = -EINVAL;
> goto return_error;
> }
> @@ -2038,8 +2039,9 @@ static int omap_nand_probe(struct platform_device *pdev)
> ecclayout->oobfree->length = mtd->oobsize - ecclayout->oobfree->offset;
> /* check if NAND device's OOB is enough to store ECC signatures */
> if (mtd->oobsize < (ecclayout->eccbytes + BADBLOCK_MARKER_LENGTH)) {
> - pr_err("not enough OOB bytes required = %d, available=%d\n",
> - ecclayout->eccbytes, mtd->oobsize);
> + dev_err(&info->pdev->dev,
> + "not enough OOB bytes required = %d, available=%d\n",
> + ecclayout->eccbytes, mtd->oobsize);
> err = -EINVAL;
> goto return_error;
> }
>
cheers,
-roger
next prev parent reply other threads:[~2014-09-08 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 11:27 [PATCH v2 0/3] nand: omap2: Two and a half improvements Ezequiel Garcia
2014-09-08 11:27 ` [PATCH v2 1/3] nand: omap2: Add support for flash-based bad block table Ezequiel Garcia
2014-09-09 8:35 ` Roger Quadros
2014-09-09 13:27 ` Ezequiel Garcia
2014-09-09 13:33 ` Roger Quadros
2014-09-08 11:27 ` [PATCH v2 2/3] nand: omap2: Remove horrible ifdefs to fix module probe Ezequiel Garcia
2014-09-08 11:27 ` [PATCH v2 3/3] nand: omap2: Replace pr_err with dev_err Ezequiel Garcia
2014-09-08 11:57 ` Roger Quadros [this message]
2014-09-08 14:35 ` Ezequiel Garcia
2014-09-09 8:33 ` Roger Quadros
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=540D99BC.5040209@ti.com \
--to=rogerq@ti.com \
--cc=computersforpeace@gmail.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=guido@vanguardiasur.com.ar \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox