From: Vinod Koul <vkoul@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Stephan Gerhold <stephan@gerhold.net>,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
Kishon Vijay Abraham I <kishon@ti.com>,
Ferry Toth <ftoth@exalondelft.nl>
Subject: Re: [PATCH v1 1/1] phy: ti: tusb1210: Don't check for write errors when powering on
Date: Thu, 16 Jun 2022 17:42:10 -0700 [thread overview]
Message-ID: <YqvN4nMvVNq7fW3V@matsya> (raw)
In-Reply-To: <20220613160848.82746-1-andriy.shevchenko@linux.intel.com>
On 13-06-22, 19:08, Andy Shevchenko wrote:
> On some platforms, like Intel Merrifield, the writing values during power on
> may timeout:
>
> tusb1210 dwc3.0.auto.ulpi: error -110 writing val 0x41 to reg 0x80
> phy phy-dwc3.0.auto.ulpi.0: phy poweron failed --> -110
> dwc3 dwc3.0.auto: error -ETIMEDOUT: failed to initialize core
> dwc3: probe of dwc3.0.auto failed with error -110
>
> which effectively fails the probe of the USB controller.
> Drop the check as it was before the culprit commit (see Fixes tag).
Applied, thanks
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2022-06-17 0:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 16:08 [PATCH v1 1/1] phy: ti: tusb1210: Don't check for write errors when powering on Andy Shevchenko
2022-06-13 20:40 ` Ferry Toth
2022-06-13 21:44 ` Ferry Toth
2022-06-14 11:23 ` Hans de Goede
2022-06-14 13:01 ` Andy Shevchenko
2022-06-14 15:49 ` Hans de Goede
2022-06-15 11:51 ` Andy Shevchenko
2022-06-15 16:11 ` Hans de Goede
2022-06-17 0:42 ` Vinod Koul [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=YqvN4nMvVNq7fW3V@matsya \
--to=vkoul@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ftoth@exalondelft.nl \
--cc=hdegoede@redhat.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=stephan@gerhold.net \
/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