From: Shawn Lin <shawn.lin@rock-chips.com>
To: Hans Zhang <18255117159@163.com>,
bhelgaas@google.com, lpieralisi@kernel.org, kw@linux.com,
kwilczynski@kernel.org, mani@kernel.org,
ilpo.jarvinen@linux.intel.com, jingoohan1@gmail.com
Cc: shawn.lin@rock-chips.com, robh@kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/3] PCI: Refactor PCIe speed validation and conversion functions
Date: Tue, 7 Apr 2026 08:36:04 +0800 [thread overview]
Message-ID: <0e7148cd-06ec-e0dc-b5fc-ff21582041d4@rock-chips.com> (raw)
In-Reply-To: <20260406105613.1228673-1-18255117159@163.com>
在 2026/04/06 星期一 18:56, Hans Zhang 写道:
> This series refactors PCIe speed validation and conversion logic to
> shared functions in the public header, eliminating code duplication
> and ensuring consistency across drivers.
>
Reviewed-by: Shawn Lin <shawn.lin@rock-chips.com>
> ---
> Changes for v6:
> - missing one line of code:
> link_speed = pcie_get_link_speed(pci->max_link_speed);
>
> Changes for v5:
> https://patchwork.kernel.org/project/linux-pci/patch/20260406104708.1218648-1-18255117159@163.com/
>
> - Rebase to v7.0-rc1. (pci/next tree)
>
> Changes for v4:
> https://patchwork.kernel.org/project/linux-pci/patch/20251102143206.111347-1-18255117159@163.com/
>
> - Maintain O(1) array-based lookup for speed conversion (addressing
> performance concerns from v3 feedback)
> - Move pcie_valid_speed() and pci_bus_speed2lnkctl2() to pci.h
> - Update dwc driver to use the shared functions
> - Rebase to v6.18-rc3.
>
> This addresses the feedback from Lukas Wunner and Manivannan Sadhasivam
> on the v3 submission, ensuring no runtime performance regression while
> achieving code reuse.
>
> Changes for v3:
> https://patchwork.kernel.org/project/linux-pci/patch/20250816154633.338653-1-18255117159@163.com/
>
> - Rebase to v6.17-rc1.
> - Gentle ping.
>
> Changes for v2:
> - s/PCIE_SPEED2LNKCTL2_TLS_ENC/PCIE_SPEED2LNKCTL2_TLS
> - The patch commit message were modified.
> ---
>
> Hans Zhang (3):
> PCI: Add public pcie_valid_speed() for shared validation
> PCI: Move pci_bus_speed2lnkctl2() to public header
> PCI: dwc: Use common speed conversion function
>
> drivers/pci/controller/dwc/pcie-designware.c | 18 +++-------------
> drivers/pci/pci.h | 22 ++++++++++++++++++++
> drivers/pci/pcie/bwctrl.c | 22 --------------------
> 3 files changed, 25 insertions(+), 37 deletions(-)
>
>
> base-commit: 525e91d84dc085492b36d4b87abb7c1cc93fcb44
prev parent reply other threads:[~2026-04-07 0:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 10:56 Hans Zhang
2026-04-06 10:56 ` [PATCH v6 1/3] PCI: Add public pcie_valid_speed() for shared validation Hans Zhang
2026-04-06 10:56 ` [PATCH v6 2/3] PCI: Move pci_bus_speed2lnkctl2() to public header Hans Zhang
2026-04-06 10:56 ` [PATCH v6 3/3] PCI: dwc: Use common speed conversion function Hans Zhang
2026-04-07 8:25 ` Ilpo Järvinen
2026-04-07 12:19 ` Hans Zhang
2026-04-07 12:29 ` Ilpo Järvinen
2026-04-07 12:32 ` Hans Zhang
2026-04-07 0:36 ` Shawn Lin [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=0e7148cd-06ec-e0dc-b5fc-ff21582041d4@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=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®