From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Shaik Sajida Bhanu <sbhanu@codeaurora.org>,
ulf.hansson@linaro.org, adrian.hunter@intel.com,
robh+dt@kernel.org
Cc: rampraka@codeaurora.org, sartgarg@codeaurora.org,
nitirawa@codeaurora.org, sayalil@codeaurora.org,
cang@codeaurora.org, linux-mmc@vger.kernel.org,
agross@kernel.org, devicetree@vger.kernel.org,
stummala@codeaurora.org, pragalla@codeaurora.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
asutoshd@codeaurora.org
Subject: Re: (subset) [PATCH V1] arm64: dts: qcom: sc7180: Use maximum drive strength values for eMMC
Date: Thu, 23 Sep 2021 15:30:59 -0500 [thread overview]
Message-ID: <163242893971.825761.9292228692666120286.b4-ty@linaro.org> (raw)
In-Reply-To: <1629132650-26277-1-git-send-email-sbhanu@codeaurora.org>
On Mon, 16 Aug 2021 22:20:50 +0530, Shaik Sajida Bhanu wrote:
> The current drive strength values are not sufficient on non discrete
> boards and this leads to CRC errors during switching to HS400 enhanced
> strobe mode.
>
> Hardware simulation results on non discrete boards shows up that use the
> maximum drive strength values for data and command lines could helps
> in avoiding these CRC errors.
>
> [...]
Applied, thanks!
[1/1] arm64: dts: qcom: sc7180: Use maximum drive strength values for eMMC
commit: 752432e40e8f0d02d0af07cce2d6d4b250be11ef
Best regards,
--
Bjorn Andersson <bjorn.andersson@linaro.org>
prev parent reply other threads:[~2021-09-23 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 16:50 [PATCH V1] arm64: dts: qcom: sc7180: Use maximum drive strength values for eMMC Shaik Sajida Bhanu
2021-08-17 13:58 ` Doug Anderson
2021-08-19 13:44 ` Doug Anderson
2021-09-23 20:19 ` Doug Anderson
2021-09-23 20:30 ` Bjorn Andersson [this message]
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=163242893971.825761.9292228692666120286.b4-ty@linaro.org \
--to=bjorn.andersson@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=agross@kernel.org \
--cc=asutoshd@codeaurora.org \
--cc=cang@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nitirawa@codeaurora.org \
--cc=pragalla@codeaurora.org \
--cc=rampraka@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sartgarg@codeaurora.org \
--cc=sayalil@codeaurora.org \
--cc=sbhanu@codeaurora.org \
--cc=stummala@codeaurora.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;
as well as URLs for NNTP newsgroup(s).