From: Andrea della Porta <andrea.porta@suse.com>
To: Alex Elder <elder@riscstar.com>
Cc: Andrea della Porta <andrea.porta@suse.com>,
bhelgaas@google.com, lizhi.hou@amd.com, herve.codina@bootlin.com,
daniel@riscstar.com, mohdayaa@qti.qualcomm.com,
lbiancon@qti.qualcomm.com, mani@kernel.org, robh@kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] PCI: of: update endpoint ranges dynamically
Date: Fri, 9 Oct 2026 15:41:16 +0200 [thread overview]
Message-ID: <asju_HpgXpIyAFdf@apocalypse> (raw)
In-Reply-To: <223c5189-bfda-4c63-b09f-4ebd01bd144a@riscstar.com>
Hi Alex,
On 10:55 Thu 08 Oct , Alex Elder wrote:
> On 10/8/26 10:45 AM, Andrea della Porta wrote:
> > After a quick test, it seems that it's not working out of the
> > box on my RPi5. Let me investigate a bit to see what's wrong.
I stand corrected: it works perfectly. So:
Tested-by: Andrea della Porta <andrea.porta@suse.com>
I think it should even be possible to tweak the static RPi5
DT in order to make it work dynamically with your patch. Can
you please provide the relevant PCI DT nodes (from PCI controller
to pci-ep-bus endpoint) from the output of:
dtc -I fs -O dts /sys/firmware/devicetree/base/
taken on your reference board?
Many thanks for your work,
Andrea
>
> THANK YOU FOR TESTING THIS!!!
>
> My hope was that the recent change (to avoid doing any
> updating of ranges property unless it was found to be
> "empty") would avoid any trouble with the RPi5.
>
> I'm eager to hear what more you find. Please let me
> know if I can be of any other help.
>
> -Alex
prev parent reply other threads:[~2026-10-09 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 22:24 [PATCH v3 0/3] PCI: of: update endpoint ranges dynamically Alex Elder
2026-09-24 22:24 ` [PATCH v3 1/3] PCI: of: make a flags argument optional Alex Elder
2026-09-24 22:24 ` [PATCH v3 2/3] PCI: of: introduce of_pci_build_prop_ranges() Alex Elder
2026-10-09 10:43 ` Ilpo Järvinen
2026-09-24 22:24 ` [PATCH v3 3/3] PCI: of: introduce of_pci_update_endpoint_node_ranges() Alex Elder
2026-10-09 10:44 ` Ilpo Järvinen
2026-10-02 16:24 ` [PATCH v3 0/3] PCI: of: update endpoint ranges dynamically Alex Elder
2026-10-08 15:45 ` Andrea della Porta
2026-10-08 15:55 ` Alex Elder
2026-10-09 13:41 ` Andrea della Porta [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=asju_HpgXpIyAFdf@apocalypse \
--to=andrea.porta@suse.com \
--cc=bhelgaas@google.com \
--cc=daniel@riscstar.com \
--cc=elder@riscstar.com \
--cc=herve.codina@bootlin.com \
--cc=lbiancon@qti.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=mani@kernel.org \
--cc=mohdayaa@qti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox