From: Bo Shen <voice.shen@atmel.com>
To: Boris BREZILLON <boris.brezillon@free-electrons.com>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Andrew Victor <linux@maxim.org.za>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] ARM: at91: remove phy fixup for sama5d3xek boards
Date: Thu, 10 Jul 2014 10:24:06 +0800 [thread overview]
Message-ID: <53BDF946.7060404@atmel.com> (raw)
In-Reply-To: <20140709183442.14b8aef8@bbrezillon>
Hi Boris,
On 07/10/2014 12:34 AM, Boris BREZILLON wrote:
> Hello Bo,
>
> I know you're quite busy, but if you have some time could you test this
> series on both CPU Modules (Embest and Ronetix): I only own the Embest
> one.
>
> Best Regards,
>
> Boris
>
> On Thu, 26 Jun 2014 12:13:33 +0200
> Boris BREZILLON <boris.brezillon@free-electrons.com> wrote:
>
>> Hello,
>>
>> This patch removes a board specific hook for sama5d3xek boards from the
>> sama5d3 generic DT board file.
>>
>> This hook (which register a phy fixup configuring board specific delays
>> in the ksz9021 ethernet phy) is now replaced by the appropriate DT
>> properties definitions in the sama5d3xcm.dtsi file.
>>
>> Best Regards,
>>
>> Boris
>>
>> Changes since v1:
>> - fix txc-skew-ps and rxc-skew-ps delays
>> - remove phy address info to handle Ronetix and Embest HW designs
>>
>> Boris BREZILLON (2):
>> ARM: at91/dt: describe rgmii ethernet phy connected to sama5d3xek
>> boards
>> ARM: at91: remove phy fixup for sama5d3xek boards
>>
>> arch/arm/boot/dts/sama5d3xcm.dtsi | 15 +++++++++++++++
>> arch/arm/mach-at91/board-dt-sama5.c | 22 ----------------------
>> 2 files changed, 15 insertions(+), 22 deletions(-)
>>
For this series, test OK on sama5d33ek (Ronetix) and sama5d34ek (Embest).
Tested-by: Bo Shen <voice.shen@atmel.com>
Best Regards,
Bo Shen
prev parent reply other threads:[~2014-07-10 2:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 10:13 [PATCH v2 0/2] ARM: at91: remove phy fixup for sama5d3xek boards Boris BREZILLON
2014-06-26 10:13 ` [PATCH v2 1/2] ARM: at91/dt: describe rgmii ethernet phy connected to " Boris BREZILLON
2014-06-26 18:15 ` Florian Fainelli
2014-06-26 20:01 ` Boris BREZILLON
2014-06-27 7:52 ` Nicolas Ferre
[not found] ` <20140710110720.03f437eb@bbrezillon>
2014-07-10 15:35 ` Florian Fainelli
2014-07-10 17:19 ` Boris BREZILLON
2014-07-10 17:46 ` Florian Fainelli
[not found] ` <CAGVrzcawPiJgQF-=18ZvFGr3LhZgS1ZSZMYA3i5x874S6=jcXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-10 19:32 ` Boris BREZILLON
2014-06-26 10:13 ` [PATCH v2 2/2] ARM: at91: remove phy fixup for " Boris BREZILLON
2014-07-01 22:38 ` [PATCH v2 0/2] " David Miller
2014-07-02 11:48 ` Boris BREZILLON
2014-07-09 16:34 ` Boris BREZILLON
2014-07-10 2:24 ` Bo Shen [this message]
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=53BDF946.7060404@atmel.com \
--to=voice.shen@atmel.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.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;
as well as URLs for NNTP newsgroup(s).