From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>
Cc: Marek Vasut <marex@denx.de>, Minda Chen <minda.chen@starfivetech.com>
Subject: [PULL] u-boot-usb/next
Date: Mon, 17 Mar 2025 04:15:23 +0100 [thread overview]
Message-ID: <20250317031542.223248-1-marex@denx.de> (raw)
The following changes since commit 0e1fc465fea62ebae91f2f56cb823e8b37ee1077:
Merge tag 'dm-pull-15mar25' of git://git.denx.de/u-boot-dm into next (2025-03-15 08:19:31 -0600)
are available in the Git repository at:
git://source.denx.de/u-boot-usb.git next
for you to fetch changes up to b0e75b4fb0bdecdcec59ff6f72d02513ad466272:
configs: starfive: Add visionfive2 cadence USB configuration (2025-03-17 01:55:19 +0100)
----------------------------------------------------------------
Minda Chen (7):
usb: cdns3: Set USB PHY mode in cdns3_drd_update_mode()
phy: starfive: Add Starfive JH7110 USB 2.0 PHY driver
phy: starfive: Add Starfive JH7110 PCIe 2.0 PHY driver
usb: cdns: starfive: Get dr mode from wrapper device dts node
usb: cdns: starfive: Add cdns USB driver
spl: starfive: visionfive2: Disable USB overcurrent pin by default.
configs: starfive: Add visionfive2 cadence USB configuration
arch/riscv/include/asm/arch-jh7110/gpio.h | 5 +
board/starfive/visionfive2/spl.c | 3 +
configs/starfive_visionfive2_defconfig | 10 ++
drivers/phy/Kconfig | 1 +
drivers/phy/Makefile | 1 +
drivers/phy/starfive/Kconfig | 21 +++
drivers/phy/starfive/Makefile | 7 +
drivers/phy/starfive/phy-jh7110-pcie.c | 239 +++++++++++++++++++++++++++
drivers/phy/starfive/phy-jh7110-usb-syscon.h | 9 +
drivers/phy/starfive/phy-jh7110-usb2.c | 162 ++++++++++++++++++
drivers/usb/cdns3/Kconfig | 7 +
drivers/usb/cdns3/Makefile | 1 +
drivers/usb/cdns3/cdns3-starfive.c | 182 ++++++++++++++++++++
drivers/usb/cdns3/core.c | 3 +
drivers/usb/cdns3/drd.c | 14 ++
15 files changed, 665 insertions(+)
create mode 100644 drivers/phy/starfive/Kconfig
create mode 100644 drivers/phy/starfive/Makefile
create mode 100644 drivers/phy/starfive/phy-jh7110-pcie.c
create mode 100644 drivers/phy/starfive/phy-jh7110-usb-syscon.h
create mode 100644 drivers/phy/starfive/phy-jh7110-usb2.c
create mode 100644 drivers/usb/cdns3/cdns3-starfive.c
next reply other threads:[~2025-03-17 3:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 3:15 Marek Vasut [this message]
2025-03-18 1:14 ` [PULL] u-boot-usb/next Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2026-06-03 0:40 Marek Vasut
2026-06-03 18:21 ` Tom Rini
2025-10-05 12:59 Marek Vasut
2025-10-05 17:48 ` Tom Rini
2025-09-25 23:08 Marek Vasut
2025-09-26 15:56 ` Tom Rini
2024-09-09 20:20 Marek Vasut
2024-09-10 4:08 ` Tom Rini
2023-09-16 10:16 Marek Vasut
2023-09-16 22:38 ` Tom Rini
2023-09-05 13:50 Marek Vasut
2023-09-06 17:50 ` Tom Rini
2023-05-18 15:01 Marek Vasut
2023-05-18 20:09 ` Tom Rini
2023-03-03 0:05 Marek Vasut
2023-03-03 23:40 ` Tom Rini
2023-02-22 15:36 Marek Vasut
2023-02-22 18:37 ` Tom Rini
2023-02-22 22:09 ` Marek Vasut
2023-02-23 1:50 ` Tom Rini
2023-02-23 4:45 ` Marek Vasut
2023-02-23 16:36 ` Tom Rini
2020-10-01 8:29 Marek Vasut
2020-10-01 17:09 ` Tom Rini
2020-10-01 17:42 ` Marek Vasut
2020-10-01 18:09 ` Tom Rini
2020-10-01 18:38 ` Marek Vasut
2020-03-30 9:32 Marek Vasut
2020-04-01 13:43 ` Tom Rini
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=20250317031542.223248-1-marex@denx.de \
--to=marex@denx.de \
--cc=minda.chen@starfivetech.com \
--cc=trini@konsulko.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 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.