From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: denali: fix write_oob_data() function
Date: Fri, 16 May 2014 15:36:54 +0900 [thread overview]
Message-ID: <20140516153654.E1A1.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <20140510021226.GI28907@ld-irv-0074>
Hi Brian,
On Fri, 9 May 2014 19:12:26 -0700
Brian Norris <computersforpeace@gmail.com> wrote:
> On Thu, Apr 17, 2014 at 07:22:54PM +0900, Masahiro Yamada wrote:
> > Since write_oob_data is calling denali_send_pipeline_cmd()
> > with access_type=SPARE_ACCESS, this might has no impact.
>
> "Might"? Are you sure? Do you have any test results? I don't want to
> change this code based on a whim...
Sorry, I could not make myself understood because of my bad English..
What I wanted to say:
I know this patch has no impact,
but calling denali_send_pipeline_cmd() with transfer_spare=false looks weird.
So I want to fix it just in case.
I referred Denali(Cadence) NAND Flash Memory Controller User's Guide
and actually I am sure this patch has no impact.
The 3rd argument (transfer_spare) of denali_send_pipeline_cmd()
is don't care if its 4th argument to is access_type=SPARE_ACCESS.
read_oob_data() function calls
denali_send_pipeline_cmd(denali, false, true, SPARE_ACCESS, DENALI_READ)
So, write_oob_data() function should call
denali_send_pipeline_cmd(denali, false, true, SPARE_ACCESS, DENALI_WRITE)
for consistency.
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2014-05-16 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 10:22 [PATCH] mtd: denali: fix write_oob_data() function Masahiro Yamada
2014-05-10 2:12 ` Brian Norris
2014-05-16 6:36 ` Masahiro Yamada [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=20140516153654.E1A1.AA925319@jp.panasonic.com \
--to=yamada.m@jp.panasonic.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.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