Re: [PATCH net-next 1/2] net: davinci_mdio: don't request io address range

2015-03-11 Thread Murali Karicheri
Tony, On 02/27/2015 11:51 AM, Tony Lindgren wrote: * Murali Karicheri [150224 13:32]: From: Grygorii Strashko Historically Davinci MDIO driver was created with assumption that MDIO is standalone device, but for Keystone 2 it's a part of NETCP module and now NETCP driver requests IO range whi

Re: [PATCH net-next 1/2] net: davinci_mdio: don't request io address range

2015-02-27 Thread Tony Lindgren
* Murali Karicheri [150224 13:32]: > From: Grygorii Strashko > > Historically Davinci MDIO driver was created with assumption that > MDIO is standalone device, but for Keystone 2 it's a part > of NETCP module and now NETCP driver requests IO range which > includes MDIO IO range too. This causes

Re: [PATCH net-next 1/2] net: davinci_mdio: don't request io address range

2015-02-27 Thread Lad, Prabhakar
On Tue, Feb 24, 2015 at 9:27 PM, Murali Karicheri wrote: > From: Grygorii Strashko > > Historically Davinci MDIO driver was created with assumption that > MDIO is standalone device, but for Keystone 2 it's a part > of NETCP module and now NETCP driver requests IO range which > includes MDIO IO r

[PATCH net-next 1/2] net: davinci_mdio: don't request io address range

2015-02-24 Thread Murali Karicheri
From: Grygorii Strashko Historically Davinci MDIO driver was created with assumption that MDIO is standalone device, but for Keystone 2 it's a part of NETCP module and now NETCP driver requests IO range which includes MDIO IO range too. This causes Keystone 2 networking stack failure during the