summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorJohan Hovold <johan+linaro@kernel.org>2024-10-25 14:16:22 +0200
committerLinus Walleij <linus.walleij@linaro.org>2024-11-18 00:40:49 +0100
commit6bc0ebfb1d920f13c522545f114cdabb49e9408a (patch)
treece8518993aa6512d498e0c78877acfbb86936874 /tools/perf/scripts/python/exported-sql-viewer.py
parentafe9803e3b82f0d05b6848a854604dcaaeb5ded0 (diff)
downloadlinux-stable-6bc0ebfb1d920f13c522545f114cdabb49e9408a.tar.gz
linux-stable-6bc0ebfb1d920f13c522545f114cdabb49e9408a.tar.bz2
linux-stable-6bc0ebfb1d920f13c522545f114cdabb49e9408a.zip
pinctrl: qcom: spmi: fix debugfs drive strength
Commit 723e8462a4fe ("pinctrl: qcom: spmi-gpio: Fix the GPIO strength mapping") fixed a long-standing issue in the Qualcomm SPMI PMIC gpio driver which had the 'low' and 'high' drive strength settings switched but failed to update the debugfs interface which still gets this wrong. Fix the debugfs code so that the exported values match the hardware settings. Note that this probably means that most devicetrees that try to describe the firmware settings got this wrong if the settings were derived from debugfs. Before the above mentioned commit the settings would have actually matched the firmware settings even if they were described incorrectly, but now they are inverted. Fixes: 723e8462a4fe ("pinctrl: qcom: spmi-gpio: Fix the GPIO strength mapping") Fixes: eadff3024472 ("pinctrl: Qualcomm SPMI PMIC GPIO pin controller driver") Cc: Anjelique Melendez <quic_amelende@quicinc.com> Cc: stable@vger.kernel.org # 3.19 Signed-off-by: Johan Hovold <johan+linaro@kernel.org> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> Link: https://lore.kernel.org/20241025121622.1496-1-johan+linaro@kernel.org Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions