RE: [PATCH 1/7] mmc-utils: interpret OPTIMAL_*_SIZE fields in extcsd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: RE: [PATCH 1/7] mmc-utils: interpret OPTIMAL_*_SIZE fields in extcsd
From: Avri Altman <Avri.Altman@xxxxxxx>
Date: Wed, 10 Oct 2018 08:40:26 +0000
Accept-language: en-US
Cc: "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <4a016f761d388a989059467507f2bc948ba26c6c.1539103468.git.jamesnuss@nanometrics.ca>
Wdcipoutbound: EOP-TRUE

Looks fine.

Thanks,
Avri

> eMMC 5.0 introduced OPTIMAL_READ_SIZE, OPTIMAL_WRITE_SIZE and
> OPTIMAL
> TRIM_UNIT_SIZE fields in the extcsd
> 
> Interpret these fields when reading out the extcsd with human-readable
> results
> 
> Signed-off-by: James Nuss <jamesnuss@xxxxxxxxxxxxxx>
Reviewed-by: Avri Altman <avri.altman@xxxxxxx>

Follow-Ups:
- Re: [PATCH 1/7] mmc-utils: interpret OPTIMAL_*_SIZE fields in extcsd
  - From: Christoph Fritz

References:
- [PATCH 0/7] fix bugs in write_reliability and enh_area set commands + more extcsd parsing
  - From: James Nuss
- [PATCH 1/7] mmc-utils: interpret OPTIMAL_*_SIZE fields in extcsd
  - From: James Nuss

Prev by Date: Re: [PATCH 1/3] clk: renesas: r7s9210: Add SDHI clocks
Next by Date: Re: [PATCH 2/3] mmc: renesas_sdhi_internal_dmac: Add R7S9210 support
Previous by thread: [PATCH 1/7] mmc-utils: interpret OPTIMAL_*_SIZE fields in extcsd
Next by thread: Re: [PATCH 1/7] mmc-utils: interpret OPTIMAL_*_SIZE fields in extcsd
Index(es):
- Date
- Thread

[Index of Archives] [Linux Memonry Technology] [Linux USB Devel] [Linux Media] [Video for Linux] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux