From: "Köry Maincent" <kory.maincent@bootlin.com>
To: Jisheng Zhang <jszhang@kernel.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lu jicong <jiconglu58@gmail.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH] usb: dwc3: don't reset device side if dwc3 was configured as host-only
Date: Thu, 16 Nov 2023 17:59:59 +0100 [thread overview]
Message-ID: <20231116175959.71f5d060@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <20231116174206.1a823aa3@kmaincent-XPS-13-7390>
On Thu, 16 Nov 2023 17:42:06 +0100
Köry Maincent <kory.maincent@bootlin.com> wrote:
> Hello,
>
> Similar issue with ZynqMP board related to that patch:
>
> xilinx-psgtr fd400000.phy: lane 3 (type 1, protocol 3): PLL lock timeout
> phy phy-fd400000.phy.3: phy poweron failed --> -110
> dwc3 fe300000.usb: error -ETIMEDOUT: failed to initialize core
>
> With CONFIG_USB_DWC3_DUAL_ROLE and dr_mode = "host";
>
> It may not be the correct fix.
Just figured out there was a patch (357191036889 usb: dwc3: Soft reset phy on
probe for host) from Thinh aimed to fix it but the issue is still here on
ZynqMP.
Regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-11-16 17:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 16:42 Köry Maincent
2023-11-16 16:59 ` Köry Maincent [this message]
2023-11-17 1:40 ` Thinh Nguyen
2023-11-17 1:55 ` Thinh Nguyen
2023-11-17 9:22 ` Köry Maincent
2023-11-21 9:49 ` Köry Maincent
2023-12-01 9:09 ` Köry Maincent
2023-12-02 0:26 ` Thinh Nguyen
2023-12-05 1:27 ` Thinh Nguyen
2023-12-05 13:56 ` Jisheng Zhang
2023-12-05 14:19 ` Köry Maincent
-- strict thread matches above, loose matches on Subject: below --
2023-06-27 16:20 Jisheng Zhang
2023-06-30 22:23 ` Thinh Nguyen
2023-09-30 7:43 ` Lu jicong
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=20231116175959.71f5d060@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=20231116174206.1a823aa3@kmaincent-XPS-13-7390 \
--cc=Thinh.Nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiconglu58@gmail.com \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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®