From: Brian Masney <masneyb@onstation.org>
To: andy.gross@linaro.org
Cc: david.brown@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linus.walleij@linaro.org,
linux-gpio@vger.kernel.org
Subject: [PATCH 5/8] arm64: dts: qcom: pm8005: add gpio-ranges
Date: Tue, 5 Mar 2019 19:53:13 -0500 [thread overview]
Message-ID: <20190306005316.12232-6-masneyb@onstation.org> (raw)
In-Reply-To: <20190306005316.12232-1-masneyb@onstation.org>
This adds the gpio-ranges property so that the GPIO pins are initialized
by the GPIO framework and not pinctrl. This fixes a circular dependency
between these two frameworks so GPIO hogging can be used on this board.
This was not tested on this particular hardware, however this same
change was tested on qcom-pm8941 using a LG Nexus 5 (hammerhead) phone.
Signed-off-by: Brian Masney <masneyb@onstation.org>
---
arch/arm64/boot/dts/qcom/pm8005.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/qcom/pm8005.dtsi b/arch/arm64/boot/dts/qcom/pm8005.dtsi
index c0ddf128136c..3f97607d8baa 100644
--- a/arch/arm64/boot/dts/qcom/pm8005.dtsi
+++ b/arch/arm64/boot/dts/qcom/pm8005.dtsi
@@ -15,6 +15,7 @@
compatible = "qcom,pm8005-gpio", "qcom,spmi-gpio";
reg = <0xc000>;
gpio-controller;
+ gpio-ranges = <&pm8005_gpio 0 0 4>;
#gpio-cells = <2>;
interrupt-controller;
#interrupt-cells = <2>;
--
2.20.1
next prev parent reply other threads:[~2019-03-06 0:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 0:53 [PATCH 0/8] qcom: spmi/ssbi gpio: correct gpio hogging Brian Masney
2019-03-06 0:53 ` [PATCH 1/8] ARM: dts: qcom: apq8064: add gpio-ranges Brian Masney
2019-03-06 0:53 ` [PATCH 2/8] ARM: dts: qcom: mdm9615: " Brian Masney
2019-03-06 0:53 ` [PATCH 3/8] ARM: dts: qcom: msm8660: " Brian Masney
2019-03-06 0:53 ` [PATCH 4/8] ARM: dts: qcom: pma8084: " Brian Masney
2019-03-06 0:53 ` Brian Masney [this message]
2019-03-06 0:53 ` [PATCH 6/8] arm64: dts: qcom: pm8998: " Brian Masney
2019-03-06 0:53 ` [PATCH 7/8] arm64: dts: qcom: pmi8994: " Brian Masney
2019-03-06 0:53 ` [PATCH 8/8] arm64: dts: qcom: pmi8998: " Brian Masney
2019-03-06 7:14 ` [PATCH 0/8] qcom: spmi/ssbi gpio: correct gpio hogging Linus Walleij
2019-04-27 5:30 ` Bjorn Andersson
2019-04-27 10:22 ` Brian Masney
2019-04-30 17:13 ` Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190306005316.12232-6-masneyb@onstation.org \
--to=masneyb@onstation.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).