xtensa-build-xephyr: fix xt-objcopy failure when default-params missing

Fixes recent commit 8aab183 ("xtensa-build-zephyr: fix
DEFAULT_TOOLCHAIN_VARIANT spill on next platf")

Some XtensaTools installation are missing this `default-params` symbolic
link:

```
XtensaTools/config/
|-- X4H3I16w2D48w3a_2017_8-params
|-- X6H3CNL_2017_8-params
|-- cavs2x_LX6HiFi3_2017_8-params
`-- default-params -> cavs2x_LX6HiFi3_2017_8-params
```

Maybe it's missing when installing with the graphical interface?

This symbolic link is surprisingly enough to make `xt-objcopy` work
_without_ the XTENSA_ variables. But when the variables _and_ the link
are both missing, then `xt-objcopy` fails with the usual error:

```
in current dir: work/current/sof; running command:
 XtDevTools/install/tools/RG-2017.8-linux/XtensaTools/bin/xt-objcopy
 --remove-section .comment sof/build-tgl/zephyr/zephyr.strip
       build-sof-staging/sof-info/tgl/stripped-zephyr.elf
Error: there is no Xtensa core registered as the default.

You need to either specify the name of a registered Xtensa core (with
the --xtensa-core option or the XTENSA_CORE environment variable) or
specify a different registry of Xtensa cores (with the --xtensa-system
option or the XTENSA_SYSTEM environment variable).

The following Xtensa cores are available:
	hifiep_bd5
	cavs2x_LX6HiFi3_2017_8
	sample_config
	sample_flix
	...
```

Fix this failure by simply passing the XTENSA_ variables to xt-objcopy.

Kudos to Seppo Ingalsuo for the interactive debugging session that
allowed root-causing this problem extremely quickly.

Signed-off-by: Marc Herbert <[email protected]>
(cherry picked from commit 3aeb2bf)

xtensa-build-xephyr: fix xt-objcopy failure when default-params missing

Fixes recent commit 8aab183 ("xtensa-build-zephyr: fix
DEFAULT_TOOLCHAIN_VARIANT spill on next platf")

Some XtensaTools installation are missing this `default-params` symbolic
link:

```
XtensaTools/config/
|-- X4H3I16w2D48w3a_2017_8-params
|-- X6H3CNL_2017_8-params
|-- cavs2x_LX6HiFi3_2017_8-params
`-- default-params -> cavs2x_LX6HiFi3_2017_8-params
```

Maybe it's missing when installing with the graphical interface?

This symbolic link is surprisingly enough to make `xt-objcopy` work
_without_ the XTENSA_ variables. But when the variables _and_ the link
are both missing, then `xt-objcopy` fails with the usual error:

```
in current dir: work/current/sof; running command:
 XtDevTools/install/tools/RG-2017.8-linux/XtensaTools/bin/xt-objcopy
 --remove-section .comment sof/build-tgl/zephyr/zephyr.strip
       build-sof-staging/sof-info/tgl/stripped-zephyr.elf
Error: there is no Xtensa core registered as the default.

You need to either specify the name of a registered Xtensa core (with
the --xtensa-core option or the XTENSA_CORE environment variable) or
specify a different registry of Xtensa cores (with the --xtensa-system
option or the XTENSA_SYSTEM environment variable).

The following Xtensa cores are available:
	hifiep_bd5
	cavs2x_LX6HiFi3_2017_8
	sample_config
	sample_flix
	...
```

Fix this failure by simply passing the XTENSA_ variables to xt-objcopy.

Kudos to Seppo Ingalsuo for the interactive debugging session that
allowed root-causing this problem extremely quickly.

Signed-off-by: Marc Herbert <[email protected]>
(cherry picked from commit 3aeb2bf)

platform: cannonlake: remove unused file idc.h

Remove one file that was missed in commit "platform: support for cAVS
1.8 platforms".

Signed-off-by: Kai Vehmanen <[email protected]>

ipc4: fix NULL dereference

This will fix NULL dereference in ipc4_process_chain_dma()

Signed-off-by: Adrian Bonislawski <[email protected]>

ace: pm_runtime: force L1 exit if requested

IMPORTANT: PM part should be moved to zephyr!

This will add possibility to force host L1 exit

Signed-off-by: Adrian Bonislawski <[email protected]>

cavs: memory bank powerup flow adjustment

Memory banks enablement flow is adjusted to recommended approach.
Power status should  be read twice to ensure ebb readiness

Signed-off-by: Michal Bukowski <[email protected]>
(cherry picked from commit aaac08a)

smart_amp_test: fix data size check

This will allow to return -EINVAL if wrong size provided.

Signed-off-by: Adrian Bonislawski <[email protected]>

Audio: SRC: Make stage buffer_start to be aligned at 8-byte boundary

sbuf length is empirically found and used to compute buffer_start.

buffer_start address is used by some instructions that require
8-byte aligned addresses:

See: src/audio/src/src_hifi4.c:
220	/* Load two data samples from two channels */
221	AE_L32X2F24_XC(d0, dp, inc); /* r0, l0 */

buffer_start = cd->delay_lines + cd->param.sbuf_length

Then we make sure cd->delay_lines is aligned to 8 and we only add
multiple by 8 lenghts.

Suggested-by: Seppo Ingalsuo <[email protected]>
Signed-off-by: Daniel Baluta <[email protected]>
(cherry picked from commit f4be6ec)

west: update zephyr to 3e9692d72d46

update zephyr to include  newest
commits from mtl-003-drop-stable branch

Signed-off-by: Adrian Bonislawski <[email protected]>

west: update zephyr to 3e9692d72d46

update zephyr to include  newest
commits from mtl-003-drop-stable branch

Signed-off-by: Adrian Bonislawski <[email protected]>