U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Harrison Mutai <harrison.mutai@arm.com>
To: Tom Rini <trini@konsulko.com>
Cc: David Feng <fenghua@phytium.com.cn>,
	Linus Walleij <linus.walleij@linaro.org>,
	Peter Hoyes <Peter.Hoyes@arm.com>,
	Liviu Dudau <liviu.dudau@foss.arm.com>,
	nd@arm.com, andre.przywara@arm.com, manish.pandey2@arm.com,
	u-boot@lists.denx.de
Subject: Re: [PATCH 4/4] board: vexpress64: enable bloblist for SPL handoff
Date: Thu, 19 Dec 2024 16:04:04 +0000	[thread overview]
Message-ID: <8eaca7d1-2cce-475f-93c1-4023ea30a843@arm.com> (raw)
In-Reply-To: <20241218163126.GG1505244@bill-the-cat>

On 18/12/2024 16:31, Tom Rini wrote:
> On Wed, Dec 18, 2024 at 03:39:31PM +0000, Harrison Mutai wrote:
> 
>> Enable bloblist on vexpress64 platforms to facilitate information
>> passing from TF-A using the firmware handoff framework.
>>
>> Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>
> [snip]
>> diff --git a/configs/vexpress_fvp_bloblist_defconfig b/configs/vexpress_fvp_bloblist_defconfig
>> new file mode 100644
>> index 0000000000..dcc87db872
>> --- /dev/null
>> +++ b/configs/vexpress_fvp_bloblist_defconfig
>> @@ -0,0 +1,5 @@
>> +#include <configs/vexpress_fvp_defconfig>
>> +
>> +CONFIG_BLOBLIST=y
>> +CONFIG_BLOBLIST_PASSAGE=y
>> +CONFIG_BLOBLIST_SIZE_RELOC=0x10000
> 
> I wonder if this means we should also do:
> 
> diff --git a/common/Kconfig b/common/Kconfig
> index 11066ec64315..cca33ed28f32 100644
> --- a/common/Kconfig
> +++ b/common/Kconfig
> @@ -1087,7 +1087,6 @@ config BLOBLIST_SIZE
>   config BLOBLIST_SIZE_RELOC
>   	hex "Size of bloblist after relocation"
>   	default BLOBLIST_SIZE if BLOBLIST_FIXED || BLOBLIST_ALLOC
> -	default 0x0 if BLOBLIST_PASSAGE
>   	default 0x20000 if (ARM && EFI_LOADER && GENERATE_ACPI_TABLE)
>   	help
>   	  Sets the size of the bloblist in bytes after relocation. Since U-Boot
> 
> Because in this case we do need to set the size of the bloblist we use
> internally to non-zero?
> 
That makes sense. The relocation in board_f will fail, as 
reserve_bloblist relies on this value being non-zero. However, if 
CONFIG_BLOBLIST_PASSAGE implies GD_FLG_SKIP_RELOC, then the relocation 
may not be necessary?

  reply	other threads:[~2024-12-19 16:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241218153933.37649-1-harrison.mutai@arm.com>
2024-12-18 15:39 ` [PATCH 1/4] bloblist: fix typo in code comments Harrison Mutai
2024-12-18 15:48   ` Tom Rini
2024-12-18 17:23     ` Harrison Mutai
2024-12-18 17:30       ` Tom Rini
2024-12-18 15:39 ` [PATCH 2/4] board: vexpress64: default to hardware device tree Harrison Mutai
2024-12-27  8:25   ` Linus Walleij
2024-12-18 15:39 ` [PATCH 3/4] bloblist: add support for CONFIG_BLOBLIST_PASSAGE Harrison Mutai
2024-12-18 16:21   ` Tom Rini
2024-12-18 15:39 ` [PATCH 4/4] board: vexpress64: enable bloblist for SPL handoff Harrison Mutai
2024-12-18 16:31   ` Tom Rini
2024-12-19 16:04     ` Harrison Mutai [this message]
2024-12-27 16:19       ` Tom Rini
2025-02-04 17:58 [PATCH v3 0/4] Enable bloblist support on Vexpress64 Harrison Mutai
2025-02-04 17:58 ` [PATCH 4/4] board: vexpress64: enable bloblist for SPL handoff Harrison Mutai

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=8eaca7d1-2cce-475f-93c1-4023ea30a843@arm.com \
    --to=harrison.mutai@arm.com \
    --cc=Peter.Hoyes@arm.com \
    --cc=andre.przywara@arm.com \
    --cc=fenghua@phytium.com.cn \
    --cc=linus.walleij@linaro.org \
    --cc=liviu.dudau@foss.arm.com \
    --cc=manish.pandey2@arm.com \
    --cc=nd@arm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox