From: Prabhakar Kushwaha <prabhakar@freescale.com>
To: Prabhakar Kushwaha <prabhakar@freescale.com>,
<linux-mtd@lists.infradead.org>
Cc: scottwood@freescale.com, dedekind1@gmail.com
Subject: Re: [PATCH] driver/mtd/ifc: Read Status while programming NAND flash
Date: Mon, 21 Oct 2013 09:04:12 +0530 [thread overview]
Message-ID: <5264A0B4.1050300@freescale.com> (raw)
In-Reply-To: <1380780401-6640-1-git-send-email-prabhakar@freescale.com>
Hi Artem,
This patch is present in upstream review list from a long time.
There are no review comments.
So, I request you to pick this patch for linux-mtd.git repository.
Regards,
Prabhakar
On 10/03/2013 11:36 AM, Prabhakar Kushwaha wrote:
> as per controller description,
> "While programming a NAND flash, status read should never skipped.
> Because it may happen that a new command is issued to the NAND Flash,
> even when the device has not yet finished processing the previous request.
> This may result in unpredictable behaviour."
>
> IFC controller never polls for R/B signal after command send. It just return
> control to software. This behaviour may not occur with NAND flash access.
> because new commands are sent after polling R/B signal. But it may happen
> in scenario where GPCM-ASIC and NAND flash device are working simultaneously.
>
> Update the controller driver to take care of this requirement
>
> Signed-off-by: Prabhakar Kushwaha <prabhakar@freescale.com>
> ---
> drivers/mtd/nand/fsl_ifc_nand.c | 34 ++++++++++++++++++++++++----------
> 1 file changed, 24 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/mtd/nand/fsl_ifc_nand.c b/drivers/mtd/nand/fsl_ifc_nand.c
> index a14885b..eb150f1 100644
> --- a/drivers/mtd/nand/fsl_ifc_nand.c
> +++ b/drivers/mtd/nand/fsl_ifc_nand.c
> @@ -504,20 +504,29 @@ static void fsl_ifc_cmdfunc(struct mtd_info *mtd, unsigned int command,
> if (mtd->writesize > 512) {
> nand_fcr0 =
> (NAND_CMD_SEQIN << IFC_NAND_FCR0_CMD0_SHIFT) |
> - (NAND_CMD_PAGEPROG << IFC_NAND_FCR0_CMD1_SHIFT);
> + (NAND_CMD_STATUS << IFC_NAND_FCR0_CMD1_SHIFT) |
> + (NAND_CMD_PAGEPROG << IFC_NAND_FCR0_CMD2_SHIFT);
>
> iowrite32be(
> - (IFC_FIR_OP_CW0 << IFC_NAND_FIR0_OP0_SHIFT) |
> - (IFC_FIR_OP_CA0 << IFC_NAND_FIR0_OP1_SHIFT) |
> - (IFC_FIR_OP_RA0 << IFC_NAND_FIR0_OP2_SHIFT) |
> - (IFC_FIR_OP_WBCD << IFC_NAND_FIR0_OP3_SHIFT) |
> - (IFC_FIR_OP_CW1 << IFC_NAND_FIR0_OP4_SHIFT),
> - &ifc->ifc_nand.nand_fir0);
> + (IFC_FIR_OP_CW0 << IFC_NAND_FIR0_OP0_SHIFT) |
> + (IFC_FIR_OP_CA0 << IFC_NAND_FIR0_OP1_SHIFT) |
> + (IFC_FIR_OP_RA0 << IFC_NAND_FIR0_OP2_SHIFT) |
> + (IFC_FIR_OP_WBCD << IFC_NAND_FIR0_OP3_SHIFT) |
> + (IFC_FIR_OP_CMD2 << IFC_NAND_FIR0_OP4_SHIFT),
> + &ifc->ifc_nand.nand_fir0);
> + iowrite32be(
> + (IFC_FIR_OP_CW1 << IFC_NAND_FIR1_OP5_SHIFT) |
> + (IFC_FIR_OP_RDSTAT <<
> + IFC_NAND_FIR1_OP6_SHIFT) |
> + (IFC_FIR_OP_NOP << IFC_NAND_FIR1_OP7_SHIFT),
> + &ifc->ifc_nand.nand_fir1);
> } else {
> nand_fcr0 = ((NAND_CMD_PAGEPROG <<
> IFC_NAND_FCR0_CMD1_SHIFT) |
> (NAND_CMD_SEQIN <<
> - IFC_NAND_FCR0_CMD2_SHIFT));
> + IFC_NAND_FCR0_CMD2_SHIFT) |
> + (NAND_CMD_STATUS <<
> + IFC_NAND_FCR0_CMD3_SHIFT));
>
> iowrite32be(
> (IFC_FIR_OP_CW0 << IFC_NAND_FIR0_OP0_SHIFT) |
> @@ -526,8 +535,13 @@ static void fsl_ifc_cmdfunc(struct mtd_info *mtd, unsigned int command,
> (IFC_FIR_OP_RA0 << IFC_NAND_FIR0_OP3_SHIFT) |
> (IFC_FIR_OP_WBCD << IFC_NAND_FIR0_OP4_SHIFT),
> &ifc->ifc_nand.nand_fir0);
> - iowrite32be(IFC_FIR_OP_CW1 << IFC_NAND_FIR1_OP5_SHIFT,
> - &ifc->ifc_nand.nand_fir1);
> + iowrite32be(
> + (IFC_FIR_OP_CMD1 << IFC_NAND_FIR1_OP5_SHIFT) |
> + (IFC_FIR_OP_CW3 << IFC_NAND_FIR1_OP6_SHIFT) |
> + (IFC_FIR_OP_RDSTAT <<
> + IFC_NAND_FIR1_OP7_SHIFT) |
> + (IFC_FIR_OP_NOP << IFC_NAND_FIR1_OP8_SHIFT),
> + &ifc->ifc_nand.nand_fir1);
>
> if (column >= mtd->writesize)
> nand_fcr0 |=
next prev parent reply other threads:[~2013-10-21 3:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 6:06 [PATCH] driver/mtd/ifc: Read Status while programming NAND flash Prabhakar Kushwaha
2013-10-21 3:34 ` Prabhakar Kushwaha [this message]
2013-10-23 16:44 ` Brian Norris
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=5264A0B4.1050300@freescale.com \
--to=prabhakar@freescale.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).