From: Johan Hovold <johan@kernel.org>
To: Andrew Halaney <ahalaney@redhat.com>
Cc: Johan Hovold <johan+linaro@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Felipe Balbi <balbi@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Wesley Cheng <quic_wcheng@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] arm64: dts: qcom: sc8280xp: fix USB interrupts
Date: Wed, 13 Jul 2022 16:35:22 +0200 [thread overview]
Message-ID: <Ys7YKkRAAI0Vbseh@hovoldconsulting.com> (raw)
In-Reply-To: <20220713141228.5z5rmgepj6mepjyp@halaneylaptop>
On Wed, Jul 13, 2022 at 09:12:28AM -0500, Andrew Halaney wrote:
> On Wed, Jul 13, 2022 at 03:13:38PM +0200, Johan Hovold wrote:
> > The two single-port SC8280XP USB controllers do not have an hs_phy_irq
> > interrupt. Instead they have a pwr_event interrupt which is distinct
> > from the former and not yet supported by the driver.
> >
> > Fix the USB node interrupt names so that they match the devicetree
> > binding.
> >
> > Fixes: 152d1faf1e2f ("arm64: dts: qcom: add SC8280XP platform")
> > Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
> > ---
> > arch/arm64/boot/dts/qcom/sc8280xp.dtsi | 12 ++++++++----
> > 1 file changed, 8 insertions(+), 4 deletions(-)
> >
> > diff --git a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
> > index 45cc7d714fd2..4a7aa9992f3a 100644
> > --- a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
> > @@ -1875,8 +1875,10 @@ usb_0: usb@a6f8800 {
> > <&pdc 14 IRQ_TYPE_EDGE_BOTH>,
> > <&pdc 15 IRQ_TYPE_EDGE_BOTH>,
> > <&pdc 138 IRQ_TYPE_LEVEL_HIGH>;
> > - interrupt-names = "hs_phy_irq", "dp_hs_phy_irq",
> > - "dm_hs_phy_irq", "ss_phy_irq";
> > + interrupt-names = "pwr_event",
> > + "dp_hs_phy_irq",
> > + "dm_hs_phy_irq",
> > + "ss_phy_irq";
> >
> > power-domains = <&gcc USB30_PRIM_GDSC>;
> >
> > @@ -1925,8 +1927,10 @@ usb_1: usb@a8f8800 {
> > <&pdc 12 IRQ_TYPE_EDGE_BOTH>,
> > <&pdc 13 IRQ_TYPE_EDGE_BOTH>,
> > <&pdc 136 IRQ_TYPE_LEVEL_HIGH>;
> > - interrupt-names = "hs_phy_irq", "dp_hs_phy_irq",
> > - "dm_hs_phy_irq", "ss_phy_irq";
> > + interrupt-names = "pwr_event",
> > + "dp_hs_phy_irq",
> > + "dm_hs_phy_irq",
> > + "ss_phy_irq";
>
> For this specific change to pwr_event:
>
> Reviewed-by: Andrew Halaney <ahalaney@redhat.com>
>
> That being said, I was reviewing this against the (fairly old)
> downstream release I have, and the IRQs defined there look like this:
>
> interrupts-extended = <&pdc 12 IRQ_TYPE_EDGE_RISING>,
> <&intc GIC_SPI 811 IRQ_TYPE_LEVEL_HIGH>,
> <&pdc 136 IRQ_TYPE_LEVEL_HIGH>,
> <&pdc 13 IRQ_TYPE_EDGE_RISING>;
> interrupt-names = "dp_hs_phy_irq", "pwr_event_irq",
> "ss_phy_irq", "dm_hs_phy_irq";
>
> The part I want to highlight is that the "pwr_event" irq downstream maps
> to <&intc GIC_SPI 811 IRQ_TYPE_LEVEL_HIGH>, but the current upstream
> devicetree I'm looking at has it mapped to <&intc GIC_SPI 136 IRQ_TYPE_LEVEL_HIGH>
>
> Do you happen to have any source you can also check to confirm if this
> is a bug or not?
Good catch! I believe this is another copy-paste error when creating
base dtsi based on some vendor source (or perhaps an error carried over
from an earlier version).
The vendor devicetree I have access to also has 811 here, which matches
the pattern for usb_0 (dwc3 interrupt + 1).
Do you mind if I fold a fix for that into a v2 of this patch?
Thanks for reviewing!
Johan
next prev parent reply other threads:[~2022-07-13 14:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 13:13 [PATCH 0/7] usb: dwc3: add support for SC8280XP Johan Hovold
2022-07-13 13:13 ` [PATCH 1/7] dt-bindings: usb: qcom,dwc3: add SC8280XP binding Johan Hovold
2022-07-14 10:48 ` Krzysztof Kozlowski
2022-07-14 10:51 ` Krzysztof Kozlowski
2022-07-13 13:13 ` [PATCH 2/7] dt-bindings: usb: qcom,dwc3: refine interrupt requirements Johan Hovold
2022-07-14 10:50 ` Krzysztof Kozlowski
2022-07-13 13:13 ` [PATCH 3/7] usb: dwc3: qcom: fix missing optional irq warnings Johan Hovold
2022-07-13 14:00 ` Andrew Halaney
2022-07-13 13:13 ` [PATCH 4/7] arm64: dts: qcom: sc8280xp: fix USB clock order Johan Hovold
2022-07-14 10:52 ` Krzysztof Kozlowski
2022-07-13 13:13 ` [PATCH 5/7] arm64: dts: qcom: sc8280xp: fix USB interrupts Johan Hovold
2022-07-13 14:12 ` Andrew Halaney
2022-07-13 14:35 ` Johan Hovold [this message]
2022-07-13 14:43 ` Andrew Halaney
2022-07-13 15:03 ` Johan Hovold
2022-07-14 10:52 ` Krzysztof Kozlowski
2022-07-13 13:13 ` [PATCH 6/7] arm64: dts: qcom: sc7280: reorder " Johan Hovold
2022-07-14 10:54 ` Krzysztof Kozlowski
2022-07-13 13:13 ` [PATCH 7/7] arm64: dts: qcom: " Johan Hovold
2022-07-14 10:54 ` Krzysztof Kozlowski
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=Ys7YKkRAAI0Vbseh@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=agross@kernel.org \
--cc=ahalaney@redhat.com \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_wcheng@quicinc.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