All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Gregory Clement <gregory.clement@free-electrons.com>
Cc: netdev <netdev@vger.kernel.org>,
	Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
	Gregory Clement <gregory.clement@free-electrons.com>
Subject: Re: [PATCH net-next 0/2] Work around missing PHY prodcut ID in mv88e6390
Date: Wed, 25 Jan 2017 02:59:05 +0100	[thread overview]
Message-ID: <20170125015905.GA24034@lunn.ch> (raw)
In-Reply-To: <1485309314-23942-1-git-send-email-andrew@lunn.ch>

On Wed, Jan 25, 2017 at 02:55:12AM +0100, Andrew Lunn wrote:
> The internal PHYs of the MV88E6390 have a Marvell OUI, but the product
> ID is zero. Work around this by trapping reads to the ID, and if it is
> zero, return the MV88E6390 family ID.

Hi Gregory

This should just work for your switch as well, the PHY will get the ID
6390. I expect the PHY is compatible with the 6390 PHYs, so i think we
can just leave it as it is. We can change it later, if we do have
compatibility problems.

	      Andrew

  parent reply	other threads:[~2017-01-25  1:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25  1:55 [PATCH net-next 0/2] Work around missing PHY prodcut ID in mv88e6390 Andrew Lunn
2017-01-25  1:55 ` [PATCH net-next 1/2] net: dsa: mv88e6xxx: Workaround missing PHY ID on mv88e6390 Andrew Lunn
2017-01-25 17:27   ` Gregory CLEMENT
2017-01-25 17:45     ` Vivien Didelot
2017-01-25 18:00       ` Andrew Lunn
2017-01-25 18:03       ` Vivien Didelot
2017-01-25 19:30         ` Andrew Lunn
2017-01-25 19:37           ` Vivien Didelot
2017-01-25 17:51     ` Florian Fainelli
2017-01-25 17:52     ` Andrew Lunn
2017-01-26 12:06   ` Gregory CLEMENT
2017-01-25  1:55 ` [PATCH net-next 2/2] net: phy: Marvell: Add mv88e6390 internal PHY Andrew Lunn
2017-01-26 12:01   ` Gregory CLEMENT
2017-01-26 14:16     ` Andrew Lunn
2017-01-25  1:59 ` Andrew Lunn [this message]
2017-01-25 18:25 ` [PATCH net-next 0/2] Work around missing PHY prodcut ID in mv88e6390 David Miller
2017-01-27 17:12   ` Gregory CLEMENT

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=20170125015905.GA24034@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=gregory.clement@free-electrons.com \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@savoirfairelinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.