From: Andrew Lunn <andrew@lunn.ch>
To: Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: vkoul@kernel.org, neil.armstrong@linaro.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, sjakhade@cadence.com,
rogerq@kernel.org, krzk@kernel.org,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
srk@ti.com
Subject: Re: [PATCH v2 2/2] phy: cadence-torrent: Add PCIe + XAUI multilink configuration for 100MHz refclk
Date: Sun, 4 Jan 2026 22:57:36 +0100 [thread overview]
Message-ID: <7fd42221-d602-4ce4-9f7f-6754ed91e7aa@lunn.ch> (raw)
In-Reply-To: <20260104114422.2868321-3-s-vadapalli@ti.com>
On Sun, Jan 04, 2026 at 05:14:18PM +0530, Siddharth Vadapalli wrote:
> From: Swapnil Jakhade <sjakhade@cadence.com>
>
> Add register sequences for PCIe + XAUI multilink configuration for
> 100MHz reference clock.
>
> Signed-off-by: Swapnil Jakhade <sjakhade@cadence.com>
> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
> ---
>
> v1 of this patch is at:
> https://lore.kernel.org/r/20251224054905.763399-3-s-vadapalli@ti.com/
> No changes since v1.
>
> Regards,
> Siddharth.
>
> drivers/phy/cadence/phy-cadence-torrent.c | 143 ++++++++++++++++++++--
> 1 file changed, 136 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/phy/cadence/phy-cadence-torrent.c b/drivers/phy/cadence/phy-cadence-torrent.c
> index 37fa4bad6bd7..f0d870886cca 100644
> --- a/drivers/phy/cadence/phy-cadence-torrent.c
> +++ b/drivers/phy/cadence/phy-cadence-torrent.c
> @@ -300,6 +300,7 @@ enum cdns_torrent_phy_type {
> TYPE_USB,
> TYPE_USXGMII,
> TYPE_PCIE_ML,
> + TYPE_XAUI,
> };
>
> enum cdns_torrent_ref_clk {
> @@ -320,14 +321,14 @@ enum cdns_torrent_ssc_mode {
> /* Unique key id for vals table entry
> * REFCLK0_RATE | REFCLK1_RATE | LINK0_TYPE | LINK1_TYPE | SSC_TYPE
> */
> -#define REFCLK0_SHIFT 12
> -#define REFCLK0_MASK GENMASK(14, 12)
> -#define REFCLK1_SHIFT 9
> -#define REFCLK1_MASK GENMASK(11, 9)
> -#define LINK0_SHIFT 6
> -#define LINK0_MASK GENMASK(8, 6)
> +#define REFCLK0_SHIFT 15
> +#define REFCLK0_MASK GENMASK(18, 15)
> +#define REFCLK1_SHIFT 11
> +#define REFCLK1_MASK GENMASK(14, 11)
> +#define LINK0_SHIFT 7
> +#define LINK0_MASK GENMASK(10, 7)
Why do these change? It would be good to add an explanation to the
commit message about this, because it is not obvious why these need to
change.
Andrew
next prev parent reply other threads:[~2026-01-04 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 11:44 [PATCH v2 0/2] Cadence: Torrent: Enable PCIe + XAUI multilink configuration Siddharth Vadapalli
2026-01-04 11:44 ` [PATCH v2 1/2] dt-bindings: phy: Add PHY_TYPE_XAUI definition Siddharth Vadapalli
2026-01-06 18:29 ` Rob Herring (Arm)
2026-01-04 11:44 ` [PATCH v2 2/2] phy: cadence-torrent: Add PCIe + XAUI multilink configuration for 100MHz refclk Siddharth Vadapalli
2026-01-04 21:57 ` Andrew Lunn [this message]
2026-01-05 15:17 ` Siddharth Vadapalli
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=7fd42221-d602-4ce4-9f7f-6754ed91e7aa@lunn.ch \
--to=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=sjakhade@cadence.com \
--cc=srk@ti.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
all inboxes | Powered by JetHome®