From: skakit@codeaurora.org
To: Stephen Boyd <swboyd@chromium.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
David Collins <collinsd@codeaurora.org>,
Kiran Gunda <kgunda@codeaurora.org>,
linux-gpio@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/2] pinctrl: qcom: spmi-gpio: correct parent irqspec translation
Date: Wed, 18 Aug 2021 10:56:18 +0530 [thread overview]
Message-ID: <5be25c9710b7706cff91f1db71f9e25e@codeaurora.org> (raw)
In-Reply-To: <CAE-0n52Ki2tA6qy6ADym3r4UQ0tkvgz3bpif_Mm2q3Y+N=huGg@mail.gmail.com>
On 2021-08-18 00:45, Stephen Boyd wrote:
> Quoting skakit@codeaurora.org (2021-08-17 02:06:42)
>> On 2021-08-17 02:38, Stephen Boyd wrote:
>> >
>> > Are there any boards supported upstream that have a gpio block that
>> > isn't at 0xc000?
>>
>> yes, all the pmics used in sm8350-mtp.dts board have gpio block at
>> addresses different than 0xc000.
>>
>
> So maybe
>
> Fixes: f67cc6a91d88 ("arm64: dts: qcom: sm8350-mtp: Add PMICs")
>
> is appropriate then?
This patch is actually fixing the pinctrl-spmi-gpio.c driver.
So, I think we should add
Fixes: ca69e2d165eb ("qcom: spmi-gpio: add support for hierarchical IRQ
chip")
next prev parent reply other threads:[~2021-08-18 5:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 4:55 [PATCH 0/2] Add Vol+ support for sc7280-idp satya priya
2021-08-13 4:55 ` [PATCH 1/2] pinctrl: qcom: spmi-gpio: correct parent irqspec translation satya priya
2021-08-13 8:57 ` Linus Walleij
2021-08-16 6:50 ` skakit
2021-08-16 21:08 ` Stephen Boyd
2021-08-17 9:06 ` skakit
2021-08-17 19:15 ` Stephen Boyd
2021-08-18 5:26 ` skakit [this message]
2021-09-02 3:37 ` Stephen Boyd
2021-08-13 4:55 ` [PATCH 2/2] arm64: dts: sc7280: Add volume up support for sc7280-idp satya priya
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=5be25c9710b7706cff91f1db71f9e25e@codeaurora.org \
--to=skakit@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=collinsd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=kgunda@codeaurora.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=robh+dt@kernel.org \
--cc=swboyd@chromium.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).