All of lore.kernel.org
 help / color / mirror / Atom feed
From: Y.b. Lu <yangbo.lu@nxp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] blk: Remove various places that do flush cache after read
Date: Thu, 24 Aug 2017 03:54:42 +0000	[thread overview]
Message-ID: <DB6PR0401MB25366DBD4C7122438013440CF89A0@DB6PR0401MB2536.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAEUhbmVFDTao=4qYghGWdTihFxieNtPO4PUnQcXT_7WrQCoHHQ@mail.gmail.com>



> -----Original Message-----
> From: Bin Meng [mailto:bmeng.cn at gmail.com]
> Sent: Wednesday, August 23, 2017 1:29 PM
> To: Y.b. Lu
> Cc: Qiang Zhao; York Sun; Grygorii Strashko; Michal Simek; Angelo
> Dureghello; Kever Yang; Jaehoon Chung; Albert Aribaud; Marcel Ziswiler;
> Markus Niebel; Z.q. Hou; Sumit Garg; Joe Hershberger; Stefan Roese;
> Wenbin Song; Simon Glass; Max Krummenacher; Masahiro Yamada; Tomas Melin;
> Q.y. Gong; Tom Rini; U-Boot Mailing List
> Subject: Re: [PATCH] blk: Remove various places that do flush cache after
> read
> 
> Hi Yangbo,
> 
> On Wed, Aug 23, 2017 at 11:29 AM, Y.b. Lu <yangbo.lu@nxp.com> wrote:
> > cmd/mmc.c
> >
> > Maybe SD controller on some vendor platforms doesn't support SNOOP.
> > flush_cache() is required to sync between DDR and cache.
> > Should be careful to remove this.
> >
> 
> Please do not top-posting.
> 
> What you mentioned if snoop is not supported, flush_cache() is required,
> is true, however that's not the issue I am trying to fix here. The
> flush_cache() here after a DMA read will cause issues because stale data
> in the cache will overwrite the correct data in the RAM that is DMAed by
> hardware (in this case, MMC controller).
> 

[Lu Yangbo-B47093] Sorry for my misunderstanding. It looks ok to me now.
flush_cache is indeed redundant after DMA reading.


> Regards,
> Bin

  reply	other threads:[~2017-08-24  3:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22  3:46 [U-Boot] [PATCH] blk: Remove various places that do flush cache after read Bin Meng
2017-08-22  6:19 ` Stefan Roese
2017-08-22  6:31   ` Bin Meng
2017-08-22 16:49 ` York Sun
2017-08-22 22:53   ` Bin Meng
2017-08-23 15:01     ` York Sun
2017-08-23  3:14   ` Qiang Zhao
2017-08-23  3:29     ` Y.b. Lu
2017-08-23  5:28       ` Bin Meng
2017-08-24  3:54         ` Y.b. Lu [this message]
2017-08-23 16:06 ` York Sun
2017-08-24 16:45 ` Joe Hershberger
2017-08-27 20:09 ` Simon Glass

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=DB6PR0401MB25366DBD4C7122438013440CF89A0@DB6PR0401MB2536.eurprd04.prod.outlook.com \
    --to=yangbo.lu@nxp.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.