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
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
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
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
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
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
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
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
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
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
10 matches
Mail list logo