aboutsummaryrefslogtreecommitdiff
path: root/drivers/net/wireless/ralink/rt2x00/rt2500pci.c
diff options
context:
space:
mode:
authorDouglas Anderson <dianders@chromium.org>2021-02-24 09:50:25 -0800
committerStephen Boyd <sboyd@kernel.org>2021-03-13 13:00:05 -0800
commit148ddaa89d4a0a927c4353398096cc33687755c1 (patch)
treeea627788382e8587e0eb92982677b1cb4ab1cefc /drivers/net/wireless/ralink/rt2x00/rt2500pci.c
parent0ae67123eafd056cc0e27ab27b0d3c5e4bdaf916 (diff)
clk: qcom: gcc-sc7180: Use floor ops for the correct sdcc1 clk
While picking commit a8cd989e1a57 ("mmc: sdhci-msm: Warn about overclocking SD/MMC") back to my tree I was surprised that it was reporting warnings. I thought I fixed those! Looking closer at the fix, I see that I totally bungled it (or at least I halfway bungled it). The SD card clock got fixed (and that was the one I was really focused on fixing), but I totally adjusted the wrong clock for eMMC. Sigh. Let's fix my dumb mistake. Now both SD and eMMC have floor for the "apps" clock. This doesn't matter a lot for the final clock rate for HS400 eMMC but could matter if someone happens to put some slower eMMC on a sc7180. We also transition through some of these lower rates sometimes and having them wrong could cause problems during these transitions. These were the messages I was seeing at boot: mmc1: Card appears overclocked; req 52000000 Hz, actual 100000000 Hz mmc1: Card appears overclocked; req 52000000 Hz, actual 100000000 Hz mmc1: Card appears overclocked; req 104000000 Hz, actual 192000000 Hz Fixes: 6d37a8d19283 ("clk: qcom: gcc-sc7180: Use floor ops for sdcc clks") Signed-off-by: Douglas Anderson <dianders@chromium.org> Link: https://lore.kernel.org/r/20210224095013.1.I2e2ba4978cfca06520dfb5d757768f9c42140f7c@changeid Reviewed-by: Taniya Das <tdas@codeaurora.org> Signed-off-by: Stephen Boyd <sboyd@kernel.org>
Diffstat (limited to 'drivers/net/wireless/ralink/rt2x00/rt2500pci.c')
0 files changed, 0 insertions, 0 deletions