From: Greg KH <greg@kroah.com>
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: stable@vger.kernel.org, loic.poulain@linaro.org
Subject: Re: [PATCH 4.14] mmc: sdhci-msm: Disable CDR function on TX
Date: Fri, 18 Jan 2019 16:59:16 +0100 [thread overview]
Message-ID: <20190118155916.GA11503@kroah.com> (raw)
In-Reply-To: <20190118134000.14707-1-georgi.djakov@linaro.org>
On Fri, Jan 18, 2019 at 03:39:59PM +0200, Georgi Djakov wrote:
> From: Loic Poulain <loic.poulain@linaro.org>
>
> commit a89e7bcb18081c611eb6cf50edd440fa4983a71a upstream.
>
> The Clock Data Recovery (CDR) circuit allows to automatically adjust
> the RX sampling-point/phase for high frequency cards (SDR104, HS200...).
> CDR is automatically enabled during DLL configuration.
> However, according to the APQ8016 reference manual, this function
> must be disabled during TX and tuning phase in order to prevent any
> interferences during tuning challenges and unexpected phase alteration
> during TX transfers.
>
> This patch enables/disables CDR according to the current transfer mode.
>
> This fixes sporadic write transfer issues observed with some SDR104 and
> HS200 cards.
>
> Inspired by sdhci-msm downstream patch:
> https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/432516/
>
> Reported-by: Leonid Segal <leonid.s@variscite.com>
> Reported-by: Manabu Igusa <migusa@arrowjapan.com>
> Signed-off-by: Loic Poulain <loic.poulain@linaro.org>
> Acked-by: Adrian Hunter <adrian.hunter@intel.com>
> Acked-by: Georgi Djakov <georgi.djakov@linaro.org>
> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
> [georgi: backport to v4.14]
> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
Both patches now applied, thanks.
greg k-h
prev parent reply other threads:[~2019-01-18 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 13:39 [PATCH 4.14] mmc: sdhci-msm: Disable CDR function on TX Georgi Djakov
2019-01-18 13:40 ` [PATCH 4.19,4.20] " Georgi Djakov
2019-01-18 15:59 ` Greg KH [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=20190118155916.GA11503@kroah.com \
--to=greg@kroah.com \
--cc=georgi.djakov@linaro.org \
--cc=loic.poulain@linaro.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.