summaryrefslogtreecommitdiff
path: root/init/version.c
diff options
context:
space:
mode:
authorDouglas Anderson <dianders@chromium.org>2020-07-09 17:40:49 +0300
committerBjorn Andersson <bjorn.andersson@linaro.org>2020-07-14 02:30:01 +0300
commit5f219524ec6eae3591f9d7cfbf4d30fc457f1eec (patch)
treee0c52ad5da2331cb1739bbd7ea3da96d74129651 /init/version.c
parent68890e20942b8693d487a4a2ea882e36523e8193 (diff)
downloadlinux-5f219524ec6eae3591f9d7cfbf4d30fc457f1eec.tar.xz
spi: spi-geni-qcom: Set the clock properly at runtime resume
In the patch ("spi: spi-geni-qcom: Avoid clock setting if not needed") we avoid a whole pile of clock code. As part of that, we should have restored the clock at runtime resume. Do that. It turns out that, at least with today's configurations, this doesn't actually matter. That's because none of the current device trees have an OPP table for geni SPI yet. That makes dev_pm_opp_set_rate(dev, 0) a no-op. This is why it wasn't noticed in the testing of the original patch. It's still a good idea to fix, though. Reviewed-by: Rajendra Nayak <rnayak@codeaurora.org> Reviewed-by: Akash Asthana <akashast@codeaurora.org> Signed-off-by: Douglas Anderson <dianders@chromium.org> Acked-by: Mark Brown <broonie@kernel.org> Link: https://lore.kernel.org/r/20200709074037.v2.1.I0b701fc23eca911a5bde4ae4fa7f97543d7f960e@changeid Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Diffstat (limited to 'init/version.c')
0 files changed, 0 insertions, 0 deletions