From: Andrew Lunn <andrew@lunn.ch>
To: Marco Hartmann <marco.hartmann@nxp.com>
Cc: Andy Duan <fugang.duan@nxp.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christian Herber <christian.herber@nxp.com>
Subject: Re: [PATCH net-next 0/1] net: fec: add C45 MDIO read/write support
Date: Tue, 20 Aug 2019 00:54:22 +0200 [thread overview]
Message-ID: <20190819225422.GD29991@lunn.ch> (raw)
In-Reply-To: <1566234659-7164-1-git-send-email-marco.hartmann@nxp.com>
On Mon, Aug 19, 2019 at 05:11:14PM +0000, Marco Hartmann wrote:
> As of yet, the Fast Ethernet Controller (FEC) driver only supports Clause 22
> conform MDIO transactions. IEEE 802.3ae Clause 45 defines a modified MDIO
> protocol that uses a two staged access model in order to increase the address
> space.
>
> This patch adds support for Clause 45 conform MDIO read and write operations to
> the FEC driver.
Hi Marco
Do all versions of the FEC hardware support C45? Or do we need to make
use of the quirk support in this driver to just enable it for some
revisions of FEC?
Thanks
Andrew
next prev parent reply other threads:[~2019-08-19 22:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 17:11 [PATCH net-next 0/1] net: fec: add C45 MDIO read/write support Marco Hartmann
2019-08-19 17:11 ` [PATCH net-next 1/1] " Marco Hartmann
2019-08-20 1:35 ` David Miller
2019-08-20 2:08 ` Andy Duan
2019-08-21 11:44 ` Marco Hartmann
2019-08-19 22:54 ` Andrew Lunn [this message]
2019-08-20 2:32 ` [EXT] Re: [PATCH net-next 0/1] net: " Andy Duan
2019-08-20 13:04 ` Andrew Lunn
2019-08-21 5:55 ` Andy Duan
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=20190819225422.GD29991@lunn.ch \
--to=andrew@lunn.ch \
--cc=christian.herber@nxp.com \
--cc=davem@davemloft.net \
--cc=fugang.duan@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.hartmann@nxp.com \
--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).