From: "Denys Dmytriyenko" <denis@denix.org>
To: nm@ti.com
Cc: meta-ti@lists.yoctoproject.org, praneeth@ti.com,
d-gerlach@ti.com, s-anna@ti.com, dmurphy@ti.com
Subject: Re: [meta-ti] [dunfell/master PATCH V2] trusted-firmware-a: Update to v2.4 merge
Date: Thu, 10 Dec 2020 17:06:54 -0500 [thread overview]
Message-ID: <20201210220654.GH19155@denix.org> (raw)
In-Reply-To: <20201210220137.2191-1-nm@ti.com>
On Thu, Dec 10, 2020 at 04:01:37PM -0600, Nishanth Menon via lists.yoctoproject.org wrote:
> Update to v2.4 tag merge from upstream to keep TF-A in sync.
>
> For major changes in trusted-firmware-a, See:
> https://trustedfirmware-a.readthedocs.io/en/latest/change-log.html#version-2-4
>
> TI specific fixups include:
> - stub for shutdown (CPUs enter wfi)
> - uart console is now configurable.
>
> While at it, update to include PV_k3 as 2.4
>
> NOTE: We use PV_k3 instead of PV since this allows meta-ti to not
> affect other platforms esp in a multi-BSP configuration.
>
> Suggested-by: Dan Murphy <dmurphy@ti.com>
> Signed-off-by: Nishanth Menon <nm@ti.com>
Looks good to me, thanks!
> ---
>
> Changes from V1:
> - Updated PV to PV_k3 to make sure we dont mess up multi-BSP configs
> (thanks Denys)
> recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
> index 3c1862643086..b1fb4e67ef9e 100644
> --- a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
> +++ b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
> @@ -1,6 +1,7 @@
> +PV_k3 = "2.4"
> BRANCH_k3 = "ti-atf"
> SRC_URI_k3 = "git://git.ti.com/atf/arm-trusted-firmware.git;branch=${BRANCH};name=tfa"
> -SRCREV_tfa_k3 = "52c334fc361194e3896ea3b2529c10a06e586a5f"
> +SRCREV_tfa_k3 = "f0a310d000fd6e8a1ed0ccc365b5931390393db1"
> COMPATIBLE_MACHINE_k3 = "k3"
> TFA_BUILD_TARGET_k3 = "all"
> TFA_INSTALL_TARGET_k3 = "bl31"
> --
> 2.25.1.377.g2d2118b814c1
--
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
prev parent reply other threads:[~2020-12-10 22:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 22:01 [dunfell/master PATCH V2] trusted-firmware-a: Update to v2.4 merge Nishanth Menon
2020-12-10 22:06 ` Denys Dmytriyenko [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=20201210220654.GH19155@denix.org \
--to=denis@denix.org \
--cc=d-gerlach@ti.com \
--cc=dmurphy@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=s-anna@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.