LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Dan Murphy <dmurphy@ti.com>
Cc: f.fainelli@gmail.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: phy: DP83811: Add support for the phy
Date: Tue, 8 May 2018 18:49:44 +0200	[thread overview]
Message-ID: <20180508164944.GE2888@lunn.ch> (raw)
In-Reply-To: <1b6877db-61cf-101a-054e-9c1fbe95a813@ti.com>

On Tue, May 08, 2018 at 10:56:55AM -0500, Dan Murphy wrote:
> All
> 
> On 05/08/2018 09:11 AM, Dan Murphy wrote:
> > Add support for the DP83811 phy by extending
> > the DP83822 driver to recognize the PHY IDs.
> > 
> > The DP83811 supports both rgmii and sgmii interfaces.
> > There are 2 part numbers for this the DP83811R does not
> > reliably support the SGMII interface but the DP83811S 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
> > 
> 
> I am withdrawing this patch for comment.
> Some of the future features have varying register definitions between the DP83811
> and DP83822

Hi Dan

It might be worth talking to the ASIC engineers and the
test/qualification engineers. There are sometime undocumented
registers for testing. You might be able to identify the exact device
from these registers.

     Andrew

  reply	other threads:[~2018-05-08 16:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 14:11 [PATCH] net: phy: DP83811: Add support for the phy Dan Murphy
2018-05-08 15:56 ` Dan Murphy
2018-05-08 16:49   ` Andrew Lunn [this message]
2018-05-08 17:13     ` Dan Murphy
2018-05-08 17:14       ` Florian Fainelli
2018-05-08 17:21         ` Dan Murphy

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=20180508164944.GE2888@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=dmurphy@ti.com \
    --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;
as well as URLs for NNTP newsgroup(s).