mmc: enable TRIM/ERASE caps for SDHCI host
Get series with b4
b4 am [email protected]Versions newest first
- v4 Latest3 patches 10 repliesIn review
Patches in v4 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | mmc: set max_discard_sectors value for mmc queuedrivers/ drivers/ include/ | +23 | 6 replies | |
| 2/3 | mmc: enable TRIM/ERASE caps for SDHCI hostdrivers/ | +11 | 6 replies | |
| 3/3 | mmc: fix division by zero when cal erase timeoutdrivers/ | +8 | 0 replies |
Reviews trailers per patch
None of the 3 patches has a Reviewed-by or Acked-by.
| Patch | Sascha Silbe |
|---|---|
| 1/3 | |
| 2/3 | T-b |
| 3/3 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v4 0/3]mmc: enable TRIM/ERASE caps for SDHCI host
Hi Chris,
These patches enable TRIM/ERASE capability for SDHCI host controller.
patch001: mmc: set max_discard_sectors value for mmc queue Rightnow max_discard_sectors value for mmc queue is UINT_MAX which means block layer can accept unlimited sectors to erase at one time. But this may delay some other important I/O requests. So set a suitable value for max_discard_sectors value by using 'pref_erase'
patch0002: mmc: enable TRIM/ERASE capability for SDHCI host. ERASE command needs R1B response, so before sending command, SDHCI host driver also need to set timeout control register for such command
patch0003: mmc: fix division by zero when calculate erase timeout when enable clock gating feature, host clock may be zero when calculate erase timeout value and this will cause division by zero bug.
Thanks
Chuanxiao