All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Rasmus Villemoes <ravi@prevas.dk>, meta-arm@lists.yoctoproject.org
Cc: Jon Mason <jon.mason@arm.com>, Jan Luebbe <jlu@pengutronix.de>
Subject: Re: [PATCH 2/2] optee-ftpm: rewrite its optee-os bbappend to use EARLY_TA_PATHS bitbake variable
Date: Fri, 4 Sep 2026 11:47:18 +0200	[thread overview]
Message-ID: <52828337-83b7-41f9-86f6-4fa72e00f877@siemens.com> (raw)
In-Reply-To: <87ld9h9x3t.fsf@prevas.dk>

On 04.09.26 11:36, Rasmus Villemoes wrote:
> On Thu, Aug 27 2026, Jan Kiszka <jan.kiszka@siemens.com> wrote:
> 
>> On 27.08.26 15:37, Rasmus Villemoes wrote:
>>> From: Rasmus Villemoes <ravi@prevas.dk>
>>>
>>> If anything else in the BSP also wants or needs to add an early TA to
>>> optee, that will conflict with this .bbappend adding its own
>>> EARLY_TA_PATHS="..." argument to EXTRA_OEMAKE.
>>>
>>> Instead, add the path to the ftpm TA to the newly introduced
>>> EARLY_TA_PATHS bitbake variable, which the main recipe will use to
>>> produce the make argument.
>>>
>>> Passing CFG_EARLY_TA=y explicitly is not needed, as optee-os' build
>>> system sets that automatically if the EARLY_TA_PATHS list is
>>> non-empty.
>>>
>>> CFG_CORE_HEAP_SIZE is somewhat harder to make play along nicely with
>>> other .bbappends that might have an opinion on its proper (minimum)
>>> value. For now, keep adding it explicitly to EXTRA_OEMAKE.
>>>
>>> Signed-off-by: Rasmus Villemoes <ravi@prevas.dk>
>>> ---
>>>  .../recipes-security/optee-ftpm/optee-os_%.bbappend    | 10 +++++-----
>>>  1 file changed, 5 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/meta-arm/recipes-security/optee-ftpm/optee-os_%.bbappend b/meta-arm/recipes-security/optee-ftpm/optee-os_%.bbappend
>>> index 92c11157..74bde25e 100644
>>> --- a/meta-arm/recipes-security/optee-ftpm/optee-os_%.bbappend
>>> +++ b/meta-arm/recipes-security/optee-ftpm/optee-os_%.bbappend
>>> @@ -4,8 +4,8 @@ DEPENDS:append = "\
>>>      ${@bb.utils.contains('MACHINE_FEATURES', 'optee-ftpm', 'optee-ftpm', '' , d)} \
>>>  "
>>>  
>>> -EXTRA_OEMAKE:append = "\
>>> -    ${@bb.utils.contains('MACHINE_FEATURES', 'optee-ftpm', \
>>> -        'CFG_CORE_HEAP_SIZE=131072 CFG_EARLY_TA=y EARLY_TA_PATHS="${STAGING_DIR_TARGET}/${base_libdir}/optee_armtz/${FTPM_UUID}.stripped.elf"', \
>>> -        '', d)} \
>>> -"
>>> +python() {
>>> +    if bb.utils.contains('MACHINE_FEATURES', 'optee-ftpm', True, False, d):
>>> +        d.appendVar('EARLY_TA_PATHS', ' ${STAGING_DIR_TARGET}/${base_libdir}/optee_armtz/${FTPM_UUID}.stripped.elf')
>>> +        d.appendVar('EXTRA_OEMAKE', ' CFG_CORE_HEAP_SIZE=131072')
>>> +}
>>
>> Both patches look good to me, but I currently have no nothing in place 
>> to test.
> 
> Thanks. I have tested locally that the resulting op-tee works as
> expected with this refactoring, and inspected the run.do_compile scripts
> to see that they are sensible.
> 
> Anything more I need to do on my end to get these merged? And when that
> is done, are they eligible for backporting to wrynose if I then resend
> with [wrynose] in $subject?
> 

I'm not the maintainer here :)

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center


      reply	other threads:[~2026-09-04  9:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 13:37 [PATCH 1/2] optee-os: make early TAs more convenient to add for .bbappends Rasmus Villemoes
2026-08-27 13:37 ` [PATCH 2/2] optee-ftpm: rewrite its optee-os bbappend to use EARLY_TA_PATHS bitbake variable Rasmus Villemoes
2026-08-27 17:00   ` Jan Kiszka
2026-09-04  9:36     ` Rasmus Villemoes
2026-09-04  9:47       ` Jan Kiszka [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=52828337-83b7-41f9-86f6-4fa72e00f877@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=jlu@pengutronix.de \
    --cc=jon.mason@arm.com \
    --cc=meta-arm@lists.yoctoproject.org \
    --cc=ravi@prevas.dk \
    /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.