diff options
| author |   David S. Miller <davem@davemloft.net> | 2015-04-03 15:08:20 -0400 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2015-04-03 15:08:20 -0400 |
| commit | b98d8075e65c9cb688e73b941d873986e7bbf7ae (patch) | |
| tree | 11065a9cf7570f455b747eab454dfc9b48916175 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | ebpf: add skb->priority to offset map for usage in {cls, act}_bpf (diff) | |
| parent | mvneta: implement SGMII-based in-band link state signaling (diff) | |
| download | wireguard-linux-b98d8075e65c9cb688e73b941d873986e7bbf7ae.tar.xz wireguard-linux-b98d8075e65c9cb688e73b941d873986e7bbf7ae.zip | |
Merge branch 'mvneta-sgmii'
Stas Sergeev says:
====================
mvneta: SGMII-based in-band link state signaling
Currently the fixed-link DT binding is pre-configured and
cannot be changed in run-time. This means the cable unplug
events are not being detected, and the link parameters can't
be negotiated.
The following patches are needed when mvneta is used
in fixed-link mode (without MDIO).
They add an API to fixed_phy that allows to update
status, and use that API in the mvneta driver when parsing
the SGMII in-band status.
There is also another implementation that doesn't add any API
and does everything in mvneta driver locally:
https://lkml.org/lkml/2015/3/31/327
I'll let people decide which approach is better.
No strong opinion on my side.
====================
Signed-off-by: Stas Sergeev <stsp@users.sourceforge.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions