Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ferry Toth <fntoth@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Vinod Koul <vkoul@kernel.org>,
	Hans de Goede <hdegoede@redhat.com>,
	Stephan Gerhold <stephan@gerhold.net>,
	linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: [PATCH v1 1/1] phy: ti: tusb1210: Don't check for write errors when powering on
Date: Mon, 13 Jun 2022 23:44:15 +0200	[thread overview]
Message-ID: <8201ecf4-29e6-6c97-d3a4-c99904187b3b@gmail.com> (raw)
In-Reply-To: <77a486ae-06bb-7f1b-17ab-8d60ccfbdee6@gmail.com>



Op 13-06-2022 om 22:40 schreef Ferry Toth:
> Hi
> 
> Op 13-06-2022 om 18:08 schreef Andy Shevchenko:
>> 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
> with the patch this error continues to appear in the logs
>>     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
> these errors are gone
>> which effectively fails the probe of the USB controller.
> 
> and probe of dwc3 succeeds
> 
> Tested on Intel Edison (Merrifield)

Tested-by: Ferry Toth <fntoth@gmail.com>

>> Drop the check as it was before the culprit commit (see Fixes tag).
>>
>> Fixes: 09a3512681b3 ("phy: ti: tusb1210: Improve ulpi_read()/_write() 
>> error checking")
>> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>> ---
>>   drivers/phy/ti/phy-tusb1210.c | 5 +++--
>>   1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/phy/ti/phy-tusb1210.c 
>> b/drivers/phy/ti/phy-tusb1210.c
>> index c3ab4b69ea68..669c13d6e402 100644
>> --- a/drivers/phy/ti/phy-tusb1210.c
>> +++ b/drivers/phy/ti/phy-tusb1210.c
>> @@ -105,8 +105,9 @@ static int tusb1210_power_on(struct phy *phy)
>>       msleep(TUSB1210_RESET_TIME_MS);
>>       /* Restore the optional eye diagram optimization value */
>> -    return tusb1210_ulpi_write(tusb, TUSB1210_VENDOR_SPECIFIC2,
>> -                   tusb->vendor_specific2);
>> +    tusb1210_ulpi_write(tusb, TUSB1210_VENDOR_SPECIFIC2, 
>> tusb->vendor_specific2);
>> +
>> +    return 0;
>>   }
>>   static int tusb1210_power_off(struct phy *phy)

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

  reply	other threads:[~2022-06-13 21:44 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 [this message]
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

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=8201ecf4-29e6-6c97-d3a4-c99904187b3b@gmail.com \
    --to=fntoth@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --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