From: Hans Zhang <18255117159@163.com>
To: bhelgaas@google.com, lpieralisi@kernel.org, kw@linux.com,
kwilczynski@kernel.org, mani@kernel.org,
ilpo.jarvinen@linux.intel.com, jingoohan1@gmail.com
Cc: robh@kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/3] PCI: dwc: Use common speed conversion function
Date: Mon, 6 Apr 2026 18:54:38 +0800 [thread overview]
Message-ID: <045cd971-7c84-4ca5-b64f-74c08abec0f9@163.com> (raw)
In-Reply-To: <20260406104708.1218648-4-18255117159@163.com>
Hi Mani,
This patch is missing one line of code:
link_speed = pcie_get_link_speed(pci->max_link_speed);
I'll send out v6. Sorry for the noise.
Best regards,
Hans
On 4/6/26 18:47, Hans Zhang wrote:
> Replace the private switch-based speed conversion in
> dw_pcie_link_set_max_speed() with the public pci_bus_speed2lnkctl2()
> function.
>
> This eliminates duplicate conversion logic and ensures consistency with
> other PCIe drivers, while handling invalid speeds by falling back to
> hardware capabilities.
>
> Signed-off-by: Hans Zhang <18255117159@163.com>
> Acked-by: Manivannan Sadhasivam <mani@kernel.org>
> ---
> drivers/pci/controller/dwc/pcie-designware.c | 17 ++---------------
> 1 file changed, 2 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/pcie-designware.c b/drivers/pci/controller/dwc/pcie-designware.c
> index 06792ba92aa7..f2dd5da69c76 100644
> --- a/drivers/pci/controller/dwc/pcie-designware.c
> +++ b/drivers/pci/controller/dwc/pcie-designware.c
> @@ -861,24 +861,11 @@ static void dw_pcie_link_set_max_speed(struct dw_pcie *pci)
> ctrl2 = dw_pcie_readl_dbi(pci, offset + PCI_EXP_LNKCTL2);
> ctrl2 &= ~PCI_EXP_LNKCTL2_TLS;
>
> - switch (pcie_get_link_speed(pci->max_link_speed)) {
> - case PCIE_SPEED_2_5GT:
> - link_speed = PCI_EXP_LNKCTL2_TLS_2_5GT;
> - break;
> - case PCIE_SPEED_5_0GT:
> - link_speed = PCI_EXP_LNKCTL2_TLS_5_0GT;
> - break;
> - case PCIE_SPEED_8_0GT:
> - link_speed = PCI_EXP_LNKCTL2_TLS_8_0GT;
> - break;
> - case PCIE_SPEED_16_0GT:
> - link_speed = PCI_EXP_LNKCTL2_TLS_16_0GT;
> - break;
> - default:
> + link_speed = pci_bus_speed2lnkctl2(link_speed);
> + if (link_speed == 0) {
> /* Use hardware capability */
> link_speed = FIELD_GET(PCI_EXP_LNKCAP_SLS, cap);
> ctrl2 &= ~PCI_EXP_LNKCTL2_HASD;
> - break;
> }
>
> dw_pcie_writel_dbi(pci, offset + PCI_EXP_LNKCTL2, ctrl2 | link_speed);
prev parent reply other threads:[~2026-04-06 10:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 10:47 [PATCH v5 0/3] PCI: Refactor PCIe speed validation and conversion functions Hans Zhang
2026-04-06 10:47 ` [PATCH v5 1/3] PCI: Add public pcie_valid_speed() for shared validation Hans Zhang
2026-04-06 10:47 ` [PATCH v5 2/3] PCI: Move pci_bus_speed2lnkctl2() to public header Hans Zhang
2026-04-07 8:11 ` Ilpo Järvinen
2026-04-07 12:09 ` Hans Zhang
2026-04-07 12:26 ` Ilpo Järvinen
2026-04-07 12:29 ` Hans Zhang
2026-04-07 12:48 ` Hans Zhang
2026-04-07 12:53 ` Ilpo Järvinen
2026-04-07 13:01 ` Hans Zhang
2026-04-06 10:47 ` [PATCH v5 3/3] PCI: dwc: Use common speed conversion function Hans Zhang
2026-04-06 10:54 ` Hans Zhang [this message]
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=045cd971-7c84-4ca5-b64f-74c08abec0f9@163.com \
--to=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jingoohan1@gmail.com \
--cc=kw@linux.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@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®