linux-kernel - RE: [PATCH v3] usb: chipidea: Grab the (legacy) USB PHY by phandle first

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <VI1PR04MB5327C5FCF2BCF404B78A2C6A8B7E0@VI1PR04MB5327.eurprd04.prod.outlook.com>
Date:   Thu, 21 Feb 2019 08:37:52 +0000
From:   Peter Chen <peter.chen@....com>
To:     Paul Kocialkowski <paul.kocialkowski@...tlin.com>,
        "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Thomas Petazzoni <thomas.petazzoni@...tlin.com>
Subject: RE: [PATCH v3] usb: chipidea: Grab the (legacy) USB PHY by phandle
 first

 
> > If there is a generic PHY node under USB controller, and there is a
> > USB PHY at other sides, both ci->phy and ci->usb_phy are valid, I
> > original thought it is the problem you met.
> 
> Right, this is not the problem we are having. The problem is that legacy USB PHYs
> are not grabbed from device-tree. Instead, they are currently matched with their
> type in the list of registered USB PHYs, making it impossible to use 2 distinct USB
> PHYs this way.
> 
> > Since you are trying to fix the legacy USB PHY grab issue, I hope you
> > could consider the generic PHY as well.
> 
> What do you have in mind about generic PHYs? Everything already works as
> expected with them.
> 
 
Current code w/o your patch, it is possible both ci->phy and ci->usb_phy are valid
if the USB PHY is not at the device tree, but generic PHY is at the device tree.
If you don't want to fix this issue with this patch, it is ok too. We could fix it later.

Peter