From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Kamal Dasu <kdasu.kdev@gmail.com>
Cc: linux-mtd@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
computersforpeace@gmail.com, richard@nod.at, dwmw2@infradead.org,
marek.vasut@gmail.com, cyrille.pitchen@wedev4u.fr,
stable@vger.kernel.org
Subject: Re: [PATCH v2] mtd: nand: brcmnand: Disable prefetch by default
Date: Mon, 8 Jan 2018 21:15:40 +0100 [thread overview]
Message-ID: <20180108211540.131f938a@bbrezillon> (raw)
In-Reply-To: <1515441973-30753-1-git-send-email-kdasu.kdev@gmail.com>
On Mon, 8 Jan 2018 15:06:13 -0500
Kamal Dasu <kdasu.kdev@gmail.com> wrote:
> Brcm nand controller prefetch feature needs to be disabled
> by default. Enabling affects performance on random reads as
> well as dma reads.
>
> Signed-off-by: Kamal Dasu <kdasu.kdev@gmail.com>
> Cc: stable@vger.kernel.org
Fixes:????
> ---
> drivers/mtd/nand/brcmnand/brcmnand.c | 13 +++----------
> 1 file changed, 3 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/mtd/nand/brcmnand/brcmnand.c b/drivers/mtd/nand/brcmnand/brcmnand.c
> index dd56a67..2a978d9 100644
> --- a/drivers/mtd/nand/brcmnand/brcmnand.c
> +++ b/drivers/mtd/nand/brcmnand/brcmnand.c
> @@ -2193,16 +2193,9 @@ static int brcmnand_setup_dev(struct brcmnand_host *host)
> if (ctrl->nand_version >= 0x0702)
> tmp |= ACC_CONTROL_RD_ERASED;
> tmp &= ~ACC_CONTROL_FAST_PGM_RDIN;
> - if (ctrl->features & BRCMNAND_HAS_PREFETCH) {
> - /*
> - * FIXME: Flash DMA + prefetch may see spurious erased-page ECC
> - * errors
> - */
> - if (has_flash_dma(ctrl))
> - tmp &= ~ACC_CONTROL_PREFETCH;
> - else
> - tmp |= ACC_CONTROL_PREFETCH;
> - }
> + if (ctrl->features & BRCMNAND_HAS_PREFETCH)
> + tmp &= ~ACC_CONTROL_PREFETCH;
> +
> nand_writereg(ctrl, offs, tmp);
>
> return 0;
prev parent reply other threads:[~2018-01-08 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 20:06 [PATCH v2] mtd: nand: brcmnand: Disable prefetch by default Kamal Dasu
2018-01-08 20:15 ` 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=20180108211540.131f938a@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=kdasu.kdev@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--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