From: "Yan, Haixiao (CN)" <haixiao.yan.cn@windriver.com>
To: reatmon@ti.com, meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti] [scarthgap][PATCH v2] trusted-firmware-a/optee-os: Add LPM support on few platforms
Date: Sun, 21 Dec 2025 08:09:57 +0800 [thread overview]
Message-ID: <c4181c69-e719-494f-9864-563a22cd7980@windriver.com> (raw)
In-Reply-To: <c0dadd48-6d6b-444f-8ff9-170919398571@ti.com>
On 12/21/2025 1:10 AM, Ryan Eatmon via lists.yoctoproject.org wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender
> and know the content is safe.
>
> On 12/20/2025 9:08 AM, Yan, Haixiao (CN) via lists.yoctoproject.org
> wrote:
>> This patch failed to apply on scarthgap.
>> the version of trusted-firmware-a is 2.10.4, the patch is not
>> suitable for this version.
>
> The recipe in meta-ti-bsp that applies this patch, also moves the
> version to 2.13+. So I'm not sure how you are trying to apply this
> patch to meta-ti scarthgap against a 2.10 trusted-firmware-a version.
>
> Clearly you are trying to do something more than taking meta-ti-bsp
> scarthgap at face value. Do you have your own layer in your build that
> is also changing the SRCREV of trusted-firmware-a to a version that
> might not accept these patches?
>
>
There is no 2.13+ version trusted-firmware-a on scarthgap.
https://git.yoctoproject.org/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.10.4.bb?h=scarthgap
$ bitbake-layers show-recipes trusted-firmware-a
NOTE: Starting bitbake server...
Loading cache: 100%
|#####################################################################|
Time: 0:00:02
Loaded 15169 entries from dependency cache.
=== Matching recipes: ===
trusted-firmware-a:
meta-arm 2.10+git
$ bitbake-layers show-appends | grep trusted-firmware-a
trusted-firmware-a_2.10.4.bb:
layers/meta-arm/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
layers/meta-ti/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
layers/ti-j7xxx/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
trusted-firmware-a_2.10.4.bb (skipped):
layers/meta-arm/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
layers/meta-ti/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
layers/ti-j7xxx/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
Thanks,
Haixiao
>> NOTE: Applying patch
>> '0001-feat-k3-choose-cluster_start_id-depending-on-the-soc.patch'
>> (../layers/meta-ti/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a/0001-feat-k3-choose-cluster_start_id-depending-on-the-soc.patch)
>>
>> NOTE: Applying patch
>> '0002-feat-ti-add-message-to-encrypt-tfa-during-suspend.patch'
>> (../layers/meta-ti/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a/0002-feat-ti-add-message-to-encrypt-tfa-during-suspend.patch)
>> ERROR: Applying patch
>> '0002-feat-ti-add-message-to-encrypt-tfa-during-suspend.patch' on
>> target directory
>> '/build-ti/tmp-glibc/work/ti_j78xx-wrs-linux/trusted-firmware-a/2.10+git/git'
>> CmdError('quilt --quiltrc
>> /build-ti/tmp-glibc/work/ti_j78xx-wrs-linux/trusted-firmware-a/2.10+git/recipe-sysroot-native/etc/quiltrc
>> push', 0, "stdout: Applying patch
>> 0002-feat-ti-add-message-to-encrypt-tfa-during-suspend.patch
>> can't find file to patch at input line 39
>> Perhaps you used the wrong -p or --strip option?
>> The text leading up to this was:
>> --------------------------
>> |From c79ff3679a4360bb848b01d4036c365533fcf791 Mon Sep 17 00:00:00 2001
>> |From: Richard Genoud <richard.genoud@bootlin.com>
>> |Date: Tue, 11 Feb 2025 18:20:17 +0100
>> |Subject: [PATCH 2/3] feat(ti): add message to encrypt tfa during
>> suspend
>> |
>> |At suspend, BL31 with its context will be encrypted by TIFS in DDR.
>> |Encryption is needed for security matters, so that the BL31 is not
>> |modified before entering suspend or early at resume.
>> |
>> |We only need the encryption function here because the decryption
>> message
>> |will be send by the R5 SPL at resume.
>> |
>> |Also introduce the LPM_ENCRYPT_IMAGE cap signals that FW has the
>> support
>> |to encrypt the image using the TISCI_MSG_LPM_ENCRYPT tisci message.
>> |
>> |This is useful in suspend to ram cases where we would like to
>> |store the encrypted image of a secure fw instead of the original image
>> |itself in the DDR.
>> |
>> |Check for LPM_ENCRYPT_IMAGE flag in the FW capabilities, and only then
>> |call encrypt.
>> |
>> |Upstream-Status: Pending
>> |
>> |Change-Id: I266472da87dd0821493019b2d9853f8886f33811
>> |Signed-off-by: Richard Genoud <richard.genoud@bootlin.com>
>> |Signed-off-by: Abhash Kumar Jha <a-kumar2@ti.com>
>> |---
>> | drivers/ti/ti_sci/ti_sci.c | 36 +++++++++++++++++++++++++++++
>> | drivers/ti/ti_sci/ti_sci.h | 7 ++++++
>> | drivers/ti/ti_sci/ti_sci_protocol.h | 32 +++++++++++++++++++++++++
>> | plat/ti/k3/common/k3_psci.c | 10 ++++++++
>> | 4 files changed, 85 insertions(+)
>> |
>> |diff --git a/drivers/ti/ti_sci/ti_sci.c b/drivers/ti/ti_sci/ti_sci.c
>> |index f0813e5b0..ee5f7166f 100644
>> |--- a/drivers/ti/ti_sci/ti_sci.c
>> |+++ b/drivers/ti/ti_sci/ti_sci.c
>> --------------------------
>> No file to patch. Skipping patch.
>> 1 out of 1 hunk ignored
>> can't find file to patch at input line 83
>> Perhaps you used the wrong -p or --strip option?
>> The text leading up to this was:
>> --------------------------
>> |diff --git a/drivers/ti/ti_sci/ti_sci.h b/drivers/ti/ti_sci/ti_sci.h
>> |index 1f1963274..2afa11317 100644
>> |--- a/drivers/ti/ti_sci/ti_sci.h
>> |+++ b/drivers/ti/ti_sci/ti_sci.h
>> --------------------------
>> No file to patch. Skipping patch.
>> 2 out of 2 hunks ignored
>> can't find file to patch at input line 107
>> Perhaps you used the wrong -p or --strip option?
>> The text leading up to this was:
>> --------------------------
>> |diff --git a/drivers/ti/ti_sci/ti_sci_protocol.h
>> b/drivers/ti/ti_sci/ti_sci_protocol.h
>> |index bdd24622a..a165cda99 100644
>> |--- a/drivers/ti/ti_sci/ti_sci_protocol.h
>> |+++ b/drivers/ti/ti_sci/ti_sci_protocol.h
>> --------------------------
>> No file to patch. Skipping patch.
>> 3 out of 3 hunks ignored
>> patching file plat/ti/k3/common/k3_psci.c
>> Hunk #2 succeeded at 269 with fuzz 1 (offset -14 lines).
>> Hunk #3 succeeded at 321 (offset -32 lines).
>> Patch 0002-feat-ti-add-message-to-encrypt-tfa-during-suspend.patch
>> does not apply (enforce with -f)
>
> --
> Ryan Eatmon reatmon@ti.com
> -----------------------------------------
> Texas Instruments, Inc. - LCPD - MGTS
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#19385): https://lists.yoctoproject.org/g/meta-ti/message/19385
> Mute This Topic: https://lists.yoctoproject.org/mt/116517214/8599992
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [Haixiao.Yan.CN@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2025-12-21 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 18:41 [meta-ti][scarthgap][PATCH v2] trusted-firmware-a/optee-os: Add LPM support on few platforms Manorit Chawdhry
2025-11-28 18:50 ` PRC Automation
2025-12-20 15:08 ` [scarthgap][PATCH " Yan, Haixiao (CN)
2025-12-20 17:10 ` [meta-ti] " Ryan Eatmon
2025-12-21 0:09 ` Yan, Haixiao (CN) [this message]
2025-12-21 18:47 ` Denys Dmytriyenko
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=c4181c69-e719-494f-9864-563a22cd7980@windriver.com \
--to=haixiao.yan.cn@windriver.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.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 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.