[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cd24b840-3509-1c03-373b-85026c01b0f7@nvidia.com>
Date: Fri, 13 Jul 2018 15:04:13 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: Aapo Vienamo <avienamo@...dia.com>,
Marcel Ziswiler <marcel.ziswiler@...adex.com>
CC: "ulf.hansson@...aro.org" <ulf.hansson@...aro.org>,
Stefan Agner <stefan.agner@...adex.com>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
"thierry.reding@...il.com" <thierry.reding@...il.com>,
"adrian.hunter@...el.com" <adrian.hunter@...el.com>
Subject: Re: REGRESSION: [PATCH] mmc: tegra: Use sdhci_pltfm_clk_get_max_clock
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
Powered by blists - more mailing lists