Re: [PATCHv2 1/3] phy: core: Add devm_of_phy_get_by_index to phy-core

2015-04-20 Thread Kishon Vijay Abraham I
Hi, On Tuesday 21 April 2015 01:49 AM, Arun Ramamurthy wrote: On 15-04-15 02:59 AM, Kishon Vijay Abraham I wrote: Hi, On Tuesday 14 April 2015 03:40 AM, Arun Ramamurthy wrote: Some generic drivers, such as ehci, may use multiple phys and for such drivers referencing phy(s) by name(s) does

Re: [PATCHv2 1/3] phy: core: Add devm_of_phy_get_by_index to phy-core

2015-04-20 Thread Arun Ramamurthy
On 15-04-15 02:59 AM, Kishon Vijay Abraham I wrote: Hi, On Tuesday 14 April 2015 03:40 AM, Arun Ramamurthy wrote: Some generic drivers, such as ehci, may use multiple phys and for such drivers referencing phy(s) by name(s) does not make sense. Instead of inventing new naming schemes and

Re: [PATCHv2 1/3] phy: core: Add devm_of_phy_get_by_index to phy-core

2015-04-20 Thread Kishon Vijay Abraham I
Hi, On Tuesday 21 April 2015 01:49 AM, Arun Ramamurthy wrote: On 15-04-15 02:59 AM, Kishon Vijay Abraham I wrote: Hi, On Tuesday 14 April 2015 03:40 AM, Arun Ramamurthy wrote: Some generic drivers, such as ehci, may use multiple phys and for such drivers referencing phy(s) by name(s) does

Re: [PATCHv2 1/3] phy: core: Add devm_of_phy_get_by_index to phy-core

2015-04-20 Thread Arun Ramamurthy
On 15-04-15 02:59 AM, Kishon Vijay Abraham I wrote: Hi, On Tuesday 14 April 2015 03:40 AM, Arun Ramamurthy wrote: Some generic drivers, such as ehci, may use multiple phys and for such drivers referencing phy(s) by name(s) does not make sense. Instead of inventing new naming schemes and

Re: [PATCHv2 1/3] phy: core: Add devm_of_phy_get_by_index to phy-core

2015-04-16 Thread Peter Chen
On Mon, Apr 13, 2015 at 03:10:45PM -0700, Arun Ramamurthy wrote: > Some generic drivers, such as ehci, may use multiple phys and for such > drivers referencing phy(s) by name(s) does not make sense. Instead of > inventing new naming schemes and using custom code to iterate through them, > such

Re: [PATCHv2 1/3] phy: core: Add devm_of_phy_get_by_index to phy-core

2015-04-16 Thread Peter Chen
On Mon, Apr 13, 2015 at 03:10:45PM -0700, Arun Ramamurthy wrote: Some generic drivers, such as ehci, may use multiple phys and for such drivers referencing phy(s) by name(s) does not make sense. Instead of inventing new naming schemes and using custom code to iterate through them, such drivers

Re: [PATCHv2 1/3] phy: core: Add devm_of_phy_get_by_index to phy-core

2015-04-15 Thread Kishon Vijay Abraham I
Hi, On Tuesday 14 April 2015 03:40 AM, Arun Ramamurthy wrote: Some generic drivers, such as ehci, may use multiple phys and for such drivers referencing phy(s) by name(s) does not make sense. Instead of inventing new naming schemes and using custom code to iterate through them, such drivers are

Re: [PATCHv2 1/3] phy: core: Add devm_of_phy_get_by_index to phy-core

2015-04-15 Thread Kishon Vijay Abraham I
Hi, On Tuesday 14 April 2015 03:40 AM, Arun Ramamurthy wrote: Some generic drivers, such as ehci, may use multiple phys and for such drivers referencing phy(s) by name(s) does not make sense. Instead of inventing new naming schemes and using custom code to iterate through them, such drivers are

[PATCHv2 1/3] phy: core: Add devm_of_phy_get_by_index to phy-core

2015-04-13 Thread Arun Ramamurthy
Some generic drivers, such as ehci, may use multiple phys and for such drivers referencing phy(s) by name(s) does not make sense. Instead of inventing new naming schemes and using custom code to iterate through them, such drivers are better of using nameless phy bindings and using this newly

[PATCHv2 1/3] phy: core: Add devm_of_phy_get_by_index to phy-core

2015-04-13 Thread Arun Ramamurthy
Some generic drivers, such as ehci, may use multiple phys and for such drivers referencing phy(s) by name(s) does not make sense. Instead of inventing new naming schemes and using custom code to iterate through them, such drivers are better of using nameless phy bindings and using this newly