From: Steev Klimaszewski <steev@kali.org>
To: Sandeep Maheswaram <quic_c_sanm@quicinc.com>,
Pavan Kondeti <quic_pkondeti@quicinc.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felipe Balbi <balbi@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Doug Anderson <dianders@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>,
Mathias Nyman <mathias.nyman@intel.com>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_ppratap@quicinc.com
Subject: Re: [PATCH v10 6/6] usb: dwc3: qcom: Enable the interrupts during probe
Date: Thu, 17 Feb 2022 16:16:42 -0600 [thread overview]
Message-ID: <5bc3b4d9-1bbb-479a-64f4-768f47075ec0@kali.org> (raw)
In-Reply-To: <cad907b6-4434-45e7-bd70-b93c0035d90c@quicinc.com>
Hi Sandeep,
On 2/17/22 12:05 AM, Sandeep Maheswaram wrote:
>
> Hi Steev,
>
> On 2/16/2022 3:21 PM, Steev Klimaszewski wrote:
>> That does allow it to boot, however.... it breaks USB.
>>
>> [ 2.013325] genirq: Setting trigger mode 3 for irq 35 failed
>> (gic_set_type+0x0/0x1b0)
>> [ 2.014063] dwc3-qcom a6f8800.usb: dp_hs_phy_irq failed: -22
>> [ 2.014134] dwc3-qcom a6f8800.usb: failed to setup IRQs, err=-22
>> [ 2.014351] dwc3-qcom: probe of a6f8800.usb failed with error -22
>> [ 2.018496] genirq: Setting trigger mode 3 for irq 39 failed
>> (gic_set_type+0x0/0x1b0)
>> [ 2.019124] dwc3-qcom a8f8800.usb: dp_hs_phy_irq failed: -22
>> [ 2.019193] dwc3-qcom a8f8800.usb: failed to setup IRQs, err=-22
>> [ 2.019372] dwc3-qcom: probe of a8f8800.usb failed with error -22
>>
>> steev@limitless:~$ lsusb
>> steev@limitless:~$
>>
>>
>> -- steev
>>
> Can you try with only IRQ_TYPE_EDGE_RISING as you are using GIC
> interrupts where IRQ_TYPE_EDGE_FALLING may not be supported
>
> diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
> b/arch/arm64/boot/dts/qcom/sdm845.dtsi
> index 0d6286d..ee3b031 100644
> --- a/arch/arm64/boot/dts/qcom/sdm845.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sdm845.dtsi
> @@ -3796,8 +3796,8 @@
>
> interrupts = <GIC_SPI 131 IRQ_TYPE_LEVEL_HIGH>,
> <GIC_SPI 486 IRQ_TYPE_LEVEL_HIGH>,
> - <GIC_SPI 488 IRQ_TYPE_LEVEL_HIGH>,
> - <GIC_SPI 489 IRQ_TYPE_LEVEL_HIGH>;
> + <GIC_SPI 488 IRQ_TYPE_EDGE_RISING>,
> + <GIC_SPI 489 IRQ_TYPE_EDGE_RISING>;
> interrupt-names = "hs_phy_irq", "ss_phy_irq",
> "dm_hs_phy_irq",
> "dp_hs_phy_irq";
>
> @@ -3844,8 +3844,8 @@
>
> interrupts = <GIC_SPI 136 IRQ_TYPE_LEVEL_HIGH>,
> <GIC_SPI 487 IRQ_TYPE_LEVEL_HIGH>,
> - <GIC_SPI 490 IRQ_TYPE_LEVEL_HIGH>,
> - <GIC_SPI 491 IRQ_TYPE_LEVEL_HIGH>;
> + <GIC_SPI 490 IRQ_TYPE_EDGE_RISING>,
> + <GIC_SPI 491 IRQ_TYPE_EDGE_RISING>;
> interrupt-names = "hs_phy_irq", "ss_phy_irq",
> "dm_hs_phy_irq",
> "dp_hs_phy_irq";
> Regards
>
> Sandeep
>
With this change, and with either EDGE_RISING or EDGE_BOTH in the lenovo
yoga c630 dts, it does indeed boot. Leaving LEVEL_HIGH in the c630, it
does also boot, but there is a delay of about 30 seconds (I'm assuming
interrupt storm?) during the boot.
-- steev
prev parent reply other threads:[~2022-02-17 22:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 5:44 [PATCH v10 0/6] USB DWC3 host wake up support from system suspend Sandeep Maheswaram
2022-01-17 5:44 ` [PATCH v10 1/6] usb: host: xhci: plat: Add suspend quirk for dwc3 controller Sandeep Maheswaram
2022-01-26 12:47 ` Greg Kroah-Hartman
2022-01-17 5:44 ` [PATCH v10 2/6] usb: dwc3: core: Host wake up support from system suspend Sandeep Maheswaram
2022-01-18 8:57 ` Jun Li
2022-01-24 5:27 ` Sandeep Maheswaram
2022-01-17 5:44 ` [PATCH v10 3/6] usb: dwc3: qcom: Add helper functions to enable,disable wake irqs Sandeep Maheswaram
2022-01-17 5:44 ` [PATCH v10 4/6] usb: dwc3: qcom: Change the IRQ flag for DP/DM hs phy irq Sandeep Maheswaram
2022-01-17 5:44 ` [PATCH v10 5/6] usb: dwc3: qcom: Keep power domain on to retain controller status Sandeep Maheswaram
2022-01-17 5:44 ` [PATCH v10 6/6] usb: dwc3: qcom: Enable the interrupts during probe Sandeep Maheswaram
2022-01-18 6:12 ` Steev Klimaszewski
2022-01-18 6:30 ` Sandeep Maheswaram
2022-01-18 8:46 ` Steev Klimaszewski
2022-01-18 9:52 ` Pavan Kondeti
2022-01-20 5:22 ` Sandeep Maheswaram
2022-01-25 9:17 ` Sandeep Maheswaram
2022-01-28 8:36 ` Steev Klimaszewski
2022-01-28 9:00 ` Pavan Kondeti
2022-02-15 9:40 ` Sandeep Maheswaram
2022-02-16 3:22 ` Steev Klimaszewski
2022-02-16 6:27 ` Sandeep Maheswaram
2022-02-16 9:51 ` Steev Klimaszewski
[not found] ` <cad907b6-4434-45e7-bd70-b93c0035d90c@quicinc.com>
2022-02-17 22:16 ` Steev Klimaszewski [this message]
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=5bc3b4d9-1bbb-479a-64f4-768f47075ec0@kali.org \
--to=steev@kali.org \
--cc=balbi@kernel.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mka@chromium.org \
--cc=quic_c_sanm@quicinc.com \
--cc=quic_pkondeti@quicinc.com \
--cc=quic_ppratap@quicinc.com \
--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
all inboxes | Powered by JetHome®