From: DooHyun Hwang <dh0421.hwang@samsung.com>
To: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, ulf.hansson@linaro.org,
robh+dt@kernel.org, axboe@kernel.dk, adrian.hunter@intel.com,
satyat@google.com, ebiggers@google.com, gustavoars@kernel.org
Cc: grant.jung@samsung.com, jt77.jang@samsung.com,
junwoo80.lee@samsung.com, jangsub.yi@samsung.com,
sh043.lee@samsung.com, cw9316.lee@samsung.com,
sh8267.baek@samsung.com, wkon.kim@samsung.com,
DooHyun Hwang <dh0421.hwang@samsung.com>
Subject: [PATCH 1/2] dt-bindings: mmc: Add no-single-read-retry property
Date: Wed, 17 Feb 2021 14:22:38 +0900 [thread overview]
Message-ID: <20210217052239.13780-2-dh0421.hwang@samsung.com> (raw)
In-Reply-To: <20210217052239.13780-1-dh0421.hwang@samsung.com>
Add an optional property to not retry multiple block read error
with several single block reads.
This property makes to handle read errors faster by not retrying
multiple block read errors with single block reads.
Signed-off-by: DooHyun Hwang <dh0421.hwang@samsung.com>
---
Documentation/devicetree/bindings/mmc/mmc-controller.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/mmc-controller.yaml b/Documentation/devicetree/bindings/mmc/mmc-controller.yaml
index e141330c1114..1eb3b73a164a 100644
--- a/Documentation/devicetree/bindings/mmc/mmc-controller.yaml
+++ b/Documentation/devicetree/bindings/mmc/mmc-controller.yaml
@@ -245,6 +245,12 @@ properties:
Controller is limited to send MMC commands during
initialization.
+ no-single-read-retry:
+ $ref: /schemas/types.yaml#/definitions/flag
+ description:
+ Single block read retrying is not supported
+ when multiple block read fails.
+
fixed-emmc-driver-type:
description:
For non-removable eMMC, enforce this driver type. The value is
--
2.29.0
next prev parent reply other threads:[~2021-02-17 5:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210217053519epcas1p4204253d3af8e1c6d2a5c3acb73eb877f@epcas1p4.samsung.com>
2021-02-17 5:22 ` [PATCH 0/2] mmc: core: add a new property DooHyun Hwang
[not found] ` <CGME20210217053520epcas1p1af462836bd9fc690d99baed0b122d6fd@epcas1p1.samsung.com>
2021-02-17 5:22 ` DooHyun Hwang [this message]
[not found] ` <CGME20210217053521epcas1p2aa80cae5d52f30c8c8882f44abe8045c@epcas1p2.samsung.com>
2021-02-17 5:22 ` [PATCH 2/2] mmc: core: Add no single read retries DooHyun Hwang
2021-02-17 5:46 ` Adrian Hunter
2021-02-17 6:00 ` Adrian Hunter
2021-02-17 8:46 ` DooHyun Hwang
2021-03-01 8:23 ` Ulf Hansson
2021-02-17 5:19 [PATCH 0/2] mmc: core: add a new property DooHyun Hwang
[not found] ` <CGME20210217053240epcas1p44ae9b8ae5bd4fe792317cfe0fe683f98@epcas1p4.samsung.com>
2021-02-17 5:19 ` [PATCH 1/2] dt-bindings: mmc: Add no-single-read-retry property DooHyun Hwang
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=20210217052239.13780-2-dh0421.hwang@samsung.com \
--to=dh0421.hwang@samsung.com \
--cc=adrian.hunter@intel.com \
--cc=axboe@kernel.dk \
--cc=cw9316.lee@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=ebiggers@google.com \
--cc=grant.jung@samsung.com \
--cc=gustavoars@kernel.org \
--cc=jangsub.yi@samsung.com \
--cc=jt77.jang@samsung.com \
--cc=junwoo80.lee@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=satyat@google.com \
--cc=sh043.lee@samsung.com \
--cc=sh8267.baek@samsung.com \
--cc=ulf.hansson@linaro.org \
--cc=wkon.kim@samsung.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 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).