[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1450830994-5450-1-git-send-email-drivshin.allworx@gmail.com>
Date: Tue, 22 Dec 2015 19:36:31 -0500
From: "David Rivshin (Allworx)" <drivshin.allworx@...il.com>
To: netdev@...r.kernel.org
Cc: linux-arm-kernel@...ts.infradead.org, linux-omap@...r.kernel.org,
devicetree@...r.kernel.org, David Miller <davem@...emloft.net>,
Heiko Schocher <hs@...x.de>,
Mugunthan V N <mugunthanvnm@...com>,
Markus Brunner <systemprogrammierung.brunner@...il.com>,
Pascal Speck <kernel@...ek.de>,
Daniel Trautmann <dtrautmann@...softec-sps.de>
Subject: [PATCH 0/3] drivers: net: cpsw: phy-handle fixes
From: David Rivshin <drivshin@...worx.com>
This series is based on the tip of the net tree.
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
- (BeagleBoneBlack) single emac, phy_id property
- (custom) single emac, fixed-link subnode
Note that I don't have a board which would uses a phy-handle property,
though I have used hacked devicetrees to exercise the code paths.
Testing by anyone who has real hardware using phy-handle or dual_emac
with fixed-link would be appreciated.
David Rivshin (3):
drivers: net: cpsw: fix parsing of phy-handle DT property in dual_emac
config
drivers: net: cpsw: fix error messages when using phy-handle DT
property
drivers: net: cpsw: use of_phy_connect() in fixed-link case
Documentation/devicetree/bindings/net/cpsw.txt | 4 +--
drivers/net/ethernet/ti/cpsw.c | 40 +++++++++++++-------------
drivers/net/ethernet/ti/cpsw.h | 1 +
3 files changed, 23 insertions(+), 22 deletions(-)
--
2.5.0
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists