From: Bean Huo <huobean@gmail.com>
To: ulf.hansson@linaro.org, adrian.hunter@intel.com,
jakob.rossler@nokia.com, Avri.Altman@wdc.com
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Bean Huo <beanhuo@micron.com>
Subject: Re: [PATCH v2 RESENT] mmc-utils: Add General command CMD56 read support
Date: Fri, 22 Apr 2022 21:41:45 +0200 [thread overview]
Message-ID: <c5f33892dbce61b267cc74dca50e0fae5d1270e9.camel@gmail.com> (raw)
In-Reply-To: <20220417111622.621650-1-huobean@gmail.com>
On Sun, 2022-04-17 at 13:16 +0200, Bean Huo wrote:
> From: Bean Huo <beanhuo@micron.com>
>
> We can use GEN_CMD (CMD56) to read a data block with vendor-specific
> format and meaning, which is very helpful and useful for customers to
> analyze device health. This patch is to add support for this command.
>
> At the same time, in order to make CMD56 universal, let more users of
> mmc-utils can benefit from this. We will allow the user to enter
> [arg]
> for special commands. Because some eMMC vendors provide an additional
> set of commands beyond the GEN_CMD (CMD56) definition in the JEDEC
> specification. These additional commands are implemented using
> generic
> CMD56 commands, and they return a wealth of useful information about
> the
> state of the NAND device. For these special purposes, the [31:1]stuff
> bits in the CMD56 argument are used. You can refer to Micron eMMC
> "TN-FC-32: e·MMC Device Health Report" as an example.
>
> I didn't add data parsing, just print the raw data as it is vendor-
> specific.
>
> Signed-off-by: Bean Huo <beanhuo@micron.com>
> Acked-by: Avri Altman <Avri.Altman@wdc.com>
> Tested-by: Rossler Jakob (Nokia - DE/Ulm) <jakob.rossler@nokia.com>
> ---
Hi Ullf,
Would you be willing to merge this patch into your mmc-utils git repo?
Kind regards,
Bean
next prev parent reply other threads:[~2022-04-22 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 11:16 Bean Huo
2022-04-22 19:41 ` Bean Huo [this message]
2022-04-26 11:49 ` Ulf Hansson
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=c5f33892dbce61b267cc74dca50e0fae5d1270e9.camel@gmail.com \
--to=huobean@gmail.com \
--cc=Avri.Altman@wdc.com \
--cc=adrian.hunter@intel.com \
--cc=beanhuo@micron.com \
--cc=jakob.rossler@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®