From: Grygorii Strashko <grygorii.strashko@ti.com>
To: u-boot@lists.denx.de
Subject: [PATCH v4 0/5] TI Ethernet PHY changes
Date: Mon, 18 May 2020 21:20:04 +0300 [thread overview]
Message-ID: <1d17e8c8-ede1-7b41-bdff-026b24e681ca@ti.com> (raw)
In-Reply-To: <20200504211440.13385-1-dmurphy@ti.com>
On 05/05/2020 00:14, Dan Murphy wrote:
> Hello
>
> The addition of the DP83867 driver to uboot was done in a generic way that
> made it a bit difficult to bring in new PHY drivers. The difficulty came in the
> config flags and the phy_init function. The change is to make the flags and
> init for the DP83867 more specific to the DP83867 device to make way to add
> more TI PHYs to uBoot.
>
> In addition the DP8382X PHY is a generic PHY driver that does not need any
> special handling to establish a link. Customers have requested that at the very
> least there be a way to know if the PHY attached is the PHY that is connected
> as "Generic PHY" is not really descriptive. These patches adds the
> registrations for TI Generic PHYs to associcate a TI PHY ID with a PHY name.
>
> Porting PHY helper routines to set and clear bits to facilitate easier side
> porting of ethernet kernel drivers to uBoot.
>
> Also fixed and added missing or kernel doc documentation in the phy.h file.
>
> Dan
>
> Dan Murphy (5):
> net: phy: Add missing kernel doc to phy functions
> net: phy: Fix kernel doc issues in phy.h
> net: phy: Add helper routines to set and clear bits
> net: phy: Add support for TI PHY init
> net: phy: Add DP8382x phy registration to TI PHY init
>
> configs/am65x_evm_a53_defconfig | 2 +-
> configs/am65x_hs_evm_a53_defconfig | 2 +-
> configs/dra7xx_evm_defconfig | 2 +-
> configs/dra7xx_hs_evm_defconfig | 2 +-
> configs/dra7xx_hs_evm_usb_defconfig | 2 +-
> configs/j721e_evm_a72_defconfig | 2 +-
> configs/j721e_hs_evm_a72_defconfig | 2 +-
> configs/k2g_evm_defconfig | 2 +-
> configs/xilinx_versal_virt_defconfig | 2 +-
> configs/xilinx_zynqmp_virt_defconfig | 2 +-
> drivers/net/phy/Kconfig | 15 ++++
> drivers/net/phy/Makefile | 3 +-
> drivers/net/phy/dp83867.c | 3 +-
> drivers/net/phy/ti_phy_init.c | 101 ++++++++++++++++++++++++
> drivers/net/phy/ti_phy_init.h | 15 ++++
> include/phy.h | 112 ++++++++++++++++++++++++---
> 16 files changed, 246 insertions(+), 23 deletions(-)
> create mode 100644 drivers/net/phy/ti_phy_init.c
> create mode 100644 drivers/net/phy/ti_phy_init.h
>
Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
--
Best regards,
grygorii
prev parent reply other threads:[~2020-05-18 18:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 21:14 [PATCH v4 0/5] TI Ethernet PHY changes Dan Murphy
2020-05-04 21:14 ` [PATCH v4 1/5] net: phy: Add missing kernel doc to phy functions Dan Murphy
2020-06-12 21:15 ` Tom Rini
2020-05-04 21:14 ` [PATCH v4 2/5] net: phy: Fix kernel doc issues in phy.h Dan Murphy
2020-06-12 21:16 ` Tom Rini
2020-05-04 21:14 ` [PATCH v4 3/5] net: phy: Add helper routines to set and clear bits Dan Murphy
2020-06-12 21:16 ` Tom Rini
2020-05-04 21:14 ` [PATCH v4 4/5] net: phy: Add support for TI PHY init Dan Murphy
2020-06-12 21:16 ` Tom Rini
2020-05-04 21:14 ` [PATCH v4 5/5] net: phy: Add DP8382x phy registration to " Dan Murphy
2020-06-12 21:16 ` Tom Rini
2020-05-12 0:52 ` [PATCH v4 0/5] TI Ethernet PHY changes Dan Murphy
2020-06-01 18:58 ` Dan Murphy
2020-05-18 18:20 ` Grygorii Strashko [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=1d17e8c8-ede1-7b41-bdff-026b24e681ca@ti.com \
--to=grygorii.strashko@ti.com \
--cc=u-boot@lists.denx.de \
/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