From: merez@codeaurora.org
To: Chris Ball <cjb@laptop.org>
Cc: Yaniv Gardi <ygardi@codeaurora.org>,
linux-mmc@vger.kernel.org, merez@codeaurora.org,
linux-arm-msm@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND v7 2/2] mmc: card: Adding support for sanitize in eMMC 4.5
Date: Thu, 19 Jul 2012 04:25:20 -0700 (PDT) [thread overview]
Message-ID: <f5830acb2ddca29357a0125cd8f3d577.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <87629k9rkc.fsf@octavius.laptop.org>
On Wed, July 18, 2012 11:46 pm, Chris Ball wrote:
> Hi Yaniv,
>
> On Thu, Jun 28 2012, Yaniv Gardi wrote:
>> This feature delete the unmap memory region of the eMMC card,
>> by writing to a specific register in the EXT_CSD
>> unmap region is the memory region that were previously deleted
>> (by erase, trim or discard operation)
>>
>> Signed-off-by: Yaniv Gardi <ygardi@codeaurora.org>
>
> Did you reply to Chuanxiao's review comments yet? He said:
>
> "So to implement your scenario, how about only add
> mmc_blk_issue_sanitize_rq() for REQ_SANITIZE but not touch
> mmc_blk_issue_secdiscard_rq()? With your changes in
> mmc_blk_issue_secdiscard_rq(), eMMC4.5 device will be failed to operate
> secure trim/erase for REQ_SECURE request."
>
> at: http://thread.gmane.org/gmane.linux.kernel.mmc/14822/focus=14880
>
> Thanks,
>
> - Chris.
> --
> Chris Ball <cjb@laptop.org> <http://printf.net/>
> One Laptop Per Child
>
Secure trim and secure erase were removed from eMMC4.5. Please refer to
annex B at B.6 section in eMMC4.5 spec.
Therefore, failure upon trying to do secure trim/erase is the expected
behavior for eMMC4.5 devices.
Thanks,
Maya
--
Sent by consultant of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2012-07-19 11:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 8:32 [PATCH RESEND v7 0/2] *** adding and exposing SANITIZE capability to the user space via a unique IOCTL *** Yaniv Gardi
2012-06-28 8:32 ` [PATCH RESEND v7 1/2] block: ioctl support for sanitize in eMMC 4.5 Yaniv Gardi
2012-06-28 8:41 ` merez
2012-07-17 10:48 ` Yaniv Gardi
2012-07-09 8:37 ` Girish K S
2012-07-09 9:03 ` Girish K S
2012-07-09 10:02 ` Girish K S
2012-06-28 8:32 ` [PATCH RESEND v7 2/2] mmc: card: Adding " Yaniv Gardi
2012-06-28 8:43 ` merez
2012-07-17 10:51 ` Yaniv Gardi
2012-07-19 6:46 ` Chris Ball
2012-07-19 11:25 ` merez [this message]
2012-07-24 6:40 ` Yaniv Gardi
2012-07-24 6:56 ` Chris Ball
2012-07-25 9:39 ` Yaniv Gardi
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=f5830acb2ddca29357a0125cd8f3d577.squirrel@www.codeaurora.org \
--to=merez@codeaurora.org \
--cc=cjb@laptop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ygardi@codeaurora.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;
as well as URLs for NNTP newsgroup(s).