Re: [RESEND] phy: da8xx-usb: rename clock con_ids

2018-01-31 Thread Kishon Vijay Abraham I
On Thursday 25 January 2018 09:11 PM, Sekhar Nori wrote: > On Tuesday 23 January 2018 11:44 PM, David Lechner wrote: >> This renames the clock con_ids in the DA8XX USB PHY driver as well as >> the matching names in the mach clock registration code. >> >> This is in preparation for using device

Re: [RESEND] phy: da8xx-usb: rename clock con_ids

2018-01-31 Thread Kishon Vijay Abraham I
On Thursday 25 January 2018 09:11 PM, Sekhar Nori wrote: > On Tuesday 23 January 2018 11:44 PM, David Lechner wrote: >> This renames the clock con_ids in the DA8XX USB PHY driver as well as >> the matching names in the mach clock registration code. >> >> This is in preparation for using device

Re: [RESEND] phy: da8xx-usb: rename clock con_ids

2018-01-25 Thread Sekhar Nori
On Tuesday 23 January 2018 11:44 PM, David Lechner wrote: > This renames the clock con_ids in the DA8XX USB PHY driver as well as > the matching names in the mach clock registration code. > > This is in preparation for using device tree clocks where these names > will become part of the device

Re: [RESEND] phy: da8xx-usb: rename clock con_ids

2018-01-25 Thread Sekhar Nori
On Tuesday 23 January 2018 11:44 PM, David Lechner wrote: > This renames the clock con_ids in the DA8XX USB PHY driver as well as > the matching names in the mach clock registration code. > > This is in preparation for using device tree clocks where these names > will become part of the device

[RESEND] phy: da8xx-usb: rename clock con_ids

2018-01-23 Thread David Lechner
This renames the clock con_ids in the DA8XX USB PHY driver as well as the matching names in the mach clock registration code. This is in preparation for using device tree clocks where these names will become part of the device tree bindings. The new names more closely match the names used in the

[RESEND] phy: da8xx-usb: rename clock con_ids

2018-01-23 Thread David Lechner
This renames the clock con_ids in the DA8XX USB PHY driver as well as the matching names in the mach clock registration code. This is in preparation for using device tree clocks where these names will become part of the device tree bindings. The new names more closely match the names used in the