From: Jon Hunter <jonathanh@nvidia.com>
To: Aapo Vienamo <avienamo@nvidia.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>
Cc: "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
Stefan Agner <stefan.agner@toradex.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>
Subject: Re: REGRESSION: [PATCH] mmc: tegra: Use sdhci_pltfm_clk_get_max_clock
Date: Fri, 13 Jul 2018 15:04:13 +0100 [thread overview]
Message-ID: <cd24b840-3509-1c03-373b-85026c01b0f7@nvidia.com> (raw)
In-Reply-To: <20180713155541.286425e9@dhcp-10-21-25-168>
On 13/07/18 13:55, Aapo Vienamo wrote:
> This happens because sdhci_pltfm_clk_get_max_clock() does not actually
> return the maximum clock rate but the current one, leading to smaller
> clock rates on some platforms. I'll send a patch that fixes this for
> sdhci-tegra. Although this raises the question whether the current
> behaviour of sdhci_pltfm_clk_get_max_clock() is desirable or not.
Agree. There is something not right here.
Cheers,
Jon
--
nvpublic
prev parent reply other threads:[~2018-07-13 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 15:35 [PATCH] mmc: tegra: Use sdhci_pltfm_clk_get_max_clock Aapo Vienamo
2018-06-04 15:35 ` Aapo Vienamo
2018-06-05 9:28 ` Thierry Reding
2018-06-05 11:58 ` Peter Geis
2018-06-05 11:58 ` Aapo Vienamo
2018-06-05 11:58 ` Aapo Vienamo
2018-06-05 9:35 ` Adrian Hunter
2018-07-02 13:16 ` Ulf Hansson
2018-07-13 1:43 ` REGRESSION: " Marcel Ziswiler
2018-07-13 9:50 ` Aapo Vienamo
2018-07-13 12:55 ` Aapo Vienamo
2018-07-13 14:04 ` Jon Hunter [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=cd24b840-3509-1c03-373b-85026c01b0f7@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=adrian.hunter@intel.com \
--cc=avienamo@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=stefan.agner@toradex.com \
--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 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.