QNX: Fix multi_process.sh for < 10 processes
The slave side executables can only handle a maximum of 10 threads,
so the script did not work corrently when it inadvertently tried to
look for an 11th thread.
This addresses SDOCM00102067.
Signed-off-by: VW <vwan@ti.com>
The slave side executables can only handle a maximum of 10 threads,
so the script did not work corrently when it inadvertently tried to
look for an 11th thread.
This addresses SDOCM00102067.
Signed-off-by: VW <vwan@ti.com>
Fix coding conventions in a few headers
Correct some IPC header issues recently identified by static
analysis.
Correct some IPC header issues recently identified by static
analysis.
Vayu: Remove ti.platform.vayu.* pkgs
In the IPC 3.00 stream the tests/examples switched to
ti.platforms.evmDRA7XX platform instances, but we left
these ti.platform.vayu.* platform packages in the IPC product
to not disrupt existing users of them.
Users have had adequate time to move to the XDC-provided
platform instances, so we are removing them in the IPC 3.10
stream.
In the IPC 3.00 stream the tests/examples switched to
ti.platforms.evmDRA7XX platform instances, but we left
these ti.platform.vayu.* platform packages in the IPC product
to not disrupt existing users of them.
Users have had adequate time to move to the XDC-provided
platform instances, so we are removing them in the IPC 3.10
stream.
QNX: Fix default build to not 'install'
The default build goal shouldn't run the 'install' goal.
This addresses SDOCM00102137.
The default build goal shouldn't run the 'install' goal.
This addresses SDOCM00102137.
QNX IPC: MmRpc - Generate .so Libs also
Generate .so libraries in addition to .a so that the
MmRpc can be dynamically linked.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Generate .so libraries in addition to .a so that the
MmRpc can be dynamically linked.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
QNX IPC: Export MmRpc Libs and Headers
Export the MmRpc generated libraries to usr/lib and
export the header file to user/include/ti/ipc/mm.
This is so that apps can easily include the header and
link with the library.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Export the MmRpc generated libraries to usr/lib and
export the header file to user/include/ti/ipc/mm.
This is so that apps can easily include the header and
link with the library.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Replaced usage of pathconf() with PATH_MAX
pathconf() returns error when file is located in /tmp. We switch to using PATH_MAX to avoid this problem.
Signed-off-by: VW <vwan@ti.com>
pathconf() returns error when file is located in /tmp. We switch to using PATH_MAX to avoid this problem.
Signed-off-by: VW <vwan@ti.com>
Vayu: Increased processor table size in NotifySetup module
When building for all cores on Vayu device, with non-SMP mode
on IPU1, the processor table was too small.
Signed-off-by: Ramsey Harris <ramsey@ti.com>
When building for all cores on Vayu device, with non-SMP mode
on IPU1, the processor table was too small.
Signed-off-by: Ramsey Harris <ramsey@ti.com>
MmRpc: Remove 'base' field from MmRpc_Xlt struct
This field was confusing and redundant. Given that the address
and offset to the embedded pointer are already available, the
base value can be derived in the MmRpc API layer.
Signed-off-by: Ramsey Harris <ramsey@ti.com>
This field was confusing and redundant. Given that the address
and offset to the embedded pointer are already available, the
base value can be derived in the MmRpc API layer.
Signed-off-by: Ramsey Harris <ramsey@ti.com>
QNX: Remove tiler and update makefiles
Tiler is now [correctly] managed independent from IPC. This
commit removes tiler support from IPC.
Tiler is now [correctly] managed independent from IPC. This
commit removes tiler support from IPC.
Tests: Update tests to support concurrently loaded slaves
Update the tests so that each core registers a different
endpoint name. In this way multiple images can be loaded
at the same time and these tests can be run for each core
without having to unload and reload another image.
Update the tests so that each core registers a different
endpoint name. In this way multiple images can be loaded
at the same time and these tests can be run for each core
without having to unload and reload another image.
Tests: Update RPC Stress test
Update the test so that each core registers a different
endpoint name. In this way multiple images can be loaded
at the same time and this test can be run for each core
without having to unload and reaload another image.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Update the test so that each core registers a different
endpoint name. In this way multiple images can be loaded
at the same time and this test can be run for each core
without having to unload and reaload another image.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
QNX: Don't Disable Host->rproc Interrupts During Register
The register/unregister functions are clearing mailbox
messages and disabling the host->rproc interrupts. When loading
multiple remote procs, this can cause an issue where the
remote proc's host->rproc interrupt remains disabled and the
remote proc is unable to receive interrupts.
This patch removes the code to avoid disabling the interrupt.
The register/unregister functions are clearing mailbox
messages and disabling the host->rproc interrupts. When loading
multiple remote procs, this can cause an issue where the
remote proc's host->rproc interrupt remains disabled and the
remote proc is unable to receive interrupts.
This patch removes the code to avoid disabling the interrupt.
BIOS: Remove M3 executable support for Vayu and OMAP5
No longer build the OMAP5 and Vayu tests when the M3 target
is set. We want to migrate users of these devices to the M4
target.
Also, an issue in BIOS 6.35.02 restricts Vayu to only M4
target support, so this ensures BIOS 6.35.02 users don't
hit this issue.
No longer build the OMAP5 and Vayu tests when the M3 target
is set. We want to migrate users of these devices to the M4
target.
Also, an issue in BIOS 6.35.02 restricts Vayu to only M4
target support, so this ensures BIOS 6.35.02 users don't
hit this issue.
Config and package updates for new XDCtools and SYS/BIOS builds
This fixes build and configuration issues for the following imports:
SYS/BIOS 6.35.02.44_eng
XDCtools 3.25.01.64_eng
Signed-off-by: Ramsey Harris <ramsey@ti.com>
This fixes build and configuration issues for the following imports:
SYS/BIOS 6.35.02.44_eng
XDCtools 3.25.01.64_eng
Signed-off-by: Ramsey Harris <ramsey@ti.com>
Tests: Update tests to use DRA7XX platform instance
Teach ti.ipc.tests to use instances of the
ti.platforms.evmDRA7XX platform rather than the IPC-specific
vayu platforms. These IPC-specific platforms can now be removed,
although we'll save that for the 3.10 stream so we don't break
existing users of them.
Note the two subtle changes in ipc-bios.bld. First, the
platform name should be 'ti.platforms.evmDRA7XX' (note the
plural 'platforms'). Second, the platform defined by XDC includes
an instance named "IPU2", so our locally defined instance name
cannot match that - so it's changed to lowercase 'ipu2'. Going
forward, we should standardize on platform instances with
all lower-case names.
Signed-off-by: Chris Ring <cring@ti.com>
Teach ti.ipc.tests to use instances of the
ti.platforms.evmDRA7XX platform rather than the IPC-specific
vayu platforms. These IPC-specific platforms can now be removed,
although we'll save that for the 3.10 stream so we don't break
existing users of them.
Note the two subtle changes in ipc-bios.bld. First, the
platform name should be 'ti.platforms.evmDRA7XX' (note the
plural 'platforms'). Second, the platform defined by XDC includes
an instance named "IPU2", so our locally defined instance name
cannot match that - so it's changed to lowercase 'ipu2'. Going
forward, we should standardize on platform instances with
all lower-case names.
Signed-off-by: Chris Ring <cring@ti.com>
Vayu: More support for the DRA7XX part number
'DRA7XX' and 'Vayu' are the same device. An earlier
commit added support for 'DRA7XX' but missed a few places,
which this commit addresses.
These missing changes were found when enabling platform instance
support to HLOS-based examples, so these changes are isolated to
packages used in HLOS environments.
Signed-off-by: Chris Ring <cring@ti.com>
'DRA7XX' and 'Vayu' are the same device. An earlier
commit added support for 'DRA7XX' but missed a few places,
which this commit addresses.
These missing changes were found when enabling platform instance
support to HLOS-based examples, so these changes are isolated to
packages used in HLOS environments.
Signed-off-by: Chris Ring <cring@ti.com>
Vayu: Remove unnecessary dependency in InterruptIpu
There was an unnecessary dependency from the IPU interrupt handler
(ti.sdo.ipc.family.vayu.InterruptIpu) onto the core of IPC
(ti.sdo.ipc.Ipc). For the MmServiceMgr use case, which needs the
interrupt handler but not the core of IPC, this dependency brought
in unnecessary code/data.
Signed-off-by: Chris Ring <cring@ti.com>
There was an unnecessary dependency from the IPU interrupt handler
(ti.sdo.ipc.family.vayu.InterruptIpu) onto the core of IPC
(ti.sdo.ipc.Ipc). For the MmServiceMgr use case, which needs the
interrupt handler but not the core of IPC, this dependency brought
in unnecessary code/data.
Signed-off-by: Chris Ring <cring@ti.com>
MmServiceMgr: Hide internal MmServiceMgr_start() fxn
Minor documentation change to hide the internal
MmServiceMgr_start() from doxygen-generated API reference guides.
Signed-off-by: Chris Ring <cring@ti.com>
Minor documentation change to hide the internal
MmServiceMgr_start() from doxygen-generated API reference guides.
Signed-off-by: Chris Ring <cring@ti.com>
Vayu: Enable configuration of IPU mailbox virt addrs
IPC must access the physical mailbox addresses (physically
at 0x4XXX_XXXX) via virtual addresses (typically set up
using the IPU's AMMU). System integrators need the
flexibility to place these mailboxes at different virtual
addresses.
System integrators can now use the InteruptIpu.mailboxBaseAddr[]
config params to place these mailboxes at virtual
addresses other than the default (which is 0x6XXX_XXXX).
Also clarified the cdoc documentation.
Signed-off-by: Chris Ring <cring@ti.com>
IPC must access the physical mailbox addresses (physically
at 0x4XXX_XXXX) via virtual addresses (typically set up
using the IPU's AMMU). System integrators need the
flexibility to place these mailboxes at different virtual
addresses.
System integrators can now use the InteruptIpu.mailboxBaseAddr[]
config params to place these mailboxes at virtual
addresses other than the default (which is 0x6XXX_XXXX).
Also clarified the cdoc documentation.
Signed-off-by: Chris Ring <cring@ti.com>
QNX IPC: Main - Use Absolute Path of Firmware
Save the absolute path of the firmware file to use
when loading the firmware.
This is useful for the recovery situation, where the
relative path will no longer work.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Save the absolute path of the firmware file to use
when loading the firmware.
This is useful for the recovery situation, where the
relative path will no longer work.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Added support for new platform: ti.platforms.evmDRA7XX
Added evmDRA7XX alias for Vayu in family Settings.xs. Removed
references to simVayu platform.
Signed-off-by: Ramsey Harris <ramsey@ti.com>
Added evmDRA7XX alias for Vayu in family Settings.xs. Removed
references to simVayu platform.
Signed-off-by: Ramsey Harris <ramsey@ti.com>
QNX IPC: RPMSG-RPC - Don't Wait for Response During Destroy
When calling rpmsg_rpc_destroy, all existing connections
are disconnected so that the remote core may be reloaded
and stale connections are not left open.
When rpmsg_rpc_destroy is called, it is assumed that
the remote processor has already been stopped. In this
case, there is no need to wait for a response from the
disconnect call. Instead, the connection can immediately
be marked as disconnected and destroy can continue.
This patch modifies each remote core connection to have
a parameter that tells whether or not the destroy function
is currently executing. Then, the disconnect call is
updated to check to see if destroy is being executed. If
destroy is being executed, then it does not send the
message to the remote core and wait for a response. Instead,
the connection is simply marked as disconnected.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
When calling rpmsg_rpc_destroy, all existing connections
are disconnected so that the remote core may be reloaded
and stale connections are not left open.
When rpmsg_rpc_destroy is called, it is assumed that
the remote processor has already been stopped. In this
case, there is no need to wait for a response from the
disconnect call. Instead, the connection can immediately
be marked as disconnected and destroy can continue.
This patch modifies each remote core connection to have
a parameter that tells whether or not the destroy function
is currently executing. Then, the disconnect call is
updated to check to see if destroy is being executed. If
destroy is being executed, then it does not send the
message to the remote core and wait for a response. Instead,
the connection is simply marked as disconnected.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
QNX IPC: Main - Fix Compile Warnings
This patch fixes the following compilation warnings:
qnx/src/ipc3x_dev/ti/syslink/build/Qnx/resmgr/syslink_main.c:
In function 'deinit_syslink_device':
qnx/src/ipc3x_dev/ti/syslink/build/Qnx/resmgr/syslink_main.c:450:
warning: unused variable 'i'
qnx/src/ipc3x_dev/ti/syslink/build/Qnx/resmgr/syslink_main.c:
In function 'deinit_syslink_trace_device':
qnx/src/ipc3x_dev/ti/syslink/build/Qnx/resmgr/syslink_main.c:392:
warning: control reaches end of non-void function
qnx/src/ipc3x_dev/ti/syslink/build/Qnx/resmgr/syslink_main.c:
In function 'init_syslink_trace_device':
qnx/src/ipc3x_dev/ti/syslink/build/Qnx/resmgr/syslink_main.c:374:
warning: control reaches end of non-void function
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
This patch fixes the following compilation warnings:
qnx/src/ipc3x_dev/ti/syslink/build/Qnx/resmgr/syslink_main.c:
In function 'deinit_syslink_device':
qnx/src/ipc3x_dev/ti/syslink/build/Qnx/resmgr/syslink_main.c:450:
warning: unused variable 'i'
qnx/src/ipc3x_dev/ti/syslink/build/Qnx/resmgr/syslink_main.c:
In function 'deinit_syslink_trace_device':
qnx/src/ipc3x_dev/ti/syslink/build/Qnx/resmgr/syslink_main.c:392:
warning: control reaches end of non-void function
qnx/src/ipc3x_dev/ti/syslink/build/Qnx/resmgr/syslink_main.c:
In function 'init_syslink_trace_device':
qnx/src/ipc3x_dev/ti/syslink/build/Qnx/resmgr/syslink_main.c:374:
warning: control reaches end of non-void function
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
QNX IPC: Vayu - Fix Compile Warnings
This patch fixes the following compilation warnings:
qnx/src/ipc3x_dev/ti/syslink/family/common/vayu/vayuipu/vayucore1/VAYUIpuCore1HalReset.c:
In function 'VAYUIPUCORE1_halResetCtrl':
qnx/src/ipc3x_dev/ti/syslink/family/common/vayu/vayuipu/vayucore1/VAYUIpuCore1HalReset.c:108:
warning: unused variable 'counter'
qnx/src/ipc3x_dev/ti/syslink/family/common/vayu/vayuipu/VAYUIpuPwr.c:
In function 'VAYUIPUPWR_on':
qnx/src/ipc3x_dev/ti/syslink/family/common/vayu/vayuipu/VAYUIpuPwr.c:1091:
warning: implicit declaration of function 'VAYUIPUMMU_enable'
qnx/src/ipc3x_dev/ti/syslink/family/common/vayu/vayuipu/VAYUIpuPwr.c:
In function 'VAYUIPUPWR_off':
qnx/src/ipc3x_dev/ti/syslink/family/common/vayu/vayuipu/VAYUIpuPwr.c:1156:
warning: implicit declaration of function 'VAYUIPUMMU_disable'
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
This patch fixes the following compilation warnings:
qnx/src/ipc3x_dev/ti/syslink/family/common/vayu/vayuipu/vayucore1/VAYUIpuCore1HalReset.c:
In function 'VAYUIPUCORE1_halResetCtrl':
qnx/src/ipc3x_dev/ti/syslink/family/common/vayu/vayuipu/vayucore1/VAYUIpuCore1HalReset.c:108:
warning: unused variable 'counter'
qnx/src/ipc3x_dev/ti/syslink/family/common/vayu/vayuipu/VAYUIpuPwr.c:
In function 'VAYUIPUPWR_on':
qnx/src/ipc3x_dev/ti/syslink/family/common/vayu/vayuipu/VAYUIpuPwr.c:1091:
warning: implicit declaration of function 'VAYUIPUMMU_enable'
qnx/src/ipc3x_dev/ti/syslink/family/common/vayu/vayuipu/VAYUIpuPwr.c:
In function 'VAYUIPUPWR_off':
qnx/src/ipc3x_dev/ti/syslink/family/common/vayu/vayuipu/VAYUIpuPwr.c:1156:
warning: implicit declaration of function 'VAYUIPUMMU_disable'
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
QNX IPC: Samples - Fix Compile Warnings
This patch fixes the following compilation warnings:
qnx/src/ipc3x_dev/ti/syslink/samples/hlos/rpmsg-rpc-stress/usr/tests_rpc_stress.c:
In function 'test_exec_call':
qnx/src/ipc3x_dev/ti/syslink/samples/hlos/rpmsg-rpc-stress/usr/tests_rpc_stress.c:280:
warning: assignment makes integer from pointer without a cast
qnx/src/ipc3x_dev/ti/syslink/samples/hlos/rpmsg-rpc-stress/usr/tests_rpc_stress.c:376:
warning: format '%x' expects type 'unsigned int', but argument 2 has type
'int *'
qnx/src/ipc3x_dev/ti/syslink/samples/hlos/rpmsg-rpc-stress/usr/tests_rpc_stress.c:376:
warning: format '%x' expects type 'unsigned int', but argument 3 has type
'void *'
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
This patch fixes the following compilation warnings:
qnx/src/ipc3x_dev/ti/syslink/samples/hlos/rpmsg-rpc-stress/usr/tests_rpc_stress.c:
In function 'test_exec_call':
qnx/src/ipc3x_dev/ti/syslink/samples/hlos/rpmsg-rpc-stress/usr/tests_rpc_stress.c:280:
warning: assignment makes integer from pointer without a cast
qnx/src/ipc3x_dev/ti/syslink/samples/hlos/rpmsg-rpc-stress/usr/tests_rpc_stress.c:376:
warning: format '%x' expects type 'unsigned int', but argument 2 has type
'int *'
qnx/src/ipc3x_dev/ti/syslink/samples/hlos/rpmsg-rpc-stress/usr/tests_rpc_stress.c:376:
warning: format '%x' expects type 'unsigned int', but argument 3 has type
'void *'
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Resource: Introduce customTable to override resource table
Users need to override the resource table. Introduce the
customTable boolean config param which uses set to true
to indicate they will provide their own table (and IPC shouldn't
generate a table for them).
They then have the responsibility to provide their own table
(with a symbol named ti_ipc_remoteproc_ResourceTable) at link
time.
Users need to override the resource table. Introduce the
customTable boolean config param which uses set to true
to indicate they will provide their own table (and IPC shouldn't
generate a table for them).
They then have the responsibility to provide their own table
(with a symbol named ti_ipc_remoteproc_ResourceTable) at link
time.
RemoteProc: rework resource_table definition/usage
Introduce the resource_table struct (defined in Linux) and
rework the device/core-specific resource tables to derive from
that struct (rather than redefine the struct themselves.
No functional difference, but this provides a better
framework and example for end users when they (soon!) are enabled
to define their own resource_table-based structs.
Introduce the resource_table struct (defined in Linux) and
rework the device/core-specific resource tables to derive from
that struct (rather than redefine the struct themselves.
No functional difference, but this provides a better
framework and example for end users when they (soon!) are enabled
to define their own resource_table-based structs.
Test: Remove unnecessary trace
Minor test cleanup, removing unnecessary trace statements.
Removed trivial copy-n-paste comment at the end of the file.
Minor test cleanup, removing unnecessary trace statements.
Removed trivial copy-n-paste comment at the end of the file.
Fix MessageQMulti's multi_process.sh script for QNX and install it
Fixed build warning in MessageQMulti test
Signed-off-by: Chris Ring <cring@ti.com>
Signed-off-by: Chris Ring <cring@ti.com>
Cleanup: remove directory qnx/src/ipc3x_dev/ti/syslink/rpmsg-resmgr
OMAP5 power management code in this directory is moved to qnx/src/ipc3x_dev/ti/syslink/family/omap5430, and the power management code itself was modified to remove checks with rpmsg-resmgr.
Signed-off-by: VW <vwan@ti.com>
OMAP5 power management code in this directory is moved to qnx/src/ipc3x_dev/ti/syslink/family/omap5430, and the power management code itself was modified to remove checks with rpmsg-resmgr.
Signed-off-by: VW <vwan@ti.com>
Cleanup: remove directory qnx/src/ipc3x_dev/ti/syslink/rpmsg-dce
Signed-off-by: VW <vwan@ti.com>
Signed-off-by: VW <vwan@ti.com>
Cleanup: remove directory qnx/src/ipc3x_dev/ti/syslink/rpmsg-omx
Signed-off-by: VW <vwan@ti.com>
Signed-off-by: VW <vwan@ti.com>
Cleanup: removed directory qnx/src/ipc3x_dev/perfutils
Signed-off-by: VW <vwan@ti.com>
Signed-off-by: VW <vwan@ti.com>
Changed Makefile.am to enable 'make dist' of files in hlos_common for Linux
Signed-off-by: VW <vwan@ti.com>
Signed-off-by: VW <vwan@ti.com>
Moved utils/MultiProc.c into hlos_common directory for both Linux and QNX.
Signed-off-by: VW <vwan@ti.com>
Signed-off-by: VW <vwan@ti.com>
Moved Std.h into ti/ipc namespace for QNX.
Signed-off-by: VW <vwan@ti.com>
Signed-off-by: VW <vwan@ti.com>
Moved headers common to both Linux and QNX into hlos_common directory.
This is done to avoid unnecessary duplication of code.
Signed-off-by: VW <vwan@ti.com>
This is done to avoid unnecessary duplication of code.
Signed-off-by: VW <vwan@ti.com>
Vayu: Fixed AMMU fault when running SYS/BIOS on IPU1
Prevent invalid mailbox accesses for interrupts between core0 and core1
because those interrupts do not use mailboxes.
Prevent invalid mailbox accesses for interrupts between core0 and core1
because those interrupts do not use mailboxes.
QNX IPC: Vayu - Add DSP1 MMU1 Programming
Currently, only MMU0 is being programmed for DSP1.
For EDMA traffic, there is a second MMU (MMU1), which
needs to be programmed. DSP1 applications which
use EDMA would want to also have the MMU1 programmed
so that the address space is the same.
This patch adds programming of the DSP MMU1
with the same entries to match the programming
of the DSP MMU0.
Additionally, this patch attaches an interrupt
to the DSP1 MMU1 for notification of MMU events.
No default interrupt is programmed for DSP1 MMU1,
so an unused MPU interrupt is selected for use and
the interrupt crossbar is programmed accordingly.
The interrupt selected is MPU interrupt 143.
Currently, only MMU0 is being programmed for DSP1.
For EDMA traffic, there is a second MMU (MMU1), which
needs to be programmed. DSP1 applications which
use EDMA would want to also have the MMU1 programmed
so that the address space is the same.
This patch adds programming of the DSP MMU1
with the same entries to match the programming
of the DSP MMU0.
Additionally, this patch attaches an interrupt
to the DSP1 MMU1 for notification of MMU events.
No default interrupt is programmed for DSP1 MMU1,
so an unused MPU interrupt is selected for use and
the interrupt crossbar is programmed accordingly.
The interrupt selected is MPU interrupt 143.
OMAP4: Removed files specific to OMAP4 in qnx directory
This commit removes all source files that are specific to OMAP4,
which the product does not support. Note that there are still file
names, variable names, macros, etc. related to OMAP4 that will need
subsequent clean up.
Files in tiler and rpmsg-resmgr directories have been left in place
as we are discussing their removal in an on-going thread.
A minor change was needed in syslink_main.c as well in order to
eliminate its use of type 'u32' defined in rprcfmt.h, so that we can
remove the latter file, which is specific to the OMAP4 loader.
Signed-off-by: VW <vwan@ti.com>
This commit removes all source files that are specific to OMAP4,
which the product does not support. Note that there are still file
names, variable names, macros, etc. related to OMAP4 that will need
subsequent clean up.
Files in tiler and rpmsg-resmgr directories have been left in place
as we are discussing their removal in an on-going thread.
A minor change was needed in syslink_main.c as well in order to
eliminate its use of type 'u32' defined in rprcfmt.h, so that we can
remove the latter file, which is specific to the OMAP4 loader.
Signed-off-by: VW <vwan@ti.com>
Style: Change //-style comments to /* */ style
Some users, especially those with MISRA-C requirements, don't
allow //-style comments.
Note that this addresses the files in packages/ti/ipc/*, there may
be more, but I didn't hunt further.
Some users, especially those with MISRA-C requirements, don't
allow //-style comments.
Note that this addresses the files in packages/ti/ipc/*, there may
be more, but I didn't hunt further.
BIOS: Fix minor typo in comment/docs
TCI6614: Improve error message during config
When this package is integrated into an unsupported environment,
it provides a better error message.
For example, before this change, when [errantly] integrating into
an OMAP5-based system, configuration would report:
TypeError: Cannot read property "IPCGR0" from undefined
Now it reports:
ti.ipc.family.tci6614.Interrupt : OMAP5430 unsupported
When this package is integrated into an unsupported environment,
it provides a better error message.
For example, before this change, when [errantly] integrating into
an OMAP5-based system, configuration would report:
TypeError: Cannot read property "IPCGR0" from undefined
Now it reports:
ti.ipc.family.tci6614.Interrupt : OMAP5430 unsupported
Removed duplicated MultiProc config info from Platform.c and simply use the info from _MultiProc_cfg.
Removed libcfg.a and moved _MultiProc_cfg into resource manager for QNX.
This is done to match a similar change in Linux that moved _MultiProc_cfg into the daemon process,
A side-effect is that Ipc_start must now be called prior to any MultiProc API.
This is done to match a similar change in Linux that moved _MultiProc_cfg into the daemon process,
A side-effect is that Ipc_start must now be called prior to any MultiProc API.
Remove BUILD_FOR_VIRTIO from products.mak and added support for DEVICE simvayu
DEVICE simvayu corresponds to a simulated vayu device
Signed-off-by: Chris Ring <cring@ti.com>
DEVICE simvayu corresponds to a simulated vayu device
Signed-off-by: Chris Ring <cring@ti.com>
IPC: Added conditional variable assignments to missing
Signed-off-by: Chris Ring <cring@ti.com>
Signed-off-by: Chris Ring <cring@ti.com>
NameServerRemoteRpmsg: Fixed strncpy operation to prevent overflow.
This is an improved solution to the patch:
195d2692fa95224d3c634daf8fe9bbd3860c7e16 BIOS: Fixed NameServerRemoteRpmsg MessageQ instanceName and name length
which now uses the actual destination length as the max characters for
strncpy() to copy, and ensures null termination of the copied string.
Improvement pointed out by Rob Tivy.
Signed-off-by: G Anthony <a0783926@ti.com>
This is an improved solution to the patch:
195d2692fa95224d3c634daf8fe9bbd3860c7e16 BIOS: Fixed NameServerRemoteRpmsg MessageQ instanceName and name length
which now uses the actual destination length as the max characters for
strncpy() to copy, and ensures null termination of the copied string.
Improvement pointed out by Rob Tivy.
Signed-off-by: G Anthony <a0783926@ti.com>
10 years agoVirtQueue: VirtQueue_init() reads vring addr from resource table, checks MAR. 3.00.00.19_eng
VirtQueue: VirtQueue_init() reads vring addr from resource table, checks MAR.
Previously, VirtQueue used hardcoded vring addresses in the code. Now, these
are read from the Resource Table, allowing the host to update them at load
time.
However, it is still expected that the vring memory is non-cached, and that
the system configuration has set this up in the CFG file.
VirtQueue_init() asserts if the vring addresses are not in the resource table,
or if the MAR bits for the vring memory show it as being caceable.
This is done only for OMAPL138 and TCI6638 VirtQueue in this patch.
Signed-off-by: G Anthony <a0783926@ti.com>
Previously, VirtQueue used hardcoded vring addresses in the code. Now, these
are read from the Resource Table, allowing the host to update them at load
time.
However, it is still expected that the vring memory is non-cached, and that
the system configuration has set this up in the CFG file.
VirtQueue_init() asserts if the vring addresses are not in the resource table,
or if the MAR bits for the vring memory show it as being caceable.
This is done only for OMAPL138 and TCI6638 VirtQueue in this patch.
Signed-off-by: G Anthony <a0783926@ti.com>
Resource: Added accessor to read vring addresses from resource table.
This will support the capability of allowing the host to allocate the vrings,
and specify the vring control structure address to the slave.
Also, renamed the existing getEntry() method to getMemEntry(), as it only
works for CARVEOUT and DEVMEM types.
Signed-off-by: G Anthony <a0783926@ti.com>
This will support the capability of allowing the host to allocate the vrings,
and specify the vring control structure address to the slave.
Also, renamed the existing getEntry() method to getMemEntry(), as it only
works for CARVEOUT and DEVMEM types.
Signed-off-by: G Anthony <a0783926@ti.com>
TCI6638: Switched to ROM model (-c) from RAM model (-cr) link option.
Kestone II DSP images were not able to be reloaded without rebooting the EVM.
This was due to the "-cr" linker options being thrown (RAM model), which
prevented processing of .cinit records at run time (done in ROM model).
So, "-cr" option was removed.
Keystone team mentioned that RLE compression was keeping the resource table
from being read properly without the "-cr" option, so added in the
"--cinit_compression=off" option just in case. This also has the benefit
of improving DSP boot times.
Reloading the DSPs via MPM server was validated on Keystone II EVM
(over remote connection).
Signed-off-by: G Anthony <a0783926@ti.com>
Kestone II DSP images were not able to be reloaded without rebooting the EVM.
This was due to the "-cr" linker options being thrown (RAM model), which
prevented processing of .cinit records at run time (done in ROM model).
So, "-cr" option was removed.
Keystone team mentioned that RLE compression was keeping the resource table
from being read properly without the "-cr" option, so added in the
"--cinit_compression=off" option just in case. This also has the benefit
of improving DSP boot times.
Reloading the DSPs via MPM server was validated on Keystone II EVM
(over remote connection).
Signed-off-by: G Anthony <a0783926@ti.com>
TCI6638: Linux target side scripts for loading, running lad, dumping trace.
Useful scripts to be used for the 8 core TCI6638 platformm.
Signed-off-by: G Anthony <a0783926@ti.com>
Useful scripts to be used for the 8 core TCI6638 platformm.
Signed-off-by: G Anthony <a0783926@ti.com>
Linux: Test - Cleanup to mmrpc build after sources moved to a common location
Signed-off-by: Chris Ring <cring@ti.com>
Signed-off-by: Chris Ring <cring@ti.com>
Linux: Building test applications as platform independent where appropriate
Platform dependent application's are no longer needed since a MultiProc
LAD daemon has been added.
Signed-off-by: Chris Ring <cring@ti.com>
Platform dependent application's are no longer needed since a MultiProc
LAD daemon has been added.
Signed-off-by: Chris Ring <cring@ti.com>
IPC: Tests - Add an Error Test Case
Add an error test case to test for MMU fault
detection.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Add an error test case to test for MMU fault
detection.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
QNX IPC: DSP Fault Recovery Fix
Fix an issue where the procId and procHandle are not
being properly set. If it is not properly set, then
error recovery doesn't happen properly.
This patch fixes that so that error recovery can happen
correctly.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Fix an issue where the procId and procHandle are not
being properly set. If it is not properly set, then
error recovery doesn't happen properly.
This patch fixes that so that error recovery can happen
correctly.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
QNX IPC: Add IPU2 MMU Fault Handling
There is no default interrupt mapped to the IPU2 MMU
for Vayu. This patch programs the interrupt crossbar
for the IPU2 MMU interrupt to MPU interrupt 142.
Also, this patch enables receiving the interrupt in the
case of an MMU fault event in order to print the required
information, as well as schedule recovery.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
There is no default interrupt mapped to the IPU2 MMU
for Vayu. This patch programs the interrupt crossbar
for the IPU2 MMU interrupt to MPU interrupt 142.
Also, this patch enables receiving the interrupt in the
case of an MMU fault event in order to print the required
information, as well as schedule recovery.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
QNX IPC: RpmsgRpc - Fix Tiler Address Translations
Tiler address translations should be done thorugh the
ProcMgr_translate function instead of just assuming
the remote core VA is the same as the PA.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Signed-off-by: Chris Ring <cring@ti.com>
Tiler address translations should be done thorugh the
ProcMgr_translate function instead of just assuming
the remote core VA is the same as the PA.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Signed-off-by: Chris Ring <cring@ti.com>
IPC - Match Resource Table for Vayu Based on Device
Match the resource table for Vayu based on the Device
name instead of the Platform name.
Currently, if the platform simVayu is used, it fails
to find the resource table. If the match is changed
to match the device name, then the simVayu platform,
which uses the Vayu device name, can compile.
Signed-off-by: Chris Ring <cring@ti.com>
Match the resource table for Vayu based on the Device
name instead of the Platform name.
Currently, if the platform simVayu is used, it fails
to find the resource table. If the match is changed
to match the device name, then the simVayu platform,
which uses the Vayu device name, can compile.
Signed-off-by: Chris Ring <cring@ti.com>
Changed all references to IPU's Core 0 to 'IPU' when in SMP mode for OMAP5.
BIOS: Minor log statement formatting
Remove some new lines and misc characters to better align with
other log statements throughout IPC.
Remove some new lines and misc characters to better align with
other log statements throughout IPC.
BIOS: Add missing dependency (rpmsg uses List)
Add the rpmsg dependency on List. This removes the need for
users to know this implementation detail of rpmsg and explicitly
bring in the List module themselves.
Add the rpmsg dependency on List. This removes the need for
users to know this implementation detail of rpmsg and explicitly
bring in the List module themselves.
BIOS: Remove unused include file
Test: Build script refactoring
Consolidate some of the test package.bld script. No functional
change.
Consolidate some of the test package.bld script. No functional
change.
OMAP5: Switch from custom DSP platforms to platform instances
Updated build scripts to use platform instances (currently of
ti.platforms.sdp5430) rather than the custom DSP platform
in ipcdev.
Remove ti.platform.omap54xx.dsp.
Updated build scripts to use platform instances (currently of
ti.platforms.sdp5430) rather than the custom DSP platform
in ipcdev.
Remove ti.platform.omap54xx.dsp.
Linux: Add MultiProc trace to log file
To improve visibility and debug, log the MultiProc configuration in the
LAD log file (when enabled) when a client asks for it.
To improve visibility and debug, log the MultiProc configuration in the
LAD log file (when enabled) when a client asks for it.
OMAP5: Rework package validation check for SMP-BIOS
OMAP5: Switch from custom IPU platforms to platform instances
Updated build scripts to use platform instances (currently of
ti.platforms.sdp5430) rather than the custom IPU platform
in ipcdev.
Remove ti.platform.omap54xx.ipu.
Also, since OMAP5 requires SMP-BIOS - remove the
ti.platform.omap54xx.core* platforms as well.
Updated build scripts to use platform instances (currently of
ti.platforms.sdp5430) rather than the custom IPU platform
in ipcdev.
Remove ti.platform.omap54xx.ipu.
Also, since OMAP5 requires SMP-BIOS - remove the
ti.platform.omap54xx.core* platforms as well.
Linux: Fix OMAP5 IPU MultiProc name
The Linux-side MultiProc names must be aligned with the BIOS-side
names.
The Linux-side MultiProc names must be aligned with the BIOS-side
names.
Vayu: New crossbar mapping for ipu2 and dsp2 to host interrupt
Original crossbar instance does not exist.
Original crossbar instance does not exist.
Revert "QNX IPC: WA For DSP Not Receiving Messages"
This reverts commit f83beccbebf69871fcd15d65525d0a8802850afa.
Conflicts:
qnx/src/ipc3x_dev/ti/syslink/ipc/hlos/knl/arch/vayu/VAYUIpcInt.c
This reverts commit f83beccbebf69871fcd15d65525d0a8802850afa.
Conflicts:
qnx/src/ipc3x_dev/ti/syslink/ipc/hlos/knl/arch/vayu/VAYUIpcInt.c
QNX IPC: DSP1 - Need to Enable DSP_SYSTEM Config for MMU0
If using DSP1 with the MMU enabled, need to also enable
the global config for MMU0 through the DSP_SYS_MMU_CONFIG
MMU0_EN bit.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
If using DSP1 with the MMU enabled, need to also enable
the global config for MMU0 through the DSP_SYS_MMU_CONFIG
MMU0_EN bit.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
IPC: DSP1 - Re-arrange Memory Map
Move the text section out of the 0x20000000 virtual address space
and group together the sections at 0x95000000 virtual address.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Move the text section out of the 0x20000000 virtual address space
and group together the sections at 0x95000000 virtual address.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
QNX IPC: Samples - Only Open SharedMemLib Once
A race condition in the rpmsg-rpc stress test could
result in one thread trying to access a NULL pointer
as there was no protection around the call to
initialize the sharedmemallocator library functions.
To avoid the race condition, move the initialization
of the sharedmemallocator functions to the main function,
to happen only once.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
A race condition in the rpmsg-rpc stress test could
result in one thread trying to access a NULL pointer
as there was no protection around the call to
initialize the sharedmemallocator library functions.
To avoid the race condition, move the initialization
of the sharedmemallocator functions to the main function,
to happen only once.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
QNX IPC: Update Int Xbar Programming to Match BIOS-side IPC
There was a conflict with the MPU Int being used by QNX IPC
for the DSP Mailbox.
The BIOS-side IPC is using MPU INT 141 for HOST receiving
interrupts from IPU2, and MPU INT 136 for HOST receiving
interrupts from DSP1.
QNX IPC is updated to use the same as we know these interrupts
are available.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
There was a conflict with the MPU Int being used by QNX IPC
for the DSP Mailbox.
The BIOS-side IPC is using MPU INT 141 for HOST receiving
interrupts from IPU2, and MPU INT 136 for HOST receiving
interrupts from DSP1.
QNX IPC is updated to use the same as we know these interrupts
are available.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
QNX IPC: Remove EVE from MultiProc as it is Not Used Currently
If EVE is defined in the MultiProc, then when the IPU is
starting up, the interrupt module will try to access the EVE
mailboxes, which leads to a crash as we are not mapping
the EVE mailboxes.
This patch updates the MultiProc config to remove the EVEs
so that the EVE mailboxes are not accessed.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
If EVE is defined in the MultiProc, then when the IPU is
starting up, the interrupt module will try to access the EVE
mailboxes, which leads to a crash as we are not mapping
the EVE mailboxes.
This patch updates the MultiProc config to remove the EVEs
so that the EVE mailboxes are not accessed.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
IPC: Vayu - Fix GPTimer Values and Control Module AMMU Config
The GPTimer values in IpcCommon.cfg.xs were using the
old virtual addresses that started with 0xA8. A
recent patch changed the virtual address mapping for
0x48000000 from 0xA8000000 to 0x68000000. The
GPTimer base addresses missed being updated.
This patch updates the GPTimer values to the correct
virtual addresses.
Also, the control module entry in IpuAmmu.cfg is
updated to do a translation from 0x4a000000 to
0x6a000000, to take advantage of the existing
mapping of the 0x6a000000 to the 0x4a000000 registers.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
The GPTimer values in IpcCommon.cfg.xs were using the
old virtual addresses that started with 0xA8. A
recent patch changed the virtual address mapping for
0x48000000 from 0xA8000000 to 0x68000000. The
GPTimer base addresses missed being updated.
This patch updates the GPTimer values to the correct
virtual addresses.
Also, the control module entry in IpuAmmu.cfg is
updated to do a translation from 0x4a000000 to
0x6a000000, to take advantage of the existing
mapping of the 0x6a000000 to the 0x4a000000 registers.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Build: Don't build big endian tests for Vayu or TCI6638
Limit the platform array for the C66 targets by only adding
TCI6638 and Vayu to the C66 little endian target, not the
big endian one.
Limit the platform array for the C66 targets by only adding
TCI6638 and Vayu to the C66 little endian target, not the
big endian one.
Build: Remove errant warning when building for Vayu
The resource table generation during configuration (by the
Resource.xdt template) errantly warns about not being able
to create the resource table.
Restructure the code to remove the warning for this successful
and valid use case.
The resource table generation during configuration (by the
Resource.xdt template) errantly warns about not being able
to create the resource table.
Restructure the code to remove the warning for this successful
and valid use case.
Docs: Minor doc typo fix
Linux: Moved IPC specific types file (Std.h) into the ti/ipc namespace
BIOS: Fix ti.ipc.transport build script for rpmsg2-based libs
Also rework ti.ipc.transport build scripts to remove unnecessary
platform-specific lib names.
Also update BIOS-side example to indicate the correct rpmsg version.
Also rework ti.ipc.transport build scripts to remove unnecessary
platform-specific lib names.
Also update BIOS-side example to indicate the correct rpmsg version.
QNX: Return E_NOTFOUND instead of E_FAIL if MQCopy_send fails
This allows MessageQ NameServer lookups to slaves that aren't
loaded to gracefully fail.
This allows MessageQ NameServer lookups to slaves that aren't
loaded to gracefully fail.
10 years agoIn VirtQueue_create, clear the VRING_USED_F_NO_NOTIFY flag to ensure all VirtQueue_ki...
In VirtQueue_create, clear the VRING_USED_F_NO_NOTIFY flag to ensure all VirtQueue_kick calls from the host results in an interrupt on slave.
10 years agoChanged GateAll to GateHwi since GateAll does not work in SMP BIOS according to SDOCM...
Changed GateAll to GateHwi since GateAll does not work in SMP BIOS according to SDOCM00100833
Fixed MultiProc config so that device names match the slave side on OMAP5
QNX IPC: Vayu - Update Xbar Config for 16_eng
In the 16_eng release of IPC 3x, the mailbox
usages is updated, so the interrupt crossbar
configuration must be updated. The new configuration
has the following mailbox usage:
Mailbox for DSP1->HOST is Mbox 5 User 2
Mailbox for IPU2->HOST is Mbox 6 User 2
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
In the 16_eng release of IPC 3x, the mailbox
usages is updated, so the interrupt crossbar
configuration must be updated. The new configuration
has the following mailbox usage:
Mailbox for DSP1->HOST is Mbox 5 User 2
Mailbox for IPU2->HOST is Mbox 6 User 2
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
BIOS IPC: Vayu - Update AMMU and MMU Configuration
In the 16_eng release, the mailbox virtual address
changed to 0x60000000 block. This was previously where
the TILER addresses were mapped. As a consequence, the
TILER mappings needed to be moved, and the AMMU config
as well as the resource table needed to be updated
to reflect the changes. Also, as a result of the move,
the VRING virtual addresses for the IPU have changed.
TILER VA: Moved from 0x60000000 to 0xA0000000
Peripherals and VRING: Moved from 0xA0000000 to 0x60000000
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
In the 16_eng release, the mailbox virtual address
changed to 0x60000000 block. This was previously where
the TILER addresses were mapped. As a consequence, the
TILER mappings needed to be moved, and the AMMU config
as well as the resource table needed to be updated
to reflect the changes. Also, as a result of the move,
the VRING virtual addresses for the IPU have changed.
TILER VA: Moved from 0x60000000 to 0xA0000000
Peripherals and VRING: Moved from 0xA0000000 to 0x60000000
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
QNX IPC - Update to New Mailbox Usage
With the latest 16_eng IPC 3.x release, the mailbox
usage has changed.
The QNX IPC is updated to be in sync with these
changes for communication with IPU2 and DSP1.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
With the latest 16_eng IPC 3.x release, the mailbox
usage has changed.
The QNX IPC is updated to be in sync with these
changes for communication with IPU2 and DSP1.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
QNX IPC: WA For DSP Not Receiving Messages
There is an issue observed when testing HOST->DSP1
communication using Vayu Virtio where if more than one
message is in the mailbox FIFO, then the DSP only
picks up one message, and the interrupt callback
stops running.
To avoid this issue, the workaround is to make sure
that we only send one message at a time from HOST->DSP1.
A side affect of this is that messages will be dropped,
but since (for the most part), the contents of the mailbox
message are the same, we can get away with this for now.
This may be just a Vayu Virtio issue, and we will
attempt to revert the WA in the future.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
There is an issue observed when testing HOST->DSP1
communication using Vayu Virtio where if more than one
message is in the mailbox FIFO, then the DSP only
picks up one message, and the interrupt callback
stops running.
To avoid this issue, the workaround is to make sure
that we only send one message at a time from HOST->DSP1.
A side affect of this is that messages will be dropped,
but since (for the most part), the contents of the mailbox
message are the same, we can get away with this for now.
This may be just a Vayu Virtio issue, and we will
attempt to revert the WA in the future.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
QNX IPC: Build - Add Vayu Build to the QNX IPC
Add the Vayu Build to the QNX IPC and update the build
files to allow specification of the device in the
products.mak file.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Add the Vayu Build to the QNX IPC and update the build
files to allow specification of the device in the
products.mak file.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Add Vayu Family Support for IPU2 (SMP) and DSP1
Add support for HOST->IPU2 and HOST->DSP1 support
for Vayu.
Add support for HOST->IPU2 and HOST->DSP1 support
for Vayu.
QNX IPC: Vayu - Add Vayu IPU2 and DSP1 Support
Add the Vayu family files to support IPC communication
between the HOST running QNX and the IPU2 and/or DSP1
running SYS/BIOS IPC3.x.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Add the Vayu family files to support IPC communication
between the HOST running QNX and the IPU2 and/or DSP1
running SYS/BIOS IPC3.x.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Add OMAP5 DSP Support for HLOS->SYSBIOS IPC
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
TCI6638: Linux target side scripts for loading, running lad, dumping trace.
Useful scripts to be used for the 8 core TCI6638 platformm.
Signed-off-by: G Anthony <a0783926@ti.com>
Signed-off-by: Chris Ring <cring@ti.com>
Useful scripts to be used for the 8 core TCI6638 platformm.
Signed-off-by: G Anthony <a0783926@ti.com>
Signed-off-by: Chris Ring <cring@ti.com>
Resource: Added config option to build images with SysMin trace resource only.
Set Resource.traceOnly to true in order to get an image with trace resources,
and without VDEV and VRING resources.
This feature was requested by the Keystone II (TCI6638) team for testing,
and so for now is only implemented for that platform's resource table.
Signed-off-by: Chris Ring <cring@ti.com>
Set Resource.traceOnly to true in order to get an image with trace resources,
and without VDEV and VRING resources.
This feature was requested by the Keystone II (TCI6638) team for testing,
and so for now is only implemented for that platform's resource table.
Signed-off-by: Chris Ring <cring@ti.com>
Build: Fix SMP support for platforms without 'ipu' in the name
A few SMP-aware packages only support platforms with the name
'ipu' in them. Remove this explicit platform name check and replace
it with a more correct check (e.g. by detecting BIOS.smpEnabled, or
using the platform's .deviceName field - which doesn't vary across
platform names).
A few SMP-aware packages only support platforms with the name
'ipu' in them. Remove this explicit platform name check and replace
it with a more correct check (e.g. by detecting BIOS.smpEnabled, or
using the platform's .deviceName field - which doesn't vary across
platform names).
Linux: Moved MultiProc config into the platform specific LAD daemon.
Also updated example apps to correctly call Ipc_start() before any
MultiProc functions.
Also updated example apps to correctly call Ipc_start() before any
MultiProc functions.