mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Siddharth Vadapalli <s-vadapalli@ti.com>,
	vkoul@kernel.org, kishon@kernel.org, sjakhade@cadence.com,
	rogerq@kernel.org, thomas.richard@bootlin.com,
	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
Subject: Re: [PATCH v2 2/2] phy: cadence-torrent: Add PCIe multilink + USB with same SSC register config for 100 MHz refclk
Date: Mon, 6 Jan 2025 23:05:35 +0100	[thread overview]
Message-ID: <24498c4e-c517-46b9-8d0c-ff1e3a308228@wanadoo.fr> (raw)
In-Reply-To: <20250106131925.263240-3-s-vadapalli@ti.com>

Le 06/01/2025 à 14:19, Siddharth Vadapalli a écrit :
> From: Swapnil Jakhade <sjakhade@cadence.com>
> 
> Add register sequences and support for PCIe multilink + USB configuration
> for 100MHz reference clock. The same SSC is used for both PCIe and USB.
> 
> Signed-off-by: Swapnil Jakhade <sjakhade@cadence.com>
> Co-developed-by: Siddharth Vadapalli <s-vadapalli@ti.com>
> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
> ---
...

> @@ -2513,6 +2517,44 @@ int cdns_torrent_phy_configure_multilink(struct cdns_torrent_phy *cdns_phy)
>   
>   		phy_t1 = fns(cdns_phy->protocol_bitmask, 0);
>   		phy_t2 = fns(cdns_phy->protocol_bitmask, 1);
> +
> +		/**

Why kernel-doc like start of comment?
Only /* ?

> +		 * PCIe Multilink configuration can be supported along with a
> +		 * non-PCIe protocol. The existing limitation associated with
> +		 * the standalone PCIe Multilink configuration still remains,
> +		 * implying that there can be only two links (subnodes) of the
> +		 * PHY type PCIe which constitute the PCIe Multilink.
> +		 *
> +		 * Such configurations are handled by introducing a new protocol
> +		 * namely TYPE_PCIE_ML. Both of the PCIe links which have the
> +		 * protocol as TYPE_PCIE shall be treated as though the protocol
> +		 * corresponding to them is TYPE_PCIE_ML only for the sake of
> +		 * configuring the SERDES.
> +		 *
> +		 * PCIe Multilink configuration can be identified by checking if
> +		 * there are exactly two links with phy_type set to TYPE_PCIE.
> +		 * phy_t1 and phy_t2 are modified in such cases to support the
> +		 * PCIe Multilink configuration with a non-PCIe protocol.
> +		 */
...

> @@ -3134,6 +3180,37 @@ static void cdns_torrent_phy_remove(struct platform_device *pdev)
>   	cdns_torrent_clk_cleanup(cdns_phy);
>   }
>   
> +/* Multilink PCIe and USB Same SSC link configuration */
> +static struct cdns_reg_pairs ml_pcie_usb_link_cmn_regs[] = {
> +	{0x0002, PHY_PLL_CFG},
> +	{0x8600, CMN_PDIAG_PLL0_CLK_SEL_M0}
> +};

Maybe const could be added here and below?

> +
> +static struct cdns_reg_pairs ml_pcie_usb_xcvr_diag_ln_regs[] = {
> +	{0x0100, XCVR_DIAG_HSCLK_SEL},
> +	{0x0013, XCVR_DIAG_HSCLK_DIV},
> +	{0x0812, XCVR_DIAG_PLLDRC_CTRL}
> +};

...

CJ

  reply	other threads:[~2025-01-06 22:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06 13:19 [PATCH v2 0/2] Enable PCIe Multilink and USB support in Cadence Torrent SERDES driver Siddharth Vadapalli
2025-01-06 13:19 ` [PATCH v2 1/2] phy: cadence-torrent: Add PCIe multilink configuration for 100 MHz refclk Siddharth Vadapalli
2025-01-06 22:00   ` Christophe JAILLET
2025-01-07  5:17     ` Siddharth Vadapalli
2025-01-06 13:19 ` [PATCH v2 2/2] phy: cadence-torrent: Add PCIe multilink + USB with same SSC register config " Siddharth Vadapalli
2025-01-06 22:05   ` Christophe JAILLET [this message]
2025-01-07  5:19     ` Siddharth Vadapalli
2025-01-09 12:20       ` 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=24498c4e-c517-46b9-8d0c-ff1e3a308228@wanadoo.fr \
    --to=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=s-vadapalli@ti.com \
    --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

all inboxes | Powered by JetHome®