From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: "Raymond Mao" <raymond.mao@linaro.org>,
"U-Boot Mailing List" <u-boot@lists.denx.de>,
"Andrew Goodbody" <andrew.goodbody@linaro.org>,
"Caleb Connolly" <caleb.connolly@linaro.org>,
"Evgeny Bachinin" <EABachinin@salutedevices.com>,
"Harrison Mutai" <harrison.mutai@arm.com>,
"Jan Kiszka" <jan.kiszka@siemens.com>,
"Jerry Van Baren" <vanbaren@cideas.com>,
"Lad Prabhakar" <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"Levi Yun" <yeoreum.yun@arm.com>,
"Marek Behún" <kabel@kernel.org>,
"Marek Vasut" <marek.vasut+renesas@mailbox.org>,
"Marek Vasut" <marex@denx.de>,
"Matthias Brugger" <mbrugger@suse.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Patrick Rudolph" <patrick.rudolph@9elements.com>,
"Quentin Schulz" <quentin.schulz@cherry.de>,
"Sumit Garg" <sumit.garg@kernel.org>,
"This contributor prefers not to receive mails"
<noreply@example.com>, mason1920 <mason1920@use.startmail.com>
Subject: Re: [PATCH 0/4] bloblist: fdt: Clean up the code
Date: Fri, 4 Apr 2025 11:55:35 -0600 [thread overview]
Message-ID: <20250404175535.GT5495@bill-the-cat> (raw)
In-Reply-To: <CAFLszTjo8HEzKbZAbO=neF57e69vGbWYsDVV_dD=kO6j_VH39w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3530 bytes --]
On Sat, Apr 05, 2025 at 06:40:08AM +1300, Simon Glass wrote:
> Hi Raymond,
>
> On Sat, 5 Apr 2025 at 03:49, Raymond Mao <raymond.mao@linaro.org> wrote:
> >
> > Hi Tom and Simon,
> >
> > On Fri, 28 Mar 2025 at 21:00, Raymond Mao <raymond.mao@linaro.org> wrote:
> > >
> > > Hi Tom and Simon,
> > >
> > > On Fri, 28 Mar 2025 at 20:02, Tom Rini <trini@konsulko.com> wrote:
> > > >
> > > > On Fri, Mar 28, 2025 at 11:38:14PM +0000, Simon Glass wrote:
> > > > > Hi Tom,
> > > > >
> > > > > On Fri, 28 Mar 2025 at 10:18, Tom Rini <trini@konsulko.com> wrote:
> > > > > >
> > > > > > On Fri, Mar 28, 2025 at 09:43:54AM -0600, Simon Glass wrote:
> > > > > >
> > > > > > > The bloblist code took what I consider to be a wrong turn a year or so
> > > > > > > ago. As discussed with Tom, this series proposes a way to arrange things
> > > > > > > so that it is simpler to understand and manage.
> > > > > > >
> > > > > > > - Unwind some of the nesting in bloblist_init()
> > > > > > > - Avoid needing to init the bloblist just to get the FDT
> > > > > > > - Create a deterministic OF_BLOBLIST option rather than using guesswork
> > > > > > >
> > > > > > > It is to be hoped that we can get a platform which uses OF_BLOBLIST into
> > > > > > > CI at some point. In the meantime, the standard passage series[1] could
> > > > > > > be resurrected to give some coverage.
> > > > > > >
> > > > > > > [1] https://patchwork.ozlabs.org/project/uboot/list/?series=281465&state=*
> > > > > >
> > > > > > Based on how it's documented to be run in
> > > > > > doc/board/armltd/vexpress64.rst in the next branch, have you confirmed
> > > > > > that platforms using the handoff spec still work?
> > > > >
> > > > > I believe so, yes. I don't have that board to test it though. Raymond
> > > > > may be able to test this series on QEMU?
> > > >
> > > > I was pointing you at the docs so that you would have access to testing
> > > > it. That's part of the docs, running the emulator.
> > > >
> > >
> > > I can help to test the firmware handoff on qemu.
> > > I have all the necessary changes and unit tests for the OP-TEE repo
> > > qemu v8 build to test this.
> > > I will try to find some time early next week to review and test this
> > > series before turning back to you.
> > >
> >
> > Just a follow-up on the testing with TF-A and OP-TEE.
> > Unfortunately, the patch series breaks the transfer list handoff to
> > U-Boot completely and just end up with below error when U-Boot boots:
> > ```
> > No valid device tree binary found at 0000000000000000
> > initcall failed at call 0000000060097bcc (err=-2)
> > ### ERROR ### Please RESET the board ###
> > ```
> >
> > U-Boot test version:
> > 'next' branch + this series + my patch [1] to point fdt_addr to gd->fdt_blob.
> >
> > [1]: https://lore.kernel.org/u-boot/20250331224011.2734284-2-raymond.mao@linaro.org/
>
> I suppose the FDT address in the register is not being read correctly.
>
> Do you have a test case for this, e.g. in QEMU? Even if it is just
> binary blobs for now, not suitable for CI, I'd like to get it in my
> lab.
>
> I did create a test back when I did standard passage, but that series
> seems to have not been applied. I'll see if I can resurrect it.
This problem should also be visible with running vexpress64 as
documented in doc/board/armltd/vexpress64.rst which is not yet in CI
(it's straight forward but non-trivial), which is why I was asking about
it earlier in the thread.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-04-04 17:55 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 15:43 [PATCH 0/4] bloblist: fdt: Clean up the code Simon Glass
2025-03-28 15:43 ` [PATCH 1/4] bloblist: Simplify bloblist init Simon Glass
2025-03-28 15:43 ` [PATCH 2/4] fdt: Introduce OF_BLOBLIST Simon Glass
2025-04-03 15:34 ` Raymond Mao
2025-04-03 17:57 ` Simon Glass
2025-03-28 15:43 ` [PATCH 3/4] bloblist: Provide access to the FDT address Simon Glass
2025-03-28 15:43 ` [PATCH 4/4] fdt: Obtain the FDT from bloblist without parsing it Simon Glass
2025-03-28 16:18 ` [PATCH 0/4] bloblist: fdt: Clean up the code Tom Rini
2025-03-28 23:38 ` Simon Glass
2025-03-29 0:02 ` Tom Rini
2025-03-29 1:00 ` Raymond Mao
2025-04-04 14:48 ` Raymond Mao
2025-04-04 14:53 ` Raymond Mao
2025-04-04 17:40 ` Simon Glass
2025-04-04 17:55 ` Tom Rini [this message]
2025-04-04 18:09 ` Raymond Mao
2025-04-06 22:06 ` Simon Glass
2025-04-06 22:35 ` Tom Rini
2025-04-07 14:07 ` Raymond Mao
2025-04-13 21:13 ` Simon Glass
2025-04-14 13:07 ` Raymond Mao
2025-04-14 19:34 ` Simon Glass
2025-04-14 19:43 ` Raymond Mao
2025-04-14 20:05 ` Simon Glass
2025-04-14 20:16 ` Raymond Mao
2025-04-14 20:41 ` Simon Glass
2025-04-14 20:47 ` Simon Glass
2025-04-15 0:32 ` Raymond Mao
2025-04-17 13:14 ` Simon Glass
2025-04-03 14:09 ` Raymond Mao
2025-04-03 17:57 ` Simon Glass
2025-04-03 18:12 ` Raymond Mao
2025-04-03 18:18 ` Simon Glass
2025-04-03 19:54 ` Raymond Mao
2025-04-03 20:40 ` Simon Glass
2025-04-03 21:52 ` Tom Rini
2025-04-03 22:41 ` Simon Glass
2025-04-03 22:50 ` Tom Rini
2025-04-04 17:39 ` Simon Glass
2025-04-04 17:57 ` Tom Rini
2025-04-06 22:06 ` Simon Glass
2025-04-06 22:38 ` Tom Rini
2025-04-07 0:35 ` Simon Glass
2025-04-07 14:30 ` Tom Rini
2025-04-07 15:24 ` Simon Glass
2025-04-07 18:22 ` Tom Rini
2025-04-07 20:17 ` Simon Glass
2025-04-07 20:34 ` Tom Rini
2025-04-14 19:34 ` Simon Glass
2025-04-14 20:34 ` Tom Rini
2025-04-17 13:14 ` Simon Glass
2025-04-17 14:14 ` Tom Rini
2025-04-17 21:24 ` Simon Glass
2025-04-17 21:58 ` Tom Rini
2025-04-17 22:02 ` Simon Glass
2025-04-17 22:14 ` Tom Rini
2025-04-17 22:28 ` Simon Glass
2025-04-17 22:37 ` Tom Rini
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=20250404175535.GT5495@bill-the-cat \
--to=trini@konsulko.com \
--cc=EABachinin@salutedevices.com \
--cc=andrew.goodbody@linaro.org \
--cc=caleb.connolly@linaro.org \
--cc=harrison.mutai@arm.com \
--cc=jan.kiszka@siemens.com \
--cc=kabel@kernel.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=marex@denx.de \
--cc=mason1920@use.startmail.com \
--cc=mbrugger@suse.com \
--cc=neil.armstrong@linaro.org \
--cc=noreply@example.com \
--cc=patrick.rudolph@9elements.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=quentin.schulz@cherry.de \
--cc=raymond.mao@linaro.org \
--cc=sjg@chromium.org \
--cc=sumit.garg@kernel.org \
--cc=u-boot@lists.denx.de \
--cc=vanbaren@cideas.com \
--cc=yeoreum.yun@arm.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