From: Florian Fainelli <f.fainelli@gmail.com>
To: "Måns Rullgård" <mans@mansr.com>, Mason <slash.tmp@free.fr>
Cc: Zefir Kurtisi <zefir.kurtisi@neratec.com>,
netdev <netdev@vger.kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Thibaud Cornic <thibaud_cornic@sigmadesigns.com>
Subject: Re: Setting link down or up in software
Date: Thu, 19 Jan 2017 09:59:20 -0800 [thread overview]
Message-ID: <027dabb7-62fb-88bf-f51e-26fdc728d85f@gmail.com> (raw)
In-Reply-To: <yw1xbmv3j5ly.fsf@unicorn.mansr.com>
On 01/19/2017 09:56 AM, Måns Rullgård wrote:
> Mason <slash.tmp@free.fr> writes:
>
>> One thing I find confusing... If the 8035 could work with the generic
>> PHY driver, what's the point of the at803x.ko driver?
>
> Almost all Ethernet PHYs support the basic operation defined the by the
> standard. Many have additional non-standardised features that require a
> specific driver. Interrupts, for example.
Or special initial configuration wrt. (RG)MII modes, and runtime
configuration (EEE, link speeds, workarounds), obtaining useful counters
etc.
The generic PHY driver only deals with the standard MII registers (and
just a subset of it actually) while the PHY driver allows you to deal
with all the hardware specifics, the whole point behind having both
specialization and abstraction.
--
Florian
prev parent reply other threads:[~2017-01-19 18:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 13:05 Setting link down or up in software Mason
2017-01-12 15:16 ` Mason
2017-01-12 15:28 ` Andrew Lunn
2017-01-12 16:22 ` Mason
2017-01-12 16:27 ` Andrew Lunn
2017-01-12 18:45 ` Dan Williams
2017-01-13 9:20 ` Zefir Kurtisi
2017-01-13 15:17 ` Mason
2017-01-13 16:28 ` Zefir Kurtisi
2017-01-13 17:35 ` Mason
2017-01-18 10:29 ` Zefir Kurtisi
2017-01-19 15:40 ` Mason
2017-01-19 17:56 ` Måns Rullgård
2017-01-19 17:59 ` Florian Fainelli [this message]
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=027dabb7-62fb-88bf-f51e-26fdc728d85f@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=mans@mansr.com \
--cc=netdev@vger.kernel.org \
--cc=slash.tmp@free.fr \
--cc=thibaud_cornic@sigmadesigns.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.