From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: <vkoul@kernel.org>, <kishon@kernel.org>, <sjakhade@cadence.com>,
<rogerq@kernel.org>, <thomas.richard@bootlin.com>,
<christophe.jaillet@wanadoo.fr>, <u.kleine-koenig@baylibre.com>,
<eballetb@redhat.com>
Cc: <linux-phy@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <srk@ti.com>,
<s-vadapalli@ti.com>
Subject: [PATCH v3 0/2] Enable PCIe Multilink and USB support in Cadence Torrent SERDES driver
Date: Thu, 9 Jan 2025 17:46:01 +0530 [thread overview]
Message-ID: <20250109121614.754466-1-s-vadapalli@ti.com> (raw)
Hello,
This series adds support for standalone PCIe Multilink configuration
along with the support for PCIe Multilink + USB configuration in the
Torrent SERDES driver.
Series is based on linux-next tagged next-20250109.
v2:
https://lore.kernel.org/r/20250106131925.263240-1-s-vadapalli@ti.com/
Changes since v2:
- Rebased series on next-20250109.
- Based on feedback received from:
Christophe JAILLET <christophe.jaillet@wanadoo.fr>
a) "const" has been used wherever applicable i.e.:
s/static struct cdns_reg_pairs/static const struct cdns_reg_pairs
s/static struct cdns_torrent_vals/static const struct cdns_torrent_vals
b) Commenting style in patch 2 has been fixed.
v1:
https://lore.kernel.org/r/20240615093433.3659829-1-s-vadapalli@ti.com/
Changes since v1:
- Rebased series on next-20250106.
- Significant changes have been made in the second patch of the series
in the process of rebasing. Support for 3 or more links was introduced
and this series had to be modified to be compatible with those changes.
- Added "Co-developed-by" tag in the second patch since some of the
changes in this series in the process of rebasing were made by me
which are quite different from the v1 version of the patch.
- Due to these changes, I have *not* collected the "Tested-by" tag on the
v1 series from Enric Balletbo i Serra <eballetbo@redhat.com>
and I hope that this series can be tested.
***NOTE***
Since I don't have the hardware required to validate PCIe Multilink +
USB functionality, kindly *do not merge* this series until it gets a
"Tested-by" tag with proper validation of the functionality.
Regards,
Siddharth.
Swapnil Jakhade (2):
phy: cadence-torrent: Add PCIe multilink configuration for 100 MHz
refclk
phy: cadence-torrent: Add PCIe multilink + USB with same SSC register
config for 100 MHz refclk
drivers/phy/cadence/phy-cadence-torrent.c | 288 +++++++++++++++++++++-
1 file changed, 279 insertions(+), 9 deletions(-)
--
2.43.0
next reply other threads:[~2025-01-09 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 12:16 Siddharth Vadapalli [this message]
2025-01-09 12:16 ` [PATCH v3 1/2] phy: cadence-torrent: Add PCIe multilink configuration for 100 MHz refclk Siddharth Vadapalli
2025-01-09 16:35 ` Roger Quadros
2025-06-12 8:48 ` Enric Balletbo i Serra
2025-06-12 10:04 ` Siddharth Vadapalli
2025-06-15 14:10 ` Vinod Koul
2025-06-16 6:13 ` Siddharth Vadapalli
2025-01-09 12:16 ` [PATCH v3 2/2] phy: cadence-torrent: Add PCIe multilink + USB with same SSC register config " Siddharth Vadapalli
2025-01-09 16:37 ` Roger Quadros
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=20250109121614.754466-1-s-vadapalli@ti.com \
--to=s-vadapalli@ti.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=eballetb@redhat.com \
--cc=kishon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=rogerq@kernel.org \
--cc=sjakhade@cadence.com \
--cc=srk@ti.com \
--cc=thomas.richard@bootlin.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=vkoul@kernel.org \
/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