From: Alex Elder <elder@riscstar.com>
To: Rob Herring <robh@kernel.org>
Cc: sashiko-reviews@lists.linux.dev, linux-pci@vger.kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/4] PCI: of: introduce of_pci_verify_node()
Date: Fri, 4 Sep 2026 08:45:16 -0500 [thread overview]
Message-ID: <453211e7-7ca4-424b-b1a4-745f0f8624dc@riscstar.com> (raw)
In-Reply-To: <58452803-d22b-4e9a-8716-db46798d6403@riscstar.com>
On 9/2/26 7:54 AM, Alex Elder wrote:
>>> I would love to get some pointers from others on how to
>>> do this correctly, but in any case I'll do a little more
>>> research on this before I post version 4.
>>
>> I'm willing to wait and see if anyone cares about cardbus. I doubt it.
>> Maybe there's some old PowerBooks with cardbus?
>
> I'll give it another few days before posting v4.
>
>> "pciex" should probably be handled.
>
> I'll add that. I'll also try to find what the range
> of "compliant" device types is; I presume it's in the
> devicetree spec.
I'm about to send v4 of this series. Here is some information on
this suggestion:
- "cardbus" is referenced in two places (two very similar functions,
one for PowerPC and one for SPARC.
of_create_pci_dev() in "arch/powerpc/kernel/pci_of_scan.c"
of_create_pci_dev() in "arch/sparc/kernel/pci.c"
Based on the tone of your earlier comment, I'll ignore "cardbus".
- "pciex" is checked in 6 places, one of which is generic (the other
five are related to the above two architectures). The generic
one is in of_bus_pci_match(), mentioned earlier.
Sashiko's suggestion only mentioned those two device_type values.
I'll just add a test for "pciex" as you suggested.
Herve, I will retain your "reviewed-by" tag; if you disagree with
this minor change say so and I'll remove it in v5.
-Alex
next prev parent reply other threads:[~2026-09-04 13:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 1:13 [PATCH v3 0/4] PCI: of: warn on bogus device_type property Alex Elder
2026-09-01 1:13 ` [PATCH v3 1/4] PCI: of: drop the reg_num argument to of_pci_set_address() Alex Elder
2026-09-01 1:16 ` sashiko-bot
2026-09-01 1:13 ` [PATCH v3 2/4] PCI: of: don't zero flags in of_pci_get_addr_flags() Alex Elder
2026-09-01 1:20 ` sashiko-bot
2026-09-01 2:42 ` Alex Elder
2026-09-01 1:13 ` [PATCH v3 3/4] PCI: of: introduce of_pci_verify_node() Alex Elder
2026-09-01 1:21 ` sashiko-bot
2026-09-01 2:42 ` Alex Elder
2026-09-01 17:32 ` Rob Herring
2026-09-02 12:54 ` Alex Elder
2026-09-04 13:45 ` Alex Elder [this message]
2026-09-01 6:11 ` Herve Codina
2026-09-01 1:13 ` [PATCH v3 4/4] of: address: kill of_node_is_pcie() Alex Elder
2026-09-01 1:18 ` sashiko-bot
2026-09-01 2:03 ` Alex Elder
2026-09-01 6:45 ` Herve Codina
2026-09-01 14:58 ` Alex Elder
2026-09-01 15:15 ` Herve Codina
2026-09-01 15:25 ` Alex Elder
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=453211e7-7ca4-424b-b1a4-745f0f8624dc@riscstar.com \
--to=elder@riscstar.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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