lkml.org 
[lkml]   [2022]   [Jun]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v1 1/1] phy: ti: tusb1210: Don't check for write errors when powering on
    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?

    --
    With Best Regards,
    Andy Shevchenko


    \
     
     \ /
      Last update: 2022-06-15 13:52    [W:3.345 / U:0.088 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site