[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHp75VdDu678oL9VU8ea=A89O5L-5pPwkp8SOuySw+bCmtsAxA@mail.gmail.com>
Date: Wed, 19 Feb 2020 13:28:05 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Alexandre Torgue <alexandre.torgue@...com>
Cc: Jack Pham <jackp@...eaurora.org>, Peter Chen <peter.chen@....com>,
Naresh Kamboju <naresh.kamboju@...aro.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"lkft-triage@...ts.linaro.org" <lkft-triage@...ts.linaro.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: msm_hsusb 78d9000.usb: failed to create device link to ci_hdrc.0.ulpi
On Wed, Feb 19, 2020 at 12:00 PM Alexandre Torgue
<alexandre.torgue@...com> wrote:
> On 2/19/20 10:23 AM, Andy Shevchenko wrote:
> > On Wed, Feb 19, 2020 at 4:46 AM Jack Pham <jackp@...eaurora.org> wrote:
> >>
> >> On Wed, Feb 19, 2020 at 01:38:22AM +0000, Peter Chen wrote:
> >>> On 20-02-17 14:02:57, Naresh Kamboju wrote:
> >>>> arm64 APQ 8016 SBC ( Dragonboard 410c) device running Linux next boot
> >>>> failed due to below error.
...
> >> Probably same cause as for this:
> >> https://bugzilla.kernel.org/show_bug.cgi?id=206435
> >
> > Yes, it's the same. I dunno why no fix yet available.
> >
>
> Kishon has posted a patch yesterday for device link issue in phy core.
Ah, good to know! (Seems it hasn't made Linux Next yet, though)
> Please see:
>
> https://lkml.org/lkml/2020/2/18/272
Hint: use lore.kernel.org instead, much better if one would like to
reply / apply / etc.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists