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,
thomas.richard@bootlin.com, linux-pci@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v10 2/6] PCI: Clean up __pci_find_next_cap_ttl() readability
Date: Tue, 29 Apr 2025 18:17:57 +0300 (EEST) [thread overview]
Message-ID: <66cdb108-80f5-fe7c-329b-8c60caf55b64@linux.intel.com> (raw)
In-Reply-To: <20250429125036.88060-3-18255117159@163.com>
On Tue, 29 Apr 2025, Hans Zhang wrote:
> Refactor the __pci_find_next_cap_ttl() to improve code clarity:
> - Replace magic number 0x40 with PCI_STD_HEADER_SIZEOF.
> - Use ALIGN_DOWN() for position alignment instead of manual bitmask.
> - Extract PCI capability fields via FIELD_GET() with standardized masks.
> - Add necessary headers (linux/align.h, uapi/linux/pci_regs.h).
>
> The changes are purely non-functional cleanups, ensuring behavior remains
> identical to the original implementation.
>
> Signed-off-by: Hans Zhang <18255117159@163.com>
> ---
> Changes since v9:
> - None
>
> Changes since v8:
> - Split into patch 1/6, patch 2/6.
> - The
> drivers/pci/pci.c | 10 ++++++----
> include/uapi/linux/pci_regs.h | 2 ++
> 2 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index 4d7c9f64ea24..1c29e8f20cb5 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -9,6 +9,7 @@
> */
>
> #include <linux/acpi.h>
> +#include <linux/align.h>
> #include <linux/kernel.h>
> #include <linux/delay.h>
> #include <linux/dmi.h>
> @@ -30,6 +31,7 @@
> #include <asm/dma.h>
> #include <linux/aer.h>
> #include <linux/bitfield.h>
> +#include <uapi/linux/pci_regs.h>
linux/pci.h will pull this in through <uapi/linux/pci.h> so you don't need
to add it (basically anywhere).
> #include "pci.h"
>
> DEFINE_MUTEX(pci_slot_mutex);
> @@ -432,17 +434,17 @@ static u8 __pci_find_next_cap_ttl(struct pci_bus *bus, unsigned int devfn,
> pci_bus_read_config_byte(bus, devfn, pos, &pos);
>
> while ((*ttl)--) {
> - if (pos < 0x40)
> + if (pos < PCI_STD_HEADER_SIZEOF)
> break;
> - pos &= ~3;
> + pos = ALIGN_DOWN(pos, 4);
> pci_bus_read_config_word(bus, devfn, pos, &ent);
>
> - id = ent & 0xff;
> + id = FIELD_GET(PCI_CAP_ID_MASK, ent);
> if (id == 0xff)
> break;
> if (id == cap)
> return pos;
> - pos = (ent >> 8);
> + pos = FIELD_GET(PCI_CAP_LIST_NEXT_MASK, ent);
> }
> return 0;
> }
> diff --git a/include/uapi/linux/pci_regs.h b/include/uapi/linux/pci_regs.h
> index ba326710f9c8..b59179e1210a 100644
> --- a/include/uapi/linux/pci_regs.h
> +++ b/include/uapi/linux/pci_regs.h
> @@ -206,6 +206,8 @@
> /* 0x48-0x7f reserved */
>
> /* Capability lists */
> +#define PCI_CAP_ID_MASK 0x00ff
> +#define PCI_CAP_LIST_NEXT_MASK 0xff00
Consider adding a comment after the value as is done for most defines in
this file.
>
> #define PCI_CAP_LIST_ID 0 /* Capability ID */
> #define PCI_CAP_ID_PM 0x01 /* Power Management */
>
--
i.
next prev parent reply other threads:[~2025-04-29 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 12:50 [PATCH v10 0/6] Refactor capability search into common macros Hans Zhang
2025-04-29 12:50 ` [PATCH v10 1/6] PCI: Introduce generic bus config read helper function Hans Zhang
2025-04-29 12:50 ` [PATCH v10 2/6] PCI: Clean up __pci_find_next_cap_ttl() readability Hans Zhang
2025-04-29 15:17 ` Ilpo Järvinen [this message]
2025-04-29 15:23 ` Hans Zhang
2025-04-29 15:26 ` Hans Zhang
2025-04-29 12:50 ` [PATCH v10 3/6] PCI: Refactor capability search into common macros Hans Zhang
2025-04-30 8:03 ` Ilpo Järvinen
2025-04-30 15:49 ` Hans Zhang
2025-04-29 12:50 ` [PATCH v10 4/6] PCI: dwc: Use common PCI host bridge APIs for finding the capabilities Hans Zhang
2025-04-29 12:50 ` [PATCH v10 5/6] PCI: cadence: " Hans Zhang
2025-04-29 12:50 ` [PATCH v10 6/6] PCI: cadence: Use cdns_pcie_find_*capability to avoid hardcode 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=66cdb108-80f5-fe7c-329b-8c60caf55b64@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 \
--cc=thomas.richard@bootlin.com \
/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