From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Hans Zhang <18255117159@163.com>
Cc: lpieralisi@kernel.org, bhelgaas@google.com,
manivannan.sadhasivam@linaro.org, kw@linux.com,
cassel@kernel.org, robh@kernel.org, jingoohan1@gmail.com,
linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v12 4/6] PCI: dwc: Use common PCI host bridge APIs for finding the capabilities
Date: Tue, 3 Jun 2025 12:42:33 +0300 (EEST) [thread overview]
Message-ID: <4f23df8e-bebe-149c-a638-be7208c8c71a@linux.intel.com> (raw)
In-Reply-To: <20250514161258.93844-5-18255117159@163.com>
On Thu, 15 May 2025, Hans Zhang wrote:
> Use the PCI core is now exposing generic macros for the host bridges to
> search for the PCIe capabilities, make use of them in the DWC driver.
>
> Signed-off-by: Hans Zhang <18255117159@163.com>
> ---
> Changes since v11:
> - Resolve compilation errors. s/dw_pcie_read_dbi/dw_pcie_read*_dbi
>
> Changes since v10:
> - None
>
> Changes since v9:
> - Resolved [v9 4/6] compilation error.
> The latest 6.15 rc1 merge __dw_pcie_find_vsec_capability, which uses
> dw_pcie_find_next_ext_capability.
>
> Changes since v8:
> - None
>
> Changes since v7:
> - Resolve compilation errors.
>
> Changes since v6:
> https://lore.kernel.org/linux-pci/20250323164852.430546-3-18255117159@163.com/
>
> - The patch commit message were modified.
>
> Changes since v5:
> https://lore.kernel.org/linux-pci/20250321163803.391056-3-18255117159@163.com/
>
> - Kconfig add "select PCI_HOST_HELPERS"
> ---
> drivers/pci/controller/dwc/pcie-designware.c | 81 ++++----------------
> 1 file changed, 14 insertions(+), 67 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/pcie-designware.c b/drivers/pci/controller/dwc/pcie-designware.c
> index 97d76d3dc066..7939411a24eb 100644
> --- a/drivers/pci/controller/dwc/pcie-designware.c
> +++ b/drivers/pci/controller/dwc/pcie-designware.c
> @@ -205,83 +205,30 @@ void dw_pcie_version_detect(struct dw_pcie *pci)
> pci->type = ver;
> }
>
> -/*
> - * These interfaces resemble the pci_find_*capability() interfaces, but these
> - * are for configuring host controllers, which are bridges *to* PCI devices but
> - * are not PCI devices themselves.
> - */
> -static u8 __dw_pcie_find_next_cap(struct dw_pcie *pci, u8 cap_ptr,
> - u8 cap)
> +static int dw_pcie_read_cfg(void *priv, int where, int size, u32 *val)
> {
> - u8 cap_id, next_cap_ptr;
> - u16 reg;
> -
> - if (!cap_ptr)
> - return 0;
> + struct dw_pcie *pci = priv;
>
> - reg = dw_pcie_readw_dbi(pci, cap_ptr);
> - cap_id = (reg & 0x00ff);
> -
> - if (cap_id > PCI_CAP_ID_MAX)
> - return 0;
> -
> - if (cap_id == cap)
> - return cap_ptr;
> + if (size == 4)
> + *val = dw_pcie_readl_dbi(pci, where);
> + else if (size == 2)
> + *val = dw_pcie_readw_dbi(pci, where);
> + else if (size == 1)
> + *val = dw_pcie_readb_dbi(pci, where);
Maybe here as well return error if the given size is invalid.
>
> - next_cap_ptr = (reg & 0xff00) >> 8;
> - return __dw_pcie_find_next_cap(pci, next_cap_ptr, cap);
> + return PCIBIOS_SUCCESSFUL;
> }
>
> u8 dw_pcie_find_capability(struct dw_pcie *pci, u8 cap)
> {
> - u8 next_cap_ptr;
> - u16 reg;
> -
> - reg = dw_pcie_readw_dbi(pci, PCI_CAPABILITY_LIST);
> - next_cap_ptr = (reg & 0x00ff);
> -
> - return __dw_pcie_find_next_cap(pci, next_cap_ptr, cap);
> + return PCI_FIND_NEXT_CAP_TTL(dw_pcie_read_cfg, PCI_CAPABILITY_LIST, cap,
> + pci);
> }
> EXPORT_SYMBOL_GPL(dw_pcie_find_capability);
>
> -static u16 dw_pcie_find_next_ext_capability(struct dw_pcie *pci, u16 start,
> - u8 cap)
> -{
> - u32 header;
> - int ttl;
> - int pos = PCI_CFG_SPACE_SIZE;
> -
> - /* minimum 8 bytes per capability */
> - ttl = (PCI_CFG_SPACE_EXP_SIZE - PCI_CFG_SPACE_SIZE) / 8;
> -
> - if (start)
> - pos = start;
> -
> - header = dw_pcie_readl_dbi(pci, pos);
> - /*
> - * If we have no capabilities, this is indicated by cap ID,
> - * cap version and next pointer all being 0.
> - */
> - if (header == 0)
> - return 0;
> -
> - while (ttl-- > 0) {
> - if (PCI_EXT_CAP_ID(header) == cap && pos != start)
> - return pos;
> -
> - pos = PCI_EXT_CAP_NEXT(header);
> - if (pos < PCI_CFG_SPACE_SIZE)
> - break;
> -
> - header = dw_pcie_readl_dbi(pci, pos);
> - }
> -
> - return 0;
> -}
> -
> u16 dw_pcie_find_ext_capability(struct dw_pcie *pci, u8 cap)
> {
> - return dw_pcie_find_next_ext_capability(pci, 0, cap);
> + return PCI_FIND_NEXT_EXT_CAPABILITY(dw_pcie_read_cfg, 0, cap, pci);
> }
> EXPORT_SYMBOL_GPL(dw_pcie_find_ext_capability);
>
> @@ -294,8 +241,8 @@ static u16 __dw_pcie_find_vsec_capability(struct dw_pcie *pci, u16 vendor_id,
> if (vendor_id != dw_pcie_readw_dbi(pci, PCI_VENDOR_ID))
> return 0;
>
> - while ((vsec = dw_pcie_find_next_ext_capability(pci, vsec,
> - PCI_EXT_CAP_ID_VNDR))) {
> + while ((vsec = PCI_FIND_NEXT_EXT_CAPABILITY(
> + dw_pcie_read_cfg, vsec, PCI_EXT_CAP_ID_VNDR, pci))) {
Start the arguments from the first line and align the continuations to (.
> header = dw_pcie_readl_dbi(pci, vsec + PCI_VNDR_HEADER);
> if (PCI_VNDR_HEADER_ID(header) == vsec_id)
> return vsec;
>
--
i.
next prev parent reply other threads:[~2025-06-03 9:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 16:12 [PATCH v12 0/6] Refactor capability search into common macros Hans Zhang
2025-05-14 16:12 ` [PATCH v12 1/6] PCI: Introduce generic bus config read helper function Hans Zhang
2025-06-03 9:18 ` Ilpo Järvinen
2025-06-03 9:21 ` Ilpo Järvinen
2025-06-03 15:41 ` Hans Zhang
2025-06-03 15:40 ` Hans Zhang
2025-05-14 16:12 ` [PATCH v12 2/6] PCI: Clean up __pci_find_next_cap_ttl() readability Hans Zhang
2025-06-03 9:30 ` Ilpo Järvinen
2025-06-03 15:42 ` Hans Zhang
2025-05-14 16:12 ` [PATCH v12 3/6] PCI: Refactor capability search into common macros Hans Zhang
2025-06-03 9:38 ` Ilpo Järvinen
2025-06-03 15:55 ` Hans Zhang
2025-05-14 16:12 ` [PATCH v12 4/6] PCI: dwc: Use common PCI host bridge APIs for finding the capabilities Hans Zhang
2025-06-03 9:42 ` Ilpo Järvinen [this message]
2025-06-03 15:58 ` Hans Zhang
2025-05-14 16:12 ` [PATCH v12 5/6] PCI: cadence: " Hans Zhang
2025-05-14 16:12 ` [PATCH v12 6/6] PCI: cadence: Use cdns_pcie_find_*capability to avoid hardcode Hans Zhang
2025-06-03 9:49 ` Ilpo Järvinen
2025-06-03 16:00 ` Hans Zhang
2025-05-26 14:53 ` [PATCH v12 0/6] Refactor capability search into common macros Hans Zhang
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=4f23df8e-bebe-149c-a638-be7208c8c71a@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.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;
as well as URLs for NNTP newsgroup(s).