From: harsimransingh.tungal@arm.com
To: meta-arm@lists.yoctoproject.org, Ross.Burton@arm.com
Cc: nd@arm.com, Harsimran Singh Tungal <harsimransingh.tungal@arm.com>
Subject: [PATCH 0/1] n1sdp:arm arm-bsp: fix tftf tests for n1sdp
Date: Fri, 26 Jan 2024 09:59:21 +0000 [thread overview]
Message-ID: <20240126095922.2836205-1-harsimransingh.tungal@arm.com> (raw)
From: Harsimran Singh Tungal <harsimransingh.tungal@arm.com>
This changeset fix the tftf tests issue on n1sdp. Before this change,
the tftf tests were getting stuck on n1sdp. The following changes have been done:
1. There were some tftf tests based on multicore which involve powering up the other cores.
These tests were creating issues and the same thing has already been mentioned in the
tests-to-skip.txt file for n1sdp platform in tftf source. Those tests are skipped while
executing tftf and patch has been created.
2. The TFTF_MODE variable added for tftf v2.10 recipe file, as did earlier for tftf v2.9.
With the help of this, we can enable debug or relase mode. The configuration based on this has
been added for n1sdp in the corresponding bbappend file.
3. Add PREFERRED_VERSION_tf-a-tests for v2.10.
Harsimran Singh Tungal (1):
n1sdp:arm arm-bsp: fix tftf tests for n1sdp
meta-arm-bsp/conf/machine/n1sdp.conf | 1 +
.../files/0001-n1sdp-tftf-tests-to-skip.patch | 46 +++++++++++++++++++
.../trusted-firmware-a/tf-a-tests_%.bbappend | 8 ++++
.../trusted-firmware-a/tf-a-tests_2.10.0.bb | 5 +-
4 files changed, 59 insertions(+), 1 deletion(-)
create mode 100644 meta-arm-bsp/recipes-bsp/trusted-firmware-a/files/0001-n1sdp-tftf-tests-to-skip.patch
--
2.25.1
next reply other threads:[~2024-01-26 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 9:59 harsimransingh.tungal [this message]
2024-01-26 9:59 ` [PATCH 1/1] n1sdp:arm arm-bsp: fix tftf tests for n1sdp harsimransingh.tungal
2024-01-27 15:34 ` [PATCH 0/1] " Jon Mason
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=20240126095922.2836205-1-harsimransingh.tungal@arm.com \
--to=harsimransingh.tungal@arm.com \
--cc=Ross.Burton@arm.com \
--cc=meta-arm@lists.yoctoproject.org \
--cc=nd@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).