<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/linux.git/include/dt-bindings/net, branch v4.20</title>
<subtitle>Linux Kernel
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v4.20</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v4.20'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/'/>
<updated>2018-10-08T17:31:27Z</updated>
<entry>
<title>dt-bindings: net: vsc8531: add two additional LED modes for VSC8584</title>
<updated>2018-10-08T17:31:27Z</updated>
<author>
<name>Quentin Schulz</name>
<email>quentin.schulz@bootlin.com</email>
</author>
<published>2018-10-08T10:14:41Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=9494a6c2e4f6ce21a1e6885145171f90c4492131'/>
<id>urn:sha1:9494a6c2e4f6ce21a1e6885145171f90c4492131</id>
<content type='text'>
The VSC8584 (and most likely other PHYs in the same generation) has two
additional LED modes that can be picked, so let's add them.

Reviewed-by: Rob Herring &lt;robh@kernel.org&gt;
Reviewed-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;
Reviewed-by: Andrew Lunn &lt;andrew@lunn.ch&gt;
Signed-off-by: Quentin Schulz &lt;quentin.schulz@bootlin.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>lan78xx: Read LED states from Device Tree</title>
<updated>2018-04-20T15:39:09Z</updated>
<author>
<name>Phil Elwell</name>
<email>phil@raspberrypi.org</email>
</author>
<published>2018-04-19T16:59:39Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=1827b0678863bc97a1653fdf5308762b2aefcd56'/>
<id>urn:sha1:1827b0678863bc97a1653fdf5308762b2aefcd56</id>
<content type='text'>
Add support for DT property "microchip,led-modes", a vector of zero
to four cells (u32s) in the range 0-15, each of which sets the mode
for one of the LEDs. Some possible values are:

    0=link/activity          1=link1000/activity
    2=link100/activity       3=link10/activity
    4=link100/1000/activity  5=link10/1000/activity
    6=link10/100/activity    14=off    15=on

These values are given symbolic constants in a dt-bindings header.

Also use the presence of the DT property to indicate that the
LEDs should be enabled - necessary in the event that no valid OTP
or EEPROM is available.

Signed-off-by: Phil Elwell &lt;phil@raspberrypi.org&gt;
Reviewed-by: Andrew Lunn &lt;andrew@lunn.ch&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>net: phy: dp83867: Add binding for the CLK_OUT pin muxing option</title>
<updated>2018-02-14T20:33:43Z</updated>
<author>
<name>Wadim Egorov</name>
<email>w.egorov@phytec.de</email>
</author>
<published>2018-02-14T16:07:11Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=9708fb630d19ee51ae3aeb3a533e3010da0e8570'/>
<id>urn:sha1:9708fb630d19ee51ae3aeb3a533e3010da0e8570</id>
<content type='text'>
The DP83867 has a muxing option for the CLK_OUT pin. It is possible
to set CLK_OUT for different channels.
Create a binding to select a specific clock for CLK_OUT pin.

Signed-off-by: Wadim Egorov &lt;w.egorov@phytec.de&gt;
Signed-off-by: Daniel Schultz &lt;d.schultz@phytec.de&gt;
Reviewed-by: Andrew Lunn &lt;andrew@lunn.ch&gt;
Reviewed-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>net: phy: Add LED mode driver for Microsemi PHYs.</title>
<updated>2017-02-08T18:29:04Z</updated>
<author>
<name>Raju Lakkaraju</name>
<email>Raju.Lakkaraju@microsemi.com</email>
</author>
<published>2017-02-07T13:40:26Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=04d8a0a5f3b6887543850d991a5e37c4ec90e250'/>
<id>urn:sha1:04d8a0a5f3b6887543850d991a5e37c4ec90e250</id>
<content type='text'>
LED Mode:
Microsemi PHY support 2 LEDs (LED[0] and LED[1]) to display different
status information that can be selected by setting LED mode.

LED Mode parameter (vsc8531, led-0-mode) and (vsc8531, led-1-mode) get
from Device Tree.

Signed-off-by: Raju Lakkaraju &lt;Raju.Lakkaraju@microsemi.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>dt: bindings: net: use boolean dt properties for eee broken modes</title>
<updated>2016-12-20T18:50:50Z</updated>
<author>
<name>jbrunet</name>
<email>jbrunet@baylibre.com</email>
</author>
<published>2016-12-19T15:05:38Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=308d3165d8b2b98d3dc3d97d6662062735daea67'/>
<id>urn:sha1:308d3165d8b2b98d3dc3d97d6662062735daea67</id>
<content type='text'>
The patches regarding eee-broken-modes was merged before all people
involved could find an agreement on the best way to move forward.

While we agreed on having a DT property to mark particular modes as broken,
the value used for eee-broken-modes mapped the phy register in very direct
way. Because of this, the concern is that it could be used to implement
configuration policies instead of describing a broken HW.

In the end, having a boolean property for each mode seems to be preferred
over one bit field value mapping the register (too) directly.

Cc: Florian Fainelli &lt;f.fainelli@gmail.com&gt;
Signed-off-by: Jerome Brunet &lt;jbrunet@baylibre.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>dt-bindings: net: add EEE capability constants</title>
<updated>2016-11-30T00:38:31Z</updated>
<author>
<name>jbrunet</name>
<email>jbrunet@baylibre.com</email>
</author>
<published>2016-11-28T09:46:47Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=1fc31357ad194fb98691f3d122bcd47e59239e83'/>
<id>urn:sha1:1fc31357ad194fb98691f3d122bcd47e59239e83</id>
<content type='text'>
Signed-off-by: Jerome Brunet &lt;jbrunet@baylibre.com&gt;
Tested-by: Yegor Yefremov &lt;yegorslists@googlemail.com&gt;
Tested-by: Andreas Färber &lt;afaerber@suse.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>net: phy: Cleanup the Edge-Rate feature in Microsemi PHYs.</title>
<updated>2016-10-14T14:06:13Z</updated>
<author>
<name>Allan W. Nielsen</name>
<email>allan.nielsen@microsemi.com</email>
</author>
<published>2016-10-12T13:47:51Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=4f58e6dceb0e44ca8f21568ed81e1df24e55964c'/>
<id>urn:sha1:4f58e6dceb0e44ca8f21568ed81e1df24e55964c</id>
<content type='text'>
Edge-Rate cleanup include the following:
- Updated device tree bindings documentation for edge-rate
- The edge-rate is now specified as a "slowdown", meaning that it is now
  being specified as positive values instead of negative (both
  documentation and implementation wise).
- Only explicitly documented values for "vsc8531,vddmac" and
  "vsc8531,edge-slowdown" are accepted by the device driver.
- Deleted include/dt-bindings/net/mscc-phy-vsc8531.h as it was not needed.
- Read/validate devicetree settings in probe instead of init

Signed-off-by: Allan W. Nielsen &lt;allan.nielsen@microsemi.com&gt;
Signed-off-by: Raju Lakkaraju &lt;raju.lakkaraju@microsemi.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>net: phy: Add Edge-rate driver for Microsemi PHYs.</title>
<updated>2016-10-04T04:47:30Z</updated>
<author>
<name>Raju Lakkaraju</name>
<email>Raju.Lakkaraju@microsemi.com</email>
</author>
<published>2016-10-03T07:23:13Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=a4cc96d1f0170b779c32c6b2cc58764f5d2cdef0'/>
<id>urn:sha1:a4cc96d1f0170b779c32c6b2cc58764f5d2cdef0</id>
<content type='text'>
Edge-rate:
As system and networking speeds increase, a signal's output transition,
also know as the edge rate or slew rate (V/ns), takes on greater importance
because high-speed signals come with a price. That price is an assortment of
interference problems like ringing on the line, signal overshoot and
undershoot, extended signal settling times, crosstalk noise, transmission
line reflections, false signal detection by the receiving device and
electromagnetic interference (EMI) -- all of which can negate the potential
gains designers are seeking when they try to increase system speeds through
the use of higher performance logic devices. The fact is, faster signaling
edge rates can cause a higher level of electrical noise or other type of
interference that can actually lead to slower line speeds and lower maximum
system frequencies. This parameter allow the board designers to change the
driving strange, and thereby change the EMI behavioral.

Edge-rate parameters (vddmac, edge-slowdown) get from Device Tree.

Tested on Beaglebone Black with VSC 8531 PHY.

Signed-off-by: Raju Lakkaraju &lt;Raju.Lakkaraju@microsemi.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>net: phy: dp83867: Add TI dp83867 phy</title>
<updated>2015-06-04T02:41:04Z</updated>
<author>
<name>Dan Murphy</name>
<email>dmurphy@ti.com</email>
</author>
<published>2015-06-02T14:34:37Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=2a10154abcb75ad0d7b6bfea6210ac743ec60897'/>
<id>urn:sha1:2a10154abcb75ad0d7b6bfea6210ac743ec60897</id>
<content type='text'>
Add support for the TI dp83867 Gigabit ethernet phy
device.

The DP83867 is a robust, low power, fully featured
Physical Layer transceiver with integrated PMD
sublayers to support 10BASE-T, 100BASE-TX and
1000BASE-T Ethernet protocols.

Signed-off-by: Dan Murphy &lt;dmurphy@ti.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
