From: Kumar Gala <galak@kernel.crashing.org>
To: Prabhakar Kushwaha <prabhakar@freescale.com>
Cc: scottwood@freescale.com, linuxppc-dev@lists.ozlabs.org,
linux-mtd@lists.infradead.org, dedekind1@gmail.com
Subject: Re: [PATCH] driver/mtd:IFC NAND:Initialise internal SRAM before any write
Date: Thu, 13 Sep 2012 07:53:34 -0500 [thread overview]
Message-ID: <68738277-B1F2-4455-B8FD-67F2DD9E1310@kernel.crashing.org> (raw)
In-Reply-To: <1347526489-20186-1-git-send-email-prabhakar@freescale.com>
On Sep 13, 2012, at 3:54 AM, Prabhakar Kushwaha wrote:
> IFC-1.1.0 uses 28nm techenology for SRAM. This tech has known limitaion for
> SRAM i.e. "byte select" is not supported. Hence Read Modify Write is
> implemented in IFC for any "system side write" into sram buffer. Reading an
> uninitialized memory results in ECC Error from sram wrapper.
>
> Hence we must initialize/prefill SRAM buffer by any data before writing
> anything in SRAM from system side. To initialize SRAM user can use "READID"
> NAND command with read bytes equal to SRAM size. It will be a one time
> activity post boot.
>
> Signed-off-by: Prabhakar Kushwaha <prabhakar@freescale.com>
> ---
> Based upon git://git.infradead.org/linux-mtd.git branch master
> The compilation of this patch depends upon following patch.
> http://patchwork.ozlabs.org/patch/177893/
> This patch is currently applied on git://git.kernel.org/pub/scm/linux/kernel/git/galak/powerpc.git
> branch next and status is "Awaiting Upstream"
>
>
> drivers/mtd/nand/fsl_ifc_nand.c | 56 ++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 55 insertions(+), 1 deletion(-)
If MTD maintainers ack, I'm happy to pull this in via PPC tree.
- k
next prev parent reply other threads:[~2012-09-13 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 8:54 [PATCH] driver/mtd:IFC NAND:Initialise internal SRAM before any write Prabhakar Kushwaha
2012-09-13 12:53 ` Kumar Gala [this message]
2012-09-26 4:45 ` Prabhakar Kushwaha
2012-09-26 9:16 ` Artem Bityutskiy
2012-09-27 12:33 ` Kumar Gala
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=68738277-B1F2-4455-B8FD-67F2DD9E1310@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=prabhakar@freescale.com \
--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