From: "Denys Dmytriyenko" <denis@denix.org>
To: dmurphy@ti.com
Cc: meta-ti@lists.yoctoproject.org, nm@ti.com
Subject: Re: [meta-ti] [dunfell/master PATCH] trusted-firmware-a: Update to v2.4 merge
Date: Thu, 10 Dec 2020 16:45:25 -0500 [thread overview]
Message-ID: <20201210214525.GG19155@denix.org> (raw)
In-Reply-To: <75965ce5-23dc-19c3-4e88-993a13150cf1@ti.com>
On Thu, Dec 10, 2020 at 03:36:26PM -0600, Dan Murphy via lists.yoctoproject.org wrote:
> Forward
>
>
>
> -------- Forwarded Message --------
> Subject: [dunfell/master PATCH] trusted-firmware-a: Update to v2.4 merge
> Date: Thu, 10 Dec 2020 15:33:48 -0600
> From: Nishanth Menon <nm@ti.com>
> To: meta-ti@lists.yoctoproject.org
> CC: praneeth@ti.com, d-gerlach@ti.com, s-anna@ti.com,
> dmurphy@ti.com, Nishanth Menon <nm@ti.com>
>
>
>
> 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 as 2.4
>
> Suggested-by: Dan Murphy <dmurphy@ti.com>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> 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..08b2e04ff711 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 = "2.4"
^^^ This should be specific to a platform or SoC family.
See how all other variables below are specific to K3 with _k3 override.
Hence: PV_k3 = "2.4"
The reason is to not affect other platforms when using meta-ti in a multi-BSP
distros.
> 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
next prev parent reply other threads:[~2020-12-10 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201210213348.30149-1-nm@ti.com>
2020-12-10 21:36 ` [dunfell/master PATCH] trusted-firmware-a: Update to v2.4 merge Dan Murphy
2020-12-10 21:45 ` Denys Dmytriyenko [this message]
2020-12-10 21:58 ` [meta-ti] " Nishanth Menon
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=20201210214525.GG19155@denix.org \
--to=denis@denix.org \
--cc=dmurphy@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=nm@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.