From: Jaehoon Chung <jh80.chung@samsung.com>
To: Prasanna NAVARATNA <prasanna.navaratna@gmail.com>
Cc: linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: enable BKOPS for supported eMMC(4.41)
Date: Thu, 05 Sep 2013 22:03:38 +0900 [thread overview]
Message-ID: <5228812A.2040301@samsung.com> (raw)
In-Reply-To: <loom.20130905T110125-516@post.gmane.org>
On 09/05/2013 06:12 PM, Prasanna NAVARATNA wrote:
> Hello,
>
>> http://permalink.gmane.org/gmane.linux.kernel.mmc/15430
> This link mentions that BKOPS_EN 163bit in EXT_CSD is one-time programmable
> flag but from JEDEC Standard No. 84-A441 spec, it is R/W bit. Please
> re-confirm about the statement.
R/W bit is one-time programmable and readable. what do you mean?
>
>
>>> MMC-Utils open source utility for enabling and disabling features.
>>> It use ioctl defined in block/card to send commands to host.
>>> git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc-utils.git
>
> I am not able to find this git in my platform repo.
> Is this mmc-utils git mandatory to have?
> What if, somebody don't have it and need to enabled BKOPS for eMMMC4.41?
> Is mmc-utils the only way to enable BKOPS?
If you want to enable the bkops, then you can use your patch at your local repo, not mainline.
Best Regards,
Jaehoon Chung
>
> Regards,
> Prasanna NAVARATNA
>
> --
> 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:[~2013-09-05 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 12:09 [PATCH] mmc: enable BKOPS for supported eMMC(4.41) Prasanna NAVARATNA
2013-09-02 6:24 ` Jaehoon Chung
2013-09-03 8:58 ` Prasanna NAVARATNA
2013-09-03 9:34 ` Nitin Singla
2013-09-04 2:34 ` Jaehoon Chung
2013-09-05 9:12 ` Prasanna NAVARATNA
2013-09-05 13:03 ` Jaehoon Chung [this message]
2013-09-05 14:12 ` Prasanna NAVARATNA
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=5228812A.2040301@samsung.com \
--to=jh80.chung@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=prasanna.navaratna@gmail.com \
/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.