U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Kropatsch <seb-dev@mail.de>
To: Simon Glass <sjg@chromium.org>,
	Philipp Tomsich <philipp.tomsich@vrull.eu>,
	Kever Yang <kever.yang@rock-chips.com>
Cc: Tom Rini <trini@konsulko.com>, u-boot@lists.denx.de
Subject: [PATCH v2 0/5] phy: rockchip: snps-pcie3: Fix bifurcation and spelling
Date: Tue, 16 Jul 2024 22:42:05 +0200	[thread overview]
Message-ID: <cover.1721161722.git.seb-dev@mail.de> (raw)

Several fixes for RK3588's PCIe PHY from upstream Linux [1][2], which
uses a very similar driver.
Tested on a FriendlyElec CM3588 NAS which uses PCIe bifurcation in
1x1x1x1 mode to enable four M.2 NVMe sockets. With these fixes applied,
NVMe SSDs get properly recognized in U-Boot.

In addition, v2 introduces a new patch to fix combo PHY muxing for
RK3588. [3]

While at it, correct a few instances where "rockchip" was written as
"rochchip" in two Rockchip PHY files.

Cheers,
Sebastian
---

Changes v1 -> v2:

 - Add new patch "phy: rockchip: naneng-combphy: Introduce PHY-IDs to fix RK3588 muxing"
 - Collect "Reviewed-by: Kever Yang" tags for all previous patches
 - Link to v1: https://lore.kernel.org/u-boot/cover.1720988760.git.seb-dev@mail.de/T/

Links:
[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/phy/rockchip/phy-rockchip-snps-pcie3.c?id=f8020dfb311d2b6cf657668792aaa5fa8863a7dd
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/phy/rockchip/phy-rockchip-snps-pcie3.c?id=55491a5fa163bf15158f34f3650b3985f25622b9
[3] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c?id=d16d4002fea69b6609b852dd8db1f5844c02fbe4

---
Sebastian Kropatsch (5):
  phy: rockchip: naneng-combphy: Fix "rockchip" spelling
  phy: rockchip: naneng-combphy: Introduce PHY-IDs to fix RK3588 muxing
  phy: rockchip: snps-pcie3: Fix "rockchip" spelling
  phy: rockchip: snps-pcie3: Fix bifurcation for RK3588
  phy: rockchip: snps-pcie3: Fix clearing PHP_GRF_PCIESEL_CON bits

 .../rockchip/phy-rockchip-naneng-combphy.c    | 53 +++++++++++++++++--
 .../phy/rockchip/phy-rockchip-snps-pcie3.c    | 42 +++++++--------
 2 files changed, 67 insertions(+), 28 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-07-16 20:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-16 20:42 Sebastian Kropatsch [this message]
2024-07-16 20:42 ` [PATCH v2 1/5] phy: rockchip: naneng-combphy: Fix "rockchip" spelling Sebastian Kropatsch
2024-07-16 20:42 ` [PATCH v2 2/5] phy: rockchip: naneng-combphy: Introduce PHY-IDs to fix RK3588 muxing Sebastian Kropatsch
2024-07-17  0:48   ` Kever Yang
2024-07-21 18:40   ` Jonas Karlman
2024-07-23 20:43     ` Sebastian Kropatsch
2024-07-16 20:42 ` [PATCH v2 3/5] phy: rockchip: snps-pcie3: Fix "rockchip" spelling Sebastian Kropatsch
2024-07-16 20:42 ` [PATCH v2 4/5] phy: rockchip: snps-pcie3: Fix bifurcation for RK3588 Sebastian Kropatsch
2024-07-16 20:42 ` [PATCH v2 5/5] phy: rockchip: snps-pcie3: Fix clearing PHP_GRF_PCIESEL_CON bits Sebastian Kropatsch

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=cover.1721161722.git.seb-dev@mail.de \
    --to=seb-dev@mail.de \
    --cc=kever.yang@rock-chips.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=sjg@chromium.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox