From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Jeffery <andrew@aj.id.au>, netdev <netdev@vger.kernel.org>
Cc: David Miller <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
mark.rutland@arm.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH 1/3] dt-bindings: net: ftgmac100: Document AST2600 compatible
Date: Thu, 10 Oct 2019 11:10:44 +1100 [thread overview]
Message-ID: <991382b92be6b78e596b089d2c3677358afa52fc.camel@kernel.crashing.org> (raw)
In-Reply-To: <4998960d-6125-4402-9905-869653a84e52@www.fastmail.com>
On Wed, 2019-10-09 at 15:25 +1030, Andrew Jeffery wrote:
>
> On Wed, 9 Oct 2019, at 15:19, Andrew Jeffery wrote:
> >
> >
> > On Wed, 9 Oct 2019, at 15:08, Benjamin Herrenschmidt wrote:
> > > On Tue, 2019-10-08 at 22:21 +1030, Andrew Jeffery wrote:
> > > > The AST2600 contains an FTGMAC100-compatible MAC, although it
> > > > no-
> > > > longer
> > > > contains an MDIO controller.
> > >
> > > How do you talk to the PHY then ?
> >
> > There are still MDIO controllers, they're just not in the MAC IP on
> > the 2600.
>
> Sorry, on reflection that description is a little ambiguous in its
> use of 'it'. I'll
> fix that in v2 as well. Does this read better?
>
> "The AST2600 contains an FTGMAC100-compatible MAC, although the MAC
> no-longer contains an MDIO controller."
That's fine. Or to be pendantic, say the MDIO controller has been moved
of the MAC unit into its own separate block or something along those
lines so people like me don't get anxious :)
Cheers,
Ben.
next prev parent reply other threads:[~2019-10-10 0:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 11:51 [PATCH 0/3] net: ftgmac100: Ungate RCLK for RMII on ASPEED MACs Andrew Jeffery
2019-10-08 11:51 ` [PATCH 1/3] dt-bindings: net: ftgmac100: Document AST2600 compatible Andrew Jeffery
2019-10-08 12:40 ` Joel Stanley
2019-10-09 4:38 ` Benjamin Herrenschmidt
2019-10-09 4:49 ` Andrew Jeffery
2019-10-09 4:55 ` Andrew Jeffery
2019-10-10 0:10 ` Benjamin Herrenschmidt [this message]
2019-10-08 11:51 ` [PATCH 2/3] dt-bindings: net: ftgmac100: Describe clock properties Andrew Jeffery
2019-10-08 12:42 ` Joel Stanley
2019-10-09 0:19 ` Andrew Jeffery
2019-10-08 11:51 ` [PATCH 3/3] net: ftgmac100: Ungate RCLK for RMII on ASPEED MACs Andrew Jeffery
2019-10-08 12:44 ` Joel Stanley
2019-10-09 0:38 ` [PATCH 0/3] " Florian Fainelli
2019-10-09 1:11 ` Joel Stanley
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=991382b92be6b78e596b089d2c3677358afa52fc.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=andrew@aj.id.au \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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).