From: Andrew Lunn <andrew@lunn.ch>
To: Zefir Kurtisi <zefir.kurtisi@neratec.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] phy state machine: failsafe leave invalid RUNNING state
Date: Wed, 4 Jan 2017 17:16:15 +0100 [thread overview]
Message-ID: <20170104161615.GF5517@lunn.ch> (raw)
In-Reply-To: <8521b51f-04f7-aeef-f862-bb150257cfa4@neratec.com>
> The setup is as follows:
> mv88e6321:
> * ports 0+1 connected to fibre-optics transceivers at fixed 100 Mbps
> * port 4 is CPU port
> * custom phy driver (replacement for marvell.ko) only populated with
> * .config_init to
> * set fixed speed for ports 0+1 (when in FO mode)
> * run genphy_config_init() for all other modes (here: CPU port)
> * .config_aneg=genphy_config_aneg, .read_status=genphy_read_status
Kicking off a side discussion:
Why do a custom PHY driver? What cannot you do with the current DSA
code? I've got boards with two FO ports, and using fixed-phy is all i
need to make them work on a 6352.
Andrew
next prev parent reply other threads:[~2017-01-04 16:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 15:04 [PATCH] phy state machine: failsafe leave invalid RUNNING state Zefir Kurtisi
2017-01-04 15:13 ` Florian Fainelli
2017-01-04 15:27 ` Zefir Kurtisi
2017-01-04 15:30 ` Florian Fainelli
2017-01-04 16:10 ` Zefir Kurtisi
2017-01-04 16:16 ` Andrew Lunn [this message]
2017-01-04 16:24 ` [SIDE DISCUSSION] " Matthias May
2017-01-04 21:44 ` Florian Fainelli
2017-01-05 9:23 ` Zefir Kurtisi
2017-01-05 19:39 ` Florian Fainelli
2017-01-04 20:07 ` kbuild test robot
2017-01-04 20:23 ` kbuild test robot
2017-01-06 11:14 ` [PATCH v2] " Zefir Kurtisi
2017-01-08 23:16 ` David Miller
2017-01-09 1:24 ` Florian Fainelli
2017-01-09 20:38 ` 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=20170104161615.GF5517@lunn.ch \
--to=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=zefir.kurtisi@neratec.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 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).