From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Brian Masney <masneyb@onstation.org>
Cc: andy.gross@linaro.org, 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: Re: [PATCH 0/8] qcom: spmi/ssbi gpio: correct gpio hogging
Date: Fri, 26 Apr 2019 22:30:34 -0700 [thread overview]
Message-ID: <20190427053034.GH3137@builder> (raw)
In-Reply-To: <20190306005316.12232-1-masneyb@onstation.org>
On Tue 05 Mar 16:53 PST 2019, Brian Masney wrote:
> 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
Looks like I missed the ARM patches before. All 8 picked up now, with
Linus' r-b.
Thanks,
Bjorn
> 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
>
next prev parent reply other threads:[~2019-04-27 5:30 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 ` [PATCH 5/8] arm64: dts: qcom: pm8005: " Brian Masney
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 [this message]
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=20190427053034.GH3137@builder \
--to=bjorn.andersson@linaro.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=masneyb@onstation.org \
--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).