From: Herve Codina <herve.codina@bootlin.com>
To: Alex Elder <elder@riscstar.com>
Cc: bhelgaas@google.com, robh@kernel.org, daniel@riscstar.com,
mohd.anwar@oss.qualcomm.com, lorenzo.bianconi@oss.qualcomm.com,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] PCI: of: warn on bogus device_type property
Date: Wed, 19 Aug 2026 12:22:26 +0200 [thread overview]
Message-ID: <20260819122226.6951c816@bootlin.com> (raw)
In-Reply-To: <20260812172247.276554-1-elder@riscstar.com>
Hi Alex,
Can you add me in Cc in all patches of the series for next iterations?
Best regards,
Hervé
On Wed, 12 Aug 2026 12:22:43 -0500
Alex Elder <elder@riscstar.com> wrote:
> The purpose of this series lies in its final patch, where a new check
> is added whenever a PCI devicetree node is found to already exist when
> one might otherwise be dynamically created.
>
> PCI has a well-defined bus and device discovery process. The
> PCI_DYNAMIC_OF_NODES Kconfig option allows PCI devices to *also*
> have a devicetree node. This enables certain things that are
> not possible with PCI enumeration alone.
>
> While working on a Qualcomm platform, I learned that some PCI
> endpoint nodes were defined with device_type = "pci" properties.
> Herve Codina pointed out that this was not correct. Rob Herring
> indicated that people seem to have trouble getting the PCI
> devicetree nodes right, and asked whether we could warn if this
> particular problem occurred.
>
> The last patch in this series implements that check and warning.
> The first three patches are fairly trivial changes to clean up
> some related code. This is the only changed patch since v1.
>
> -Alex
>
> Between version 1 and version 2:
> - Check the PCI devicetree node even when PCI_DYNAMIC_OF_NODES is
> not enabled
>
> Version 1 is available here:
> https://lore.kernel.org/lkml/20260807194100.455599-1-elder@riscstar.com/
>
> Alex Elder (4):
> PCI: of: drop the reg_num argument to of_pci_set_address()
> PCI: of: don't zero flags in of_pci_get_addr_flags()
> PCI: of: make a flags argument optional
> PCI: of: introduce of_pci_verify_node()
>
> drivers/pci/bus.c | 1 +
> drivers/pci/of.c | 26 ++++++++++++++++++++++++++
> drivers/pci/of_property.c | 20 ++++++++++----------
> drivers/pci/pci.h | 3 +++
> 4 files changed, 40 insertions(+), 10 deletions(-)
>
>
> base-commit: db2ddb87143519e20a95aa36c60b36107b736a58
prev parent reply other threads:[~2026-08-19 10:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 17:22 [PATCH v2 0/4] PCI: of: warn on bogus device_type property Alex Elder
2026-08-12 17:22 ` [PATCH v2 1/4] PCI: of: drop the reg_num argument to of_pci_set_address() Alex Elder
2026-08-12 17:28 ` sashiko-bot
2026-08-12 17:22 ` [PATCH v2 2/4] PCI: of: don't zero flags in of_pci_get_addr_flags() Alex Elder
2026-08-12 17:27 ` sashiko-bot
2026-08-12 17:22 ` [PATCH v2 3/4] PCI: of: make a flags argument optional Alex Elder
2026-08-12 17:29 ` sashiko-bot
2026-08-19 10:22 ` Herve Codina
2026-08-19 14:22 ` Alex Elder
2026-08-12 17:22 ` [PATCH v2 4/4] PCI: of: introduce of_pci_verify_node() Alex Elder
2026-08-12 17:28 ` sashiko-bot
2026-08-19 10:20 ` Herve Codina
2026-08-19 14:23 ` Alex Elder
2026-08-19 10:22 ` Herve Codina [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=20260819122226.6951c816@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=bhelgaas@google.com \
--cc=daniel@riscstar.com \
--cc=devicetree@vger.kernel.org \
--cc=elder@riscstar.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.bianconi@oss.qualcomm.com \
--cc=mohd.anwar@oss.qualcomm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.