From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Jagdish Gediya <jagdish.gediya@nxp.com>
Cc: linux-mtd@lists.infradead.org,
boris.brezillon@free-electrons.com, stable@vger.kernel.org,
leoyang.li@nxp.com, oss@buserror.net,
computersforpeace@gmail.com
Subject: Re: [PATCH][v3] mtd: rawnand: fsl_ifc: Fix nand waitfunc return value
Date: Fri, 23 Mar 2018 08:51:15 +0100 [thread overview]
Message-ID: <20180323085115.1c9af019@bbrezillon> (raw)
In-Reply-To: <1521586908-7667-1-git-send-email-jagdish.gediya@nxp.com>
On Wed, 21 Mar 2018 04:31:36 +0530
Jagdish Gediya <jagdish.gediya@nxp.com> wrote:
> As per the IFC hardware manual, Most significant 2 bytes in
> nand_fsr register are the outcome of NAND READ STATUS command.
>
> So status value need to be shifted and aligned as per the nand
> framework requirement.
>
> Fixes: 82771882d960 ("NAND Machine support for Integrated Flash Controller")
> Cc: stable@vger.kernel.org # v3.18+
> Signed-off-by: Jagdish Gediya <jagdish.gediya@nxp.com>
> Reviewed-by: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
Applied.
Thanks,
Boris
> ---
> Changes for v2: Incorporated comments from Boris Brezillon
> - Added fixes tag
>
> Changes for v3: Incorporated comments from Boris Brezillon
>
> drivers/mtd/nand/fsl_ifc_nand.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mtd/nand/fsl_ifc_nand.c b/drivers/mtd/nand/fsl_ifc_nand.c
> index 9390cbd..16104ca 100644
> --- a/drivers/mtd/nand/fsl_ifc_nand.c
> +++ b/drivers/mtd/nand/fsl_ifc_nand.c
> @@ -629,6 +629,7 @@ static int fsl_ifc_wait(struct mtd_info *mtd, struct nand_chip *chip)
> struct fsl_ifc_ctrl *ctrl = priv->ctrl;
> struct fsl_ifc_runtime __iomem *ifc = ctrl->rregs;
> u32 nand_fsr;
> + int status;
>
> /* Use READ_STATUS command, but wait for the device to be ready */
> ifc_out32((IFC_FIR_OP_CW0 << IFC_NAND_FIR0_OP0_SHIFT) |
> @@ -643,12 +644,12 @@ static int fsl_ifc_wait(struct mtd_info *mtd, struct nand_chip *chip)
> fsl_ifc_run_command(mtd);
>
> nand_fsr = ifc_in32(&ifc->ifc_nand.nand_fsr);
> -
> + status = nand_fsr >> 24;
> /*
> * The chip always seems to report that it is
> * write-protected, even when it is not.
> */
> - return nand_fsr | NAND_STATUS_WP;
> + return status | NAND_STATUS_WP;
> }
>
> /*
--
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-03-23 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 23:01 [PATCH][v3] mtd: rawnand: fsl_ifc: Fix nand waitfunc return value Jagdish Gediya
2018-03-23 7:51 ` Boris Brezillon [this message]
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=20180323085115.1c9af019@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=jagdish.gediya@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-mtd@lists.infradead.org \
--cc=oss@buserror.net \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).