TCF: disable running single core testcases on Quark SE's x86+arc

By default TCF was running test single core test cases in both Quark
SE cores at the same time.

This worked because the ARC output came through the IPM console to
x86, which enabled them to coexist.

However, after default configuration changes, this is no longer
possible without adding extra hardware to the current test setup,
which is cost prohibitive, and thus we are driving ARC output to the
same port as the x86 output.

This would make the output single-core test cases that are ran at the
same time in the x86 and ARC cores mix their outputs.

So we have that scenario disabled (and makes us run less test
cases). However, multicore test cases still can be run by selecting:

@targets bsp_model:x86+arc

Change-Id: I5f6b43246a24d0b263fd4a47866c7f0f99d20505
Signed-off-by: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>

1 files changed, 12 insertions, 1 deletions

diff --git a/defaults.tc b/defaults.tc
index 26dfde9dc..6a79c16c6 100644
--- a/defaults.tc
+++ b/defaults.tc
@@ -128,7 +128,18 @@
 # ^build [ quark_se_stub == 'yes'  and bsp == 'arc' ] \
 #   echo "# Generated by Zephyr's TCF defaults.tc"   > %(srcdir)s/outdir-%(tchash)s-%(board)s/tcf_2.3.4.conf; \
 #   echo 'CONFIG_UART_CONSOLE_ON_DEV_NAME="UART_1"' >> %(srcdir)s/outdir-%(tchash)s-%(board)s/tcf_2.3.4.conf
-
+#
+# (2.3.5) Quark SE: run test cases on x86 or ARC modes by default
+#
+#         This applies to test cases that are designed to run only in
+#         one core, as Quark SE will share one serial port in our test
+#         setup and the outputs will conflict and be a mess.
+#
+#         Test cases that need to run in both cores (BSP MODEl
+#         x86+arc) can still request it by tagging '@targets
+#         bsp_model:x86\+arc'
+#
+# @targets [ quark_se_stub == 'yes' ] bsp_model:^(x86|arc)$
 
 # (3) Generate the initial configuration
 #