From: Jon Hunter <jonathanh@nvidia.com>
To: Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
"Ritesh Harjani" <riteshh@codeaurora.org>
Cc: <linux-mmc@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] mmc: sdhci: Add support for setting parent clock
Date: Thu, 16 Mar 2017 18:00:00 +0000 [thread overview]
Message-ID: <6072f40f-78e1-9c7a-6c9a-8db99f771af1@nvidia.com> (raw)
In-Reply-To: <1489660364-17698-1-git-send-email-jonathanh@nvidia.com>
On 16/03/17 10:32, Jon Hunter wrote:
> It is common for SD/MMC host controllers to set the parent clock that
> drives the SD/MMC interface in order to support various operating
> speeds. Typically, this is performed by calling common clock framework
> APIs such as clk_set_rate(). The problem is that these APIs may sleep
> and must not be called from within atomic sections and therefore, these
> functions cannot be called within the existing 'set_clock' SDHCI
> operator because they are called from within the context of a spinlock.
> Add a new 'set_parent_clock' operator for the SDHCI driver that is
> called early during the SDHCI 'set_ios' before the spinlock is aquire to
> give the platform driver the opportunity to set the parent clock rate.
>
> Please note that, unfortunately, the Tegra and MSM SDHCI drivers
> currently appear to mis-use the 'set_clock' operator by calling
> clk_set_rate(). In the case of Tegra, occasionally but not always,
> 'scheduling while atomic' errors are reported (so most of the time we
> are getting lucky). In the of the MSM SDHCI driver, it is releasing and
> re-acquiring the spinlock which is bad.
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
>
> I have not attempted to fix the MSM driver in this seris, but I am
> copying hopefully, the right people to fix it.
>
> drivers/mmc/host/sdhci.c | 3 +++
> drivers/mmc/host/sdhci.h | 2 ++
> 2 files changed, 5 insertions(+)
>
> diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
> index 6fdd7a70f229..b7f1521edbec 100644
> --- a/drivers/mmc/host/sdhci.c
> +++ b/drivers/mmc/host/sdhci.c
> @@ -1579,6 +1579,9 @@ static void sdhci_set_ios(struct mmc_host *mmc, struct mmc_ios *ios)
> if (ios->power_mode == MMC_POWER_UNDEFINED)
> return;
>
> + if (host->ops->set_parent_clock)
> + host->ops->set_parent_clock(host, ios->power_mode);
Ugh ... not sure what happened here but this should be 'ios->clock'! And
I did test this!
Sorry will resend.
Jon
--
nvpublic
next prev parent reply other threads:[~2017-03-16 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 10:32 Jon Hunter
2017-03-16 10:32 ` [PATCH 2/2] mmc: tegra: Fix setting of Tegra SDHCI module clock Jon Hunter
2017-03-16 18:00 ` Jon Hunter [this message]
2017-03-20 19:22 ` [PATCH 1/2] mmc: sdhci: Add support for setting parent clock Adrian Hunter
2017-03-20 20:31 ` Jon Hunter
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=6072f40f-78e1-9c7a-6c9a-8db99f771af1@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=riteshh@codeaurora.org \
--cc=thierry.reding@gmail.com \
--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
all inboxes | Powered by JetHome®