From: Mugunthan V N <mugunthanvnm@ti.com>
To: "David Rivshin (Allworx)" <drivshin.allworx@gmail.com>,
<netdev@vger.kernel.org>, <linux-omap@vger.kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Andrew Goodbody <andrew.goodbody@cambrionix.com>,
Markus Brunner <systemprogrammierung.brunner@gmail.com>,
Nicolas Chauvet <kwizart@gmail.com>
Subject: Re: [PATCH net v2 0/3] drivers: net: cpsw: phy-handle fixes
Date: Fri, 22 Apr 2016 12:25:29 +0530 [thread overview]
Message-ID: <5719CAE1.40801@ti.com> (raw)
In-Reply-To: <1461261035-5578-1-git-send-email-drivshin.allworx@gmail.com>
On Thursday 21 April 2016 11:20 PM, David Rivshin (Allworx) wrote:
> From: David Rivshin <drivshin@allworx.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@ti.com>
Regards
Mugunthan V N
next prev parent reply other threads:[~2016-04-22 6:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 17:50 [PATCH net v2 0/3] drivers: net: cpsw: phy-handle fixes David Rivshin (Allworx)
2016-04-21 18:19 ` [PATCH net v2 1/3] drivers: net: cpsw: fix parsing of phy-handle DT property in dual_emac config David Rivshin (Allworx)
2016-04-22 13:03 ` Grygorii Strashko
2016-04-25 19:14 ` Grygorii Strashko
2016-04-21 18:26 ` [PATCH net v2 2/3] drivers: net: cpsw: fix error messages when using phy-handle DT property David Rivshin (Allworx)
2016-04-22 13:03 ` Grygorii Strashko
2016-04-22 15:45 ` David Rivshin (Allworx)
2016-04-25 19:12 ` Grygorii Strashko
2016-04-25 21:55 ` David Rivshin (Allworx)
2016-04-26 7:50 ` Grygorii Strashko
2016-04-21 18:41 ` [PATCH net v2 3/3] drivers: net: cpsw: use of_phy_connect() in fixed-link case David Rivshin (Allworx)
2016-04-22 13:34 ` Grygorii Strashko
2016-04-22 6:55 ` Mugunthan V N [this message]
2016-04-22 13:44 ` [PATCH net v2 0/3] drivers: net: cpsw: phy-handle fixes Andrew Goodbody
[not found] <1461209082-25609-1-git-send-email-drivshin.allworx@gmail.com>
2016-04-21 4:20 ` David Rivshin (Allworx)
-- strict thread matches above, loose matches on Subject: below --
2016-04-21 3:51 David Rivshin (Allworx)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5719CAE1.40801@ti.com \
--to=mugunthanvnm@ti.com \
--cc=andrew.goodbody@cambrionix.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=drivshin.allworx@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=kwizart@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=systemprogrammierung.brunner@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox