[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5719CAE1.40801@ti.com>
Date: Fri, 22 Apr 2016 12:25:29 +0530
From: Mugunthan V N <mugunthanvnm@...com>
To: "David Rivshin (Allworx)" <drivshin.allworx@...il.com>,
<netdev@...r.kernel.org>, <linux-omap@...r.kernel.org>
CC: <linux-arm-kernel@...ts.infradead.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Grygorii Strashko <grygorii.strashko@...com>,
Andrew Goodbody <andrew.goodbody@...brionix.com>,
Markus Brunner <systemprogrammierung.brunner@...il.com>,
Nicolas Chauvet <kwizart@...il.com>
Subject: Re: [PATCH net v2 0/3] drivers: net: cpsw: phy-handle fixes
On Thursday 21 April 2016 11:20 PM, David Rivshin (Allworx) wrote:
> From: David Rivshin <drivshin@...worx.com>
>
> The first patch fixes a bug that makes dual_emac mode break if
> either slave uses the phy-handle property in the devicetree.
>
> The second patch fixes some cosmetic problems with error messages,
> and also makes the binding documentation more explicit.
>
> The third patch cleans up the fixed-link case to work like
> the now-fixed phy-handle case.
>
> I have tested on the following hardware configurations:
> - (EVMSK) dual emac, phy_id property in both slaves
> - (EVMSK) dual emac, phy-handle property in both slaves
> - (BeagleBoneBlack) single emac, phy_id property
> - (custom) single emac, fixed-link subnode
>
> Nicolas Chauvet reported testing on an HP t410 (dm8148).
>
> Markus Brunner reported testing v1 on the following [1]:
> - emac0 with phy_id and emac1 with fixed phy
> - emac0 with phy-handle and emac1 with fixed phy
> - emac0 with fixed phy and emac1 with fixed phy
>
>
Reviewed-by: Mugunthan V N <mugunthanvnm@...com>
Regards
Mugunthan V N
Powered by blists - more mailing lists