Re: [RFC usb-next v2 1/2] usb: core: split usb_phy_roothub_{init,alloc}

2018-03-26 Thread Chunfeng Yun
On Mon, 2018-03-26 at 22:31 +0200, Martin Blumenstingl wrote: > Hi Chunfeng, > > On Mon, Mar 26, 2018 at 5:37 AM, Chunfeng Yun > wrote: > > On Sat, 2018-03-24 at 15:21 +0100, Martin Blumenstingl wrote: > >> Before this patch usb_phy_roothub_init served two purposes

Re: [RFC usb-next v2 1/2] usb: core: split usb_phy_roothub_{init,alloc}

2018-03-26 Thread Martin Blumenstingl
Hi Chunfeng, On Mon, Mar 26, 2018 at 5:37 AM, Chunfeng Yun wrote: > On Sat, 2018-03-24 at 15:21 +0100, Martin Blumenstingl wrote: >> Before this patch usb_phy_roothub_init served two purposes (from a >> caller's point of view - like hcd.c): >> - parsing the PHYs and

Re: [RFC usb-next v2 1/2] usb: core: split usb_phy_roothub_{init,alloc}

2018-03-26 Thread Roger Quadros
On 24/03/18 16:21, Martin Blumenstingl wrote: > Before this patch usb_phy_roothub_init served two purposes (from a > caller's point of view - like hcd.c): > - parsing the PHYs and allocating the list entries > - calling phy_init on each list entry > > While this worked so far it has one

Re: [RFC usb-next v2 1/2] usb: core: split usb_phy_roothub_{init,alloc}

2018-03-25 Thread Chunfeng Yun
On Sat, 2018-03-24 at 15:21 +0100, Martin Blumenstingl wrote: > Before this patch usb_phy_roothub_init served two purposes (from a > caller's point of view - like hcd.c): > - parsing the PHYs and allocating the list entries > - calling phy_init on each list entry > > While this worked so far it

[RFC usb-next v2 1/2] usb: core: split usb_phy_roothub_{init,alloc}

2018-03-24 Thread Martin Blumenstingl
Before this patch usb_phy_roothub_init served two purposes (from a caller's point of view - like hcd.c): - parsing the PHYs and allocating the list entries - calling phy_init on each list entry While this worked so far it has one disadvantage: if we need to call phy_init for each PHY instance