From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: Yixun Lan <yixun.lan@amlogic.com>,
Jerome Brunet <jbrunet@baylibre.com>,
devicetree@vger.kernel.org, Carlo Caione <carlo@caione.org>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM64: dts: meson-axg: add RMII pins for ethernet controller
Date: Tue, 30 Jan 2018 16:00:06 -0800 [thread overview]
Message-ID: <7hvafic2yh.fsf@baylibre.com> (raw)
In-Reply-To: <593cbb66-7040-b27d-5109-702fb43dc18e@baylibre.com> (Neil Armstrong's message of "Thu, 11 Jan 2018 10:33:27 +0100")
Neil Armstrong <narmstrong@baylibre.com> writes:
> On 11/01/2018 10:11, Yixun Lan wrote:
>> Hi Jerome：
>>
>> On 01/11/18 16:37, Jerome Brunet wrote:
>>> On Thu, 2018-01-11 at 11:04 +0800, Yixun Lan wrote:
>>>> Comparing to RGMII interface, the RMII interface require few pins.
>>>> So it's worth describing them here.
>>>>
>>>> Signed-off-by: Yixun Lan <yixun.lan@amlogic.com>
>>>
>>> The only axg platform we have upstream is the s400 and is using rgmii.
>>> May I ask how this was tested ?
>>>
>> It's true that S400 using RGMII interface.
>>
>> but, we have customer using RTL8201FR-VB/VD which is a RMII PHY,
>>
>> This is actually tested with the 'eth_rmii_x_pins' group.
>>
>> Yixun
>>
>
> I pushed the same for GXBB,
>
> Acked-by: Neil Armstrong <narmstrong@baylibre.com>
Applied to v4.17/dt64 with Neil's ack.
Kevin
prev parent reply other threads:[~2018-01-31 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 3:04 [PATCH] ARM64: dts: meson-axg: add RMII pins for ethernet controller Yixun Lan
2018-01-11 8:37 ` Jerome Brunet
2018-01-11 9:11 ` Yixun Lan
2018-01-11 9:33 ` Neil Armstrong
2018-01-31 0:00 ` Kevin Hilman [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=7hvafic2yh.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=yixun.lan@amlogic.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