<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/drivers/net/phy/Kconfig, branch v2020.10</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/drivers/net/phy/Kconfig?h=v2020.10</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/drivers/net/phy/Kconfig?h=v2020.10'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2020-07-07T20:09:22Z</updated>
<entry>
<title>net: phy: realtek: Introduce PHY_RTL8201F_S700_RMII_TIMINGS to adjust rx/tx timings</title>
<updated>2020-07-07T20:09:22Z</updated>
<author>
<name>Amit Singh Tomar</name>
<email>amittomer25@gmail.com</email>
</author>
<published>2020-05-09T14:25:11Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=fa6539a3dcbf269121ca64084cff4c146fcdaf19'/>
<id>urn:sha1:fa6539a3dcbf269121ca64084cff4c146fcdaf19</id>
<content type='text'>
RTL8201F PHY module found on Actions Semi Cubieboard7 seems to have
specific Rx/Tx interface timings requirement for proper PHY operations.
These timing values are not documented anywhere and picked from vendor
code.

This commits lets proper packets to be transmitted over the network.

Signed-off-by: Amit Singh Tomar &lt;amittomer25@gmail.com&gt;
</content>
</entry>
<entry>
<title>net: phy: Add DP8382x phy registration to TI PHY init</title>
<updated>2020-06-12T17:17:23Z</updated>
<author>
<name>Dan Murphy</name>
<email>dmurphy@ti.com</email>
</author>
<published>2020-05-04T21:14:40Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8882238cc4c1276629c989ea1fe71b15358a5040'/>
<id>urn:sha1:8882238cc4c1276629c989ea1fe71b15358a5040</id>
<content type='text'>
Add the DP8382X generic PHY registration to the TI PHY init file.

Acked-by: Michal Simek &lt;michal.simek@xilinx.com&gt;
Signed-off-by: Dan Murphy &lt;dmurphy@ti.com&gt;
</content>
</entry>
<entry>
<title>net: phy: Add support for TI PHY init</title>
<updated>2020-06-12T17:17:23Z</updated>
<author>
<name>Dan Murphy</name>
<email>dmurphy@ti.com</email>
</author>
<published>2020-05-04T21:14:39Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=bc0e578f903d24b5291d34959ad534138ced0780'/>
<id>urn:sha1:bc0e578f903d24b5291d34959ad534138ced0780</id>
<content type='text'>
ti_phy_init function was allocated to the DP83867 PHY.  This function
name is to generic for a specific PHY.  The function can be moved to a
TI specific file that can register all TI PHYs that are defined in the
defconfig.  The ti_phy_init file will contain all TI PHYs initialization
so that only phy_ti_init can be called from the framework.

In addition to the above the config flag for the DP83867 needs to be changed
in the Kconfig and dependent defconfig files. The config flag that was
used for the DP83867 was also generic in nature so a more specific
config flag for the DP83867 was created.

Acked-by: Michal Simek &lt;michal.simek@xilinx.com&gt;
Signed-off-by: Dan Murphy &lt;dmurphy@ti.com&gt;
</content>
</entry>
<entry>
<title>phy: Add support for the NC-SI protocol</title>
<updated>2020-03-09T23:11:23Z</updated>
<author>
<name>Samuel Mendoza-Jonas</name>
<email>sam@mendozajonas.com</email>
</author>
<published>2019-06-18T01:37:17Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f641a8ac93e0c0179fe6f73429812af228109ff2'/>
<id>urn:sha1:f641a8ac93e0c0179fe6f73429812af228109ff2</id>
<content type='text'>
This introduces support for the NC-SI protocol, modelled as a phy driver
for other ethernet drivers to consume.

NC-SI (Network Controller Sideband Interface) is a protocol to manage a
sideband connection to a proper network interface, for example a BMC
(Baseboard Management Controller) sharing the NIC of the host system.
Probing and configuration occurs by communicating with the "remote" NIC
via NC-SI control frames (Ethernet header 0x88f8).

This implementation is roughly based on the upstream Linux
implementation[0], with a reduced feature set and an emphasis on getting
a link up as fast as possible rather than probing the full possible
topology of the bus.
The current phy model relies on the network being "up", sending NC-SI
command frames via net_send_packet() and receiving them from the
net_loop() loop (added in a following patch).

The ncsi-pkt.h header[1] is copied from the Linux kernel for consistent
field definitions.

[0]: https://github.com/torvalds/linux/tree/master/net/ncsi
[1]: https://github.com/torvalds/linux/blob/master/net/ncsi/ncsi-pkt.h

Signed-off-by: Samuel Mendoza-Jonas &lt;sam@mendozajonas.com&gt;
Reviewed-by: Joel Stanley &lt;joel@jms.id.au&gt;
Acked-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
</content>
</entry>
<entry>
<title>net: phy: fix switch vendor name</title>
<updated>2019-12-09T15:47:42Z</updated>
<author>
<name>Anatolij Gustschin</name>
<email>agust@denx.de</email>
</author>
<published>2019-10-26T23:14:41Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=389488df92f08eed95149e66562d29db634af6a3'/>
<id>urn:sha1:389488df92f08eed95149e66562d29db634af6a3</id>
<content type='text'>
Fix vendor name in MV88E61xx option description.

Signed-off-by: Anatolij Gustschin &lt;agust@denx.de&gt;
Reviewed-by: Chris Packham &lt;judge.packham@gmail.com&gt;
Tested-by: Chris Packham &lt;judge.packham@gmail.com&gt;
Acked-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
</content>
</entry>
<entry>
<title>Convert CONFIG_SYS_CORTINA_FW_IN_MMC et al to Kconfig</title>
<updated>2019-12-03T13:43:24Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2019-11-26T22:32:43Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e78f16b751c86de8d20222083b1d14fd4e1c0f59'/>
<id>urn:sha1:e78f16b751c86de8d20222083b1d14fd4e1c0f59</id>
<content type='text'>
This converts the following to Kconfig:
   CONFIG_SYS_CORTINA_FW_IN_MMC
   CONFIG_SYS_CORTINA_FW_IN_NAND
   CONFIG_SYS_CORTINA_FW_IN_NOR
   CONFIG_SYS_CORTINA_FW_IN_REMOTE
   CONFIG_SYS_CORTINA_FW_IN_SPIFLASH

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>net: phy: Add gmiitorgmii converter support</title>
<updated>2019-10-08T07:41:27Z</updated>
<author>
<name>Siva Durga Prasad Paladugu</name>
<email>siva.durga.paladugu@xilinx.com</email>
</author>
<published>2018-11-27T06:19:11Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f41e588c033f31cdf4b1f1c70fac2e0264c6c4db'/>
<id>urn:sha1:f41e588c033f31cdf4b1f1c70fac2e0264c6c4db</id>
<content type='text'>
This patch adds support for gmiitorgmii converter.
This converter sits between the MAC and the external phy
MAC &lt;==&gt; GMII2RGMII &lt;==&gt; RGMII_PHY.
The ethernet driver probes this bridge and this bridge driver
probes real phy driver and invokes the real phy functionalities
as requested. This bridge just needs to be configured based on
real phy negotiated speed and duplex.

Signed-off-by: Siva Durga Prasad Paladugu &lt;siva.durga.paladugu@xilinx.com&gt;
Signed-off-by: Michal Simek &lt;michal.simek@xilinx.com&gt;
</content>
</entry>
<entry>
<title>net: phy: micrel: Allow KSZ8xxx and KSZ90x1 to be used together</title>
<updated>2019-05-14T19:43:33Z</updated>
<author>
<name>James Byrne</name>
<email>james.byrne@origamienergy.com</email>
</author>
<published>2019-03-06T12:48:27Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=77b508d34b9485c981b084e8169dd64b381935b6'/>
<id>urn:sha1:77b508d34b9485c981b084e8169dd64b381935b6</id>
<content type='text'>
Commit d397f7c45b0b ("net: phy: micrel: Separate KSZ9000 drivers from
KSZ8000 drivers") separated the KSZ8xxx and KSZ90x1 drivers and warns
that you shouldn't select both of them due to a device ID clash between
the KSZ9021 and the KS8721, asserting that "it is highly unlikely for a
system to contain both a KSZ8000 and a KSZ9000 PHY". Unfortunately
boards like the SAMA5D3xEK do contain both types of PHY, but fortunately
the Linux Micrel PHY driver provides a solution by using different PHY
ID and mask values to distinguish these chips.

This commit contains the following changes:

- The PHY ID and mask values for the KSZ9021 and the KS8721 now match
those used by the Linux driver.
- The warnings about not enabling both drivers have been removed.
- The description for PHY_MICREL_KSZ8XXX has been corrected (these are
10/100 PHYs, not GbE PHYs).
- PHY_MICREL_KSZ9021 and PHY_MICREL_KSZ9031 no longer select PHY_GIGE
since this is selected by PHY_MICREL_KSZ90X1.
- All of the relevant defconfig files have been updated now that
PHY_MICREL_KSZ8XXX does not default to 'Y'.

Signed-off-by: James Byrne &lt;james.byrne@origamienergy.com&gt;
Acked-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
</content>
</entry>
<entry>
<title>net: phy: realtek: Introduce quirk to mark RXC not stoppable</title>
<updated>2019-05-07T19:51:55Z</updated>
<author>
<name>Carlo Caione</name>
<email>ccaione@baylibre.com</email>
</author>
<published>2019-01-24T08:54:37Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=d47cfdbd315297af73746462599b0c81dac6054a'/>
<id>urn:sha1:d47cfdbd315297af73746462599b0c81dac6054a</id>
<content type='text'>
When EEE is supported by the PHY and the driver allows it, libphy in the
kernel is configuring the PHY to stop receiving the xMII clock while it
is signaling LPI. While this (usually) works fine in the kernel this is
causing issues in U-Boot when rebooting from the linux kernel with this
bit set (without having the possibility to reset the PHY) where the PHY
suddenly stops working.

A new quirk is introduced to unconditionally reset this bit. If the
quirk is not enabled using the proper configuration symbol, the PHY state
is not changed.

Signed-off-by: Carlo Caione &lt;ccaione@baylibre.com&gt;
Acked-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
</content>
</entry>
<entry>
<title>net: phy: aquantia: add firmware loading support</title>
<updated>2018-10-24T19:45:37Z</updated>
<author>
<name>Jeremy Gebben</name>
<email>jgebben@sweptlaser.com</email>
</author>
<published>2018-09-18T21:49:36Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=4506423ad23749a28ae48720bc64ad40caf089b2'/>
<id>urn:sha1:4506423ad23749a28ae48720bc64ad40caf089b2</id>
<content type='text'>
Aquantia phys have firmware that can be loaded automatically
from storage directly attached to the phy or via MDIO commands.
Add support for loading firmware from either a file or a
raw location on an MMC device.

Signed-off-by: Jeremy Gebben &lt;jgebben@sweptlaser.com&gt;
Acked-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
</content>
</entry>
</feed>
