From: Seungwon Jeon <tgih.jun@samsung.com>
To: "'Andrei E. Warkentin'" <andrey.warkentin@gmail.com>
Cc: 'Adrian Hunter' <adrian.hunter@intel.com>,
linux-mmc@vger.kernel.org, cjb@laptop.org,
linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
dh.han@samsung.com
Subject: RE: [PATCH] mmc: core: Add cache control for eMMC4.5 device
Date: Thu, 06 Oct 2011 17:22:26 +0900 [thread overview]
Message-ID: <000f01cc8401$14d6ffd0$3e84ff70$%jun@samsung.com> (raw)
In-Reply-To: <CANz0V+4Ue_TNXsJEEpGwTyHFUJjz+f41aF+VfWdKqc=BqW1-0w@mail.gmail.com>
Andrei E. Warkentin wrote:
> Hi Seungwon,
>
> 2011/10/6 Seungwon Jeon <tgih.jun@samsung.com>:
> > Adrian Hunter wrote:
> >> On 08/09/11 10:29, Seungwon Jeon wrote:
> >> > This patch adds cache feature of eMMC4.5 Spec.
> >> > If device supports cache capability, host can utilize some specific
> >> > operations.
> >> >
> >> > Signed-off-by: Seungwon Jeon<tgih.jun@samsung.com>
> >> > ---
>
> I don't think eMMC 4.5 is public yet, so could you elaborate on the
> volatile cache? I am
> in particular interested in how the volatile cache affects reliable
> writes (I would assume it doesn't
> affect them at all).
Right, no effect.
Data of reliable write will be written the non-volatile memory not cache forcedly.
>
> A
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-10-06 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 7:29 [PATCH] mmc: core: Add cache control for eMMC4.5 device Seungwon Jeon
2011-10-05 11:47 ` Adrian Hunter
2011-10-06 4:38 ` Seungwon Jeon
2011-10-06 5:21 ` Andrei E. Warkentin
2011-10-06 8:22 ` Seungwon Jeon [this message]
2011-10-06 19:38 ` Andrei E. Warkentin
2011-10-06 7:06 ` Adrian Hunter
2011-10-06 8:48 ` Seungwon Jeon
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='000f01cc8401$14d6ffd0$3e84ff70$%jun@samsung.com' \
--to=tgih.jun@samsung.com \
--cc=adrian.hunter@intel.com \
--cc=andrey.warkentin@gmail.com \
--cc=cjb@laptop.org \
--cc=dh.han@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@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