From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Neil Armstrong <narmstrong@baylibre.com>,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Guenter Roeck <linux@roeck-us.net>,
Fabian Frederick <fabf@skynet.be>,
Pavel Nakonechny <pavel.nakonechny@skitlab.ru>,
Joe Perches <joe@perches.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Frode Isaksen <fisaksen@baylibre.com>
Subject: Re: [PATCH v2 1/6] net: dsa: Use delayed work instead of timer+work for polling
Date: Thu, 29 Oct 2015 10:52:34 -0400 [thread overview]
Message-ID: <20151029145234.GB21131@ketchup.mtl.sfl> (raw)
In-Reply-To: <20151029144012.GT2307@lunn.ch>
On Oct. Thursday 29 (44) 03:40 PM, Andrew Lunn wrote:
> > Thanks for the hint, I will test this, but while reviewing the datasheet,
> > the port 5 has no PHY, so must only be used as cpu port.
>
> Not necessarily. All that is needed is an external phy. Linux does not
> care what MDIO bus that phy hangs off. It could be the same MDIO bus
> as the switch, or some other MDIO bus. It is likely that port 5 is the
> CPU port, but it does not have to be.
Indeed in my setup with a single 88E6352, we will soon add an external
PHY there (or on port 6, doesn't matter) to make it a 6-port switch.
> > I also have another patchset which fixes 2 setup registers writes and
> > adds a shiny new mv88e6060.h based on mv88e6xxx.h.
>
> Great. I hope that will help determine if we can merge 6060 into 6xxx.
Is 6060 supported by the 6352 family? It doesn't share any mv88e6xxx
code...
Thanks,
-v
next prev parent reply other threads:[~2015-10-29 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 13:22 Neil Armstrong
2015-10-29 13:51 ` Andrew Lunn
2015-10-29 14:10 ` Neil Armstrong
2015-10-29 14:40 ` Andrew Lunn
2015-10-29 14:52 ` Vivien Didelot [this message]
2015-10-29 15:28 ` Andrew Lunn
2015-10-30 15:44 ` Neil Armstrong
2015-10-30 16:30 ` Andrew Lunn
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=20151029145234.GB21131@ketchup.mtl.sfl \
--to=vivien.didelot@savoirfairelinux.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=fabf@skynet.be \
--cc=fisaksen@baylibre.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=narmstrong@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=pavel.nakonechny@skitlab.ru \
/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
all inboxes | Powered by JetHome®