From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Vinod Koul <vkoul@kernel.org>,
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: Wed, 15 Jun 2022 18:11:18 +0200 [thread overview]
Message-ID: <402d2059-d0ab-2229-870c-f511cd6f29ee@redhat.com> (raw)
In-Reply-To: <YqnHpXvZJEfhX21/@smile.fi.intel.com>
Hi,
On 6/15/22 13:51, Andy Shevchenko wrote:
> On Tue, Jun 14, 2022 at 05:49:22PM +0200, Hans de Goede wrote:
>> On 6/14/22 15:01, Andy Shevchenko wrote:
>>> On Tue, Jun 14, 2022 at 01:23:21PM +0200, Hans de Goede wrote:
>>>> On 6/13/22 18:08, Andy Shevchenko wrote:
>
> ...
>
>>> [ 35.126397] tusb1210 dwc3.0.auto.ulpi: GPIO lookup for consumer reset
>>> [ 35.126418] tusb1210 dwc3.0.auto.ulpi: using ACPI for GPIO lookup
>>> [ 35.126455] tusb1210 dwc3.0.auto.ulpi: using lookup tables for GPIO lookup
>>> [ 35.126465] tusb1210 dwc3.0.auto.ulpi: No GPIO consumer reset found
>>> [ 35.126476] tusb1210 dwc3.0.auto.ulpi: GPIO lookup for consumer cs
>>> [ 35.126485] tusb1210 dwc3.0.auto.ulpi: using ACPI for GPIO lookup
>>> [ 35.126538] tusb1210 dwc3.0.auto.ulpi: using lookup tables for GPIO lookup
>>> [ 35.126548] tusb1210 dwc3.0.auto.ulpi: No GPIO consumer cs found
>>> [ 40.534107] tusb1210 dwc3.0.auto.ulpi: error -110 writing val 0x41 to reg 0x80
>>>
>>> (I put 5000 ms there to be sure)
>>>
>>>> I'm fine with going with this workaround patch to fix things.
>>
>> Ok, so I guess we should just apply this workaround patch to make
>> the error non fatal. Still would be good to dig a little deeper one
>> of these days and see what is going on here...
>
> Can you give a formal tag?
Sure:
Acked-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2022-06-15 16:11 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 [this message]
2022-06-17 0:42 ` Vinod Koul
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=402d2059-d0ab-2229-870c-f511cd6f29ee@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ftoth@exalondelft.nl \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=stephan@gerhold.net \
--cc=vkoul@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