From: Dan Murphy <dmurphy@ti.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: <f.fainelli@gmail.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] net: phy: DP83TC811: Introduce support for the DP83TC811 phy
Date: Fri, 11 May 2018 13:51:28 -0500 [thread overview]
Message-ID: <56ca63ce-d609-5bb7-f38c-17d875496bd5@ti.com> (raw)
In-Reply-To: <20180511183006.GB12738@lunn.ch>
Andrew
On 05/11/2018 01:30 PM, Andrew Lunn wrote:
> On Fri, May 11, 2018 at 01:08:19PM -0500, Dan Murphy wrote:
>> Add support for the DP83811 phy.
>>
>> The DP83811 supports both rgmii and sgmii interfaces.
>> There are 2 part numbers for this the DP83TC811R does not
>> reliably support the SGMII interface but the DP83TC811S will.
>>
>> There is not a way to differentiate these parts from the
>> hardware or register set. So this is controlled via the DT
>> to indicate which phy mode is required. Or the part can be
>> strapped to a certain interface.
>>
>> Data sheet can be found here:
>> http://www.ti.com/product/DP83TC811S-Q1/description
>> http://www.ti.com/product/DP83TC811R-Q1/description
>>
>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>
> Hi Dan
>
> It is normal to add any Reviewed-by, or Tested-by: tags you received,
> so long as you don't make major changes.
>
Thanks for the reminder.
I usually add them if I get them explicitly stated in the review.
I have not seen any Reviewed-by or Tested-by tags in any of the replies for the
patch. But I may have missed it.
Dan
> Andrew
>
--
------------------
Dan Murphy
next prev parent reply other threads:[~2018-05-11 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 18:08 Dan Murphy
2018-05-11 18:30 ` Andrew Lunn
2018-05-11 18:51 ` Dan Murphy [this message]
2018-05-11 19:10 ` Andrew Lunn
2018-05-11 19:15 ` David Miller
2018-05-11 19:12 ` Florian Fainelli
2018-05-11 20:36 ` David Miller
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=56ca63ce-d609-5bb7-f38c-17d875496bd5@ti.com \
--to=dmurphy@ti.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®