From: Ferry Toth <ftoth@exalondelft.nl>
To: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Sean Anderson <sean.anderson@seco.com>,
Liu Shixin <liushixin2@huawei.com>, Ferry Toth <fntoth@gmail.com>,
Andrey Smirnov <andrew.smirnov@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Ferry Toth <ftoth@exalondelft.nl>
Subject: [PATCH v5 0/2] usb: dwc3: core: defer probe on ulpi_read_id timeout
Date: Mon, 5 Dec 2022 21:15:25 +0100 [thread overview]
Message-ID: <20221205201527.13525-1-ftoth@exalondelft.nl> (raw)
v5:
- Fix the tag block (Andy)
- Rephrasing, typo's (Andy, Thinh)
v4:
- Sent in correct version (Andy, Thinh)
- Add details on reproducing on Intel Merrifield (Thinh)
v3:
- Correct commit message (Greg)
- Add Fixes: and Cc: stable (Greg)
v2:
- Split into separate commits (Thinh)
- Only defer probe on -ETIMEDOUT (Thinh)
- Loose curly brackets (Heikki)
Ferry Toth (2):
usb: ulpi: defer ulpi_register on ulpi_read_id timeout
usb: dwc3: core: defer probe on ulpi_read_id timeout
drivers/usb/common/ulpi.c | 2 +-
drivers/usb/dwc3/core.c | 7 ++++++-
2 files changed, 7 insertions(+), 2 deletions(-)
--
2.37.2
next reply other threads:[~2022-12-05 20:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 20:15 Ferry Toth [this message]
2022-12-05 20:15 ` [PATCH v5 1/2] usb: ulpi: defer ulpi_register " Ferry Toth
2022-12-07 11:33 ` Heikki Krogerus
2022-12-20 19:43 ` Guenter Roeck
2022-12-21 10:07 ` Ferry Toth
2022-12-21 12:41 ` Guenter Roeck
2022-12-21 14:29 ` Ferry Toth
2022-12-21 17:30 ` Guenter Roeck
2022-12-21 18:23 ` Greg Kroah-Hartman
2022-12-21 18:38 ` Ferry Toth
2022-12-21 18:48 ` Greg Kroah-Hartman
2022-12-22 12:45 ` [PATCH v5 1/2] usb: ulpi: defer ulpi_register on ulpi_read_id timeout #forregzbot Thorsten Leemhuis
2022-12-05 20:15 ` [PATCH v5 2/2] usb: dwc3: core: defer probe on ulpi_read_id timeout Ferry Toth
2022-12-05 21:19 ` Thinh Nguyen
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=20221205201527.13525-1-ftoth@exalondelft.nl \
--to=ftoth@exalondelft.nl \
--cc=Thinh.Nguyen@synopsys.com \
--cc=andrew.smirnov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fntoth@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=liushixin2@huawei.com \
--cc=sean.anderson@seco.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®