[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190306005316.12232-1-masneyb@onstation.org>
Date: Tue, 5 Mar 2019 19:53:08 -0500
From: Brian Masney <masneyb@...tation.org>
To: andy.gross@...aro.org
Cc: david.brown@...aro.org, robh+dt@...nel.org, mark.rutland@....com,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linus.walleij@...aro.org,
linux-gpio@...r.kernel.org
Subject: [PATCH 0/8] qcom: spmi/ssbi gpio: correct gpio hogging
Here are some patches that fix gpio hogging for all boards that use
spmi-gpio and ssbi-gpio. These depend on the following two patches
that were merged in 4.20-rc1:
commit 149a96047237 ("pinctrl: qcom: spmi-gpio: fix gpio-hog related
boot issues")
commit 7ed078557738 ("pinctrl: qcom: ssbi-gpio: fix gpio-hog related
boot issues")
I've already fixed pm8941 for the Nexus 5 and that fix is queued to go
into v5.1 during this merge window:
https://lore.kernel.org/lkml/20181101001149.13453-7-masneyb@onstation.org/
Andy: You may want to consider submitting these post rc1 as a fix for
v5.1 and possibly marking these for stable.
Brian Masney (8):
ARM: dts: qcom: apq8064: add gpio-ranges
ARM: dts: qcom: mdm9615: add gpio-ranges
ARM: dts: qcom: msm8660: add gpio-ranges
ARM: dts: qcom: pma8084: add gpio-ranges
arm64: dts: qcom: pm8005: add gpio-ranges
arm64: dts: qcom: pm8998: add gpio-ranges
arm64: dts: qcom: pmi8994: add gpio-ranges
arm64: dts: qcom: pmi8998: add gpio-ranges
arch/arm/boot/dts/qcom-apq8064.dtsi | 1 +
arch/arm/boot/dts/qcom-mdm9615.dtsi | 1 +
arch/arm/boot/dts/qcom-msm8660.dtsi | 1 +
arch/arm/boot/dts/qcom-pma8084.dtsi | 1 +
arch/arm64/boot/dts/qcom/pm8005.dtsi | 1 +
arch/arm64/boot/dts/qcom/pm8998.dtsi | 1 +
arch/arm64/boot/dts/qcom/pmi8994.dtsi | 1 +
arch/arm64/boot/dts/qcom/pmi8998.dtsi | 1 +
8 files changed, 8 insertions(+)
--
2.20.1
Powered by blists - more mailing lists