Re: [PATCH v2 1/2] usb: phy: Introduce one extcon device into usb phy

Hi, On 29 March 2017 at 06:56, NeilBrown wrote: > On Thu, Mar 23 2017, Baolin Wang wrote: > >> Usually usb phy need register one extcon device to get the connection >> notifications. It will remove some duplicate code if the extcon device >> is registered using common code instead of each phy dri

Re: [PATCH v2 1/2] usb: phy: Introduce one extcon device into usb phy

Hi, On 28 March 2017 at 21:40, Felipe Balbi wrote: > > Hi, > > Baolin Wang writes: >> Usually usb phy need register one extcon device to get the connection >> notifications. It will remove some duplicate code if the extcon device >> is registered using common code instead of each phy driver havi

Re: [PATCH v2 1/2] usb: phy: Introduce one extcon device into usb phy

On Thu, Mar 23 2017, Baolin Wang wrote: > Usually usb phy need register one extcon device to get the connection > notifications. It will remove some duplicate code if the extcon device > is registered using common code instead of each phy driver having its > own related extcon APIs. So we add one

Re: [PATCH v2 1/2] usb: phy: Introduce one extcon device into usb phy

Hi, Baolin Wang writes: > Usually usb phy need register one extcon device to get the connection > notifications. It will remove some duplicate code if the extcon device > is registered using common code instead of each phy driver having its > own related extcon APIs. So we add one pointer of ext