author | Arnie Reynoso <arnier@ti.com> | |
Tue, 21 Jan 2014 22:17:44 +0000 (14:17 -0800) | ||
committer | Chris Ring <cring@ti.com> | |
Wed, 22 Jan 2014 16:34:58 +0000 (08:34 -0800) | ||
commit | cb004c5225dbe46f5b36b0ed3e7b0705a57f70fb | |
tree | 4d5241b480726da62e8e33dc127e591fb636ec86 | tree | snapshot (tar.xz tar.gz zip) |
parent | 1987f0a84d5b7a271ed572faf6c5d113f8846ed8 | commit | diff |
Linux: Added GateMP support for DRA7XX devices
GateMP support has been added using the device's spinlocks.
To enable GateMP on the host, throw -g option when launching the
LAD daemon as follows:
./lad_dra7xx log.txt -g
To enable GateMP on the slave core, the core must be configured as
the owner of SR0 and GateMP.hostSupport config param must be set
to 'true' as follows:
var GateMP = xdc.useModule('ti.sdo.ipc.GateMP');
GateMP.hostSupport = true;
The slave core with GateMP enabled must the loaded (remoteproc)
prior to the execution of LAD on the host. This adds a restriction
on LAD that wasn't previously there.
Note: Initial validation has only been performed on DRA7XX DSP1.
GateMP support has been added using the device's spinlocks.
To enable GateMP on the host, throw -g option when launching the
LAD daemon as follows:
./lad_dra7xx log.txt -g
To enable GateMP on the slave core, the core must be configured as
the owner of SR0 and GateMP.hostSupport config param must be set
to 'true' as follows:
var GateMP = xdc.useModule('ti.sdo.ipc.GateMP');
GateMP.hostSupport = true;
The slave core with GateMP enabled must the loaded (remoteproc)
prior to the execution of LAD on the host. This adds a restriction
on LAD that wasn't previously there.
Note: Initial validation has only been performed on DRA7XX DSP1.
28 files changed: