UPSTREAM: ath10k: snoc: relax voltage requirements
I rarely see drivers specify precise voltage requirements like this, but if we really have to...let's at least give a little wiggle room. Board designs (and accompanying device trees) may not provide exactly the voltage listed here, and we shouldn't fail to probe just because of this. Round these ranges down to the nearest volt, and provide a 0.05V margin. The regulator should provide its own supported ranges, which will helpfully intersect with these ranges. I would just as well remove these ranges entirely, but if I understand correctly, there's some reason that QCOM SoC's like to set zero / non-zero voltages. BUG=b:137525452 TEST=None Signed-off-by:Brian Norris <briannorris@chromium.org> Reviewed-by:
Douglas Anderson <dianders@chromium.org> Signed-off-by:
Kalle Valo <kvalo@codeaurora.org> Signed-off-by:
Govind Singh <govinds@codeaurora.org> (Cherry picked from commit bfe57a6a) (Source: git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git ) Change-Id: I6e9f5fae6f8b77a1c7358f418727b5fc77aaca76 Signed-off-by:
Vamsi Singamsetty <vamssi@codeaurora.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/1710370 Reviewed-by:
Julan Hsu <julanhsu@google.com> Reviewed-by:
Sean Paul <seanpaul@chromium.org> Tested-by:
Julan Hsu <julanhsu@google.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
Loading
Please sign in to comment