From: Torsten Duwe <duwe@lst.de>
To: Simon Glass <sjg@chromium.org>
Cc: "Peter Robinson" <pbrobinson@gmail.com>,
"Matthias Brugger" <mbrugger@suse.com>,
"Bin Meng" <bmeng.cn@gmail.com>,
"Andrew Goodbody" <andrew.goodbody@linaro.org>,
"Tom Rini" <trini@konsulko.com>,
"Andrea della Porta" <andrea.porta@suse.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Jan Čermák" <sairon@sairon.cz>,
u-boot@lists.denx.de
Subject: Re: [PATCH 1/3] core: Skip parent device nodes without a DT reference when looking for dma-ranges
Date: Fri, 8 May 2026 21:42:22 +0200 [thread overview]
Message-ID: <20260508214222.642b15cb@lst.de> (raw)
In-Reply-To: <CAFLszTgaG8RV=kWgr7Gu3tkVniq5pNVQ7RSUEv2EMyyQ4ALO6Q@mail.gmail.com>
On Fri, 8 May 2026 12:47:45 -0600
Simon Glass <sjg@chromium.org> wrote:
[...]
> There's already a unit test for device_get_dma_constraints() in
> test/dm/read.c (dm_test_dma_ranges). Since you are extending it to
> walk past nodes without an ofnode, please can you add a case
> exercising the new path - a sandbox device whose immediate parent has
> no DT reference should do it.
I'll have a look.
Talking unit tests, is it just me who experiences reproducible crashes
on RPi5 with today's master branch?
Torsten
next prev parent reply other threads:[~2026-05-08 19:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 15:41 [PATCH 0/3] Fix NVMe, not only on Raspberry Pi 5 Torsten Duwe
2026-05-08 15:42 ` [PATCH 1/3] core: Skip parent device nodes without a DT reference when looking for dma-ranges Torsten Duwe
2026-05-08 18:47 ` Simon Glass
2026-05-08 19:42 ` Torsten Duwe [this message]
2026-05-08 19:56 ` Peter Robinson
2026-05-08 23:36 ` Simon Glass
2026-05-09 15:29 ` Peter Robinson
2026-05-08 15:42 ` [PATCH 2/3] nvme: Fix missing address translation for PCIe inbound access Torsten Duwe
2026-05-09 15:28 ` Peter Robinson
2026-05-11 14:50 ` Neil Armstrong
2026-05-12 9:30 ` Torsten Duwe
2026-05-12 9:34 ` Neil Armstrong
2026-05-08 15:42 ` [PATCH 3/3] configs: enable NVMe Torsten Duwe
2026-05-08 18:00 ` Peter Robinson
2026-05-09 15:27 ` Peter Robinson
2026-05-09 15:31 ` [PATCH 0/3] Fix NVMe, not only on Raspberry Pi 5 Peter Robinson
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=20260508214222.642b15cb@lst.de \
--to=duwe@lst.de \
--cc=andrea.porta@suse.com \
--cc=andrew.goodbody@linaro.org \
--cc=bmeng.cn@gmail.com \
--cc=mbrugger@suse.com \
--cc=neil.armstrong@linaro.org \
--cc=pbrobinson@gmail.com \
--cc=sairon@sairon.cz \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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.