netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
	ivan@de.ibm.com, f.fainelli@gmail.com, andrew@lunn.ch,
	robh+dt@kernel.org
Subject: Re: [PATCH v1.1] net: emac: add support for device-tree based PHY discovery and setup
Date: Mon, 27 Feb 2017 20:42:15 +0100	[thread overview]
Message-ID: <2567253.1QjLrx0r05@debian64> (raw)
In-Reply-To: <20170222.153735.1289514443979947868.davem@davemloft.net>

On Wednesday, February 22, 2017 3:37:35 PM CET David Miller wrote:
> From: Christian Lamparter <chunkeey@googlemail.com>
> Date: Mon, 20 Feb 2017 20:10:58 +0100
> 
> > This patch adds glue-code that allows the EMAC driver to interface
> > with the existing dt-supported PHYs in drivers/net/phy.
> > 
> > Because currently, the emac driver maintains a small library of
> > supported phys for in a private phy.c file located in the drivers
> > directory.
> > 
> > The support is limited to mostly single ethernet transceiver like the:
> > CIS8201, BCM5248, ET1011C, Marvell 88E1111 and 88E1112, AR8035.
> > 
> > However, routers like the Netgear WNDR4700 and Cisco Meraki MX60(W)
> > have a 5-port switch (AR8327N) attached to the EMAC. The switch chip
> > is supported by the qca8k mdio driver, which uses the generic phy
> > library. Another reason is that PHYLIB also supports the BCM54610,
> > which was used for the Western Digital My Book Live.
> > 
> > This will now also make EMAC select PHYLIB.
> > 
> > Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
> 
> Applied, thanks.
> 
Thanks David.

I noticed that the DT Documentation patch:
"[v1,1/2] dt: emac: document device-tree based phy discovery and setup"
is still pending with "Changes Requested":
<https://patchwork.ozlabs.org/patch/729658/>

I think this is because of Florian's comment on patch:
"[v1,2/2] net: emac: add support for device-tree based PHY discovery and setup"
If so, can you please queue this documentation update patch for -next?
(I haven't received any comments or complains. If necessary, I can also
resent it.)

Thanks,
Christian

  reply	other threads:[~2017-02-27 19:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-19 21:22 [PATCH v1 1/2] dt: emac: document device-tree based phy discovery and setup Christian Lamparter
     [not found] ` <8f94c394faf5665ae693f41832f2446dfc7c989e.1487539319.git.chunkeey-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-02-19 21:22   ` [PATCH v1 2/2] net: emac: add support for device-tree based PHY " Christian Lamparter
2017-02-20  5:13     ` Florian Fainelli
     [not found]       ` <2109609d-c6a7-5c6f-d6aa-657107765778-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-20 19:10         ` [PATCH v1.1] " Christian Lamparter
     [not found]           ` <d32546b59c67456c77d003af1df51862d2f8c5de.1487617501.git.chunkeey-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-02-22 20:37             ` David Miller
2017-02-27 19:42               ` Christian Lamparter [this message]
2017-02-27 19:54                 ` David Miller
     [not found]                   ` <20170227.145447.1005420963599745103.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-02-27 20:11                     ` [PATCH v1.1] dt: emac: document device-tree based phy " Christian Lamparter
     [not found]                       ` <8f94c394faf5665ae693f41832f2446dfc7c989e.1488226061.git.chunkeey-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-02-27 20:25                         ` Florian Fainelli
2017-02-27 20:41                           ` [PATCH v1.2] " Christian Lamparter
2017-02-27 20:44                             ` Florian Fainelli
2017-02-27 20:54                               ` [PATCH v2] " Christian Lamparter
2017-03-07 20:15                                 ` 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=2567253.1QjLrx0r05@debian64 \
    --to=chunkeey@googlemail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=ivan@de.ibm.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).