public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Krishna Kurapati PSSNV <quic_kriskura@quicinc.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	cros-qcom-dts-watchers@chromium.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] ARM/arm64: dts: qcom: fix USB wakeup interrupt types
Date: Wed, 13 Dec 2023 18:38:28 +0100	[thread overview]
Message-ID: <ZXnsFIl9i6Ix-woH@hovoldconsulting.com> (raw)
In-Reply-To: <06354190-b572-46e4-8036-0fae7f15dd15@quicinc.com>

On Tue, Dec 12, 2023 at 03:00:07PM +0530, Krishna Kurapati PSSNV wrote:
> On 12/11/2023 10:09 PM, Johan Hovold wrote:
> > On Mon, Nov 20, 2023 at 05:43:20PM +0100, Johan Hovold wrote:

> > Konrad reported off-list that the sc8180x patch in this series breaks
> > probe of the dwc3 driver.
> > 
> > Turns out a number of these SoCs were using GIC interrupts for the
> > DP/DM_HS_PHY interrupts despite the fact that the driver tries to
> > reconfigure these as IRQ_TYPE_EDGE_FALLING (which the GIC does not
> > support) to detect disconnect events during suspend.
> > 
> > This is obviously broken and the proper fix is to replace the GIC
> > interrupts with the corresponding PDC interrupts. I believe Konrad is
> > digging out the magic numbers at this moment.
> > 
> > The following patches will need a follow-up fix:
> > 
> >>    ARM: dts: qcom: sdx55: fix USB wakeup interrupt types
> > 
> >>    arm64: dts: qcom: sc8180x: fix USB wakeup interrupt types
> >>    arm64: dts: qcom: sdm670: fix USB wakeup interrupt types
> >>    arm64: dts: qcom: sdm845: fix USB wakeup interrupt types
> >>    arm64: dts: qcom: sm6375: fix USB wakeup interrupt types
> >>    arm64: dts: qcom: sm8150: fix USB wakeup interrupt types

>   If it helps, I tried to dig up the PDC numbers for corresponding 
> GIC_SPI vectors:

Thanks, Krisha, that helps a lot.

I've sent two series (for arm and arm64) based on yours and Konrad's
input:

	https://lore.kernel.org/lkml/20231213173131.29436-1-johan+linaro@kernel.org/
	https://lore.kernel.org/lkml/20231213173403.29544-1-johan+linaro@kernel.org/

> SM8150:
> 
> eud_p0_dpse_int_mx	apps_pdc_irq_out[9]	SYS_apcsQgicSPI[489]
> eud_p0_dmse_int_mx    apps_pdc_irq_out[8]	SYS_apcsQgicSPI[488]
> qmp_usb3_lfps_rxterm_irq apps_pdc_irq_out[6]	SYS_apcsQgicSPI[486]
> usb31_power_event_irq	SYS_apcsQgicSPI[130]
> usb31_hs_phy_irq	SYS_apcsQgicSPI[131]
> 
> interrupts-extended = <&pdc 9 IRQ_TYPE_EDGE_RISING>,
> 			<&intc GIC_SPI 130 IRQ_TYPE_LEVEL_HIGH>,
> 			<&pdc 6 IRQ_TYPE_LEVEL_HIGH>,
> 			<&pdc 8 IRQ_TYPE_EDGE_RISING>;
> 
> interrupt-names = "dp_hs_phy_irq", "pwr_event_irq",
> 		"ss_phy_irq", "dm_hs_phy_irq";

Do you have the corresponding numbers also for the second controller on
SM8150? I inferred them from SDM845, but it would good to verify that.

And can someone dig out the corresponding SS PHY interrupt for sc8180x?

Johan

  reply	other threads:[~2023-12-13 17:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 16:43 [PATCH 00/11] ARM/arm64: dts: qcom: fix USB wakeup interrupt types Johan Hovold
2023-11-20 16:43 ` [PATCH 01/11] ARM: dts: qcom: sdx55: " Johan Hovold
2023-11-20 16:43 ` [PATCH 02/11] arm64: dts: qcom: sa8775p: " Johan Hovold
2023-11-20 17:26   ` Andrew Halaney
2023-11-20 16:43 ` [PATCH 03/11] arm64: dts: qcom: sc7180: " Johan Hovold
2023-11-20 16:43 ` [PATCH 04/11] arm64: dts: qcom: sc7280: fix usb_1 " Johan Hovold
2023-11-20 17:58   ` Krzysztof Kozlowski
2023-11-20 16:43 ` [PATCH 05/11] arm64: dts: qcom: sc7280: fix usb_2 " Johan Hovold
2023-11-20 16:43 ` [PATCH 06/11] arm64: dts: qcom: sc8180x: fix USB " Johan Hovold
2023-11-20 16:43 ` [PATCH 07/11] arm64: dts: qcom: sdm670: " Johan Hovold
2023-11-21  2:01   ` Richard Acayan
2023-11-20 16:43 ` [PATCH 08/11] arm64: dts: qcom: sdm845: " Johan Hovold
2023-11-20 16:43 ` [PATCH 09/11] arm64: dts: qcom: sm6375: " Johan Hovold
2023-11-20 16:43 ` [PATCH 10/11] arm64: dts: qcom: sm8150: " Johan Hovold
2023-11-23  2:16   ` Jack Pham
2023-11-20 16:43 ` [PATCH 11/11] arm64: dts: qcom: sm8550: " Johan Hovold
2023-11-20 16:53   ` Abel Vesa
2023-12-08 14:55 ` (subset) [PATCH 00/11] ARM/arm64: dts: qcom: " Bjorn Andersson
2023-12-11 16:39 ` Johan Hovold
2023-12-12  9:30   ` Krishna Kurapati PSSNV
2023-12-13 17:38     ` Johan Hovold [this message]
2023-12-13 18:39     ` Konrad Dybcio
2023-12-14  7:49       ` Johan Hovold

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=ZXnsFIl9i6Ix-woH@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=cros-qcom-dts-watchers@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_kriskura@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