Re: [PATCH 0/3] fix ohci phy name

On Thu, Nov 3, 2016 at 1:00 PM, Sekhar Nori wrote: > On Thursday 03 November 2016 01:54 PM, Axel Haslam wrote: >> Hi Sekhar, David, >> >> It might make sense to have this patch series, >> squashed into a single patch, would you agree, >> or do you prefer it as is:

Re: [PATCH 0/3] fix ohci phy name

On Thursday 03 November 2016 01:54 PM, Axel Haslam wrote: > Hi Sekhar, David, > > It might make sense to have this patch series, > squashed into a single patch, would you agree, > or do you prefer it as is: one-per-subsystem? Patches in the current form are okay. Some coordination is required in

Re: [PATCH 0/3] fix ohci phy name

Hi Sekhar, David, It might make sense to have this patch series, squashed into a single patch, would you agree, or do you prefer it as is: one-per-subsystem? Regards Axel. On Wed, Nov 2, 2016 at 1:44 PM, Axel Haslam wrote: > The usb ohci clock match is not working because

[PATCH 0/3] fix ohci phy name

The usb ohci clock match is not working because the usb clock is registered as "ohci" instead of "ohci.0" But since there is only a single ohci instance, lets pass -1 to the platform data id parameter and avoid the extra ".0" matching. while we are fixing this, rename the driver to "ohci-da8xx"