MSC8144E Reference Manual, Rev. 3
26-6
Freescale
Semiconductor
Security Engine (SEC)
26.1.3.2 Channel Completion
The channel indicates completion by sending a descriptor via an interrupt to the core processor or
by a writeback of the descriptor header into core processor memory. In the case of a writeback,
the value written back is identical to the header that was read, except for a DONE field, which is
set to all 1s. The user performs this notification signalling at the end of every descriptor or at the
end of selected descriptors.
26.1.3.3 Integrity Check Value (ICV) Generation and Checking
An EU operation can include generating an ICV and then comparing it against a received ICV.
The result of the ICV checking can be sent to the core processor via interrupt or by a writeback of
the descriptor header (but not by both methods). In the case of a writeback, the user can opt to do
it at the end of every descriptor or only at the end of descriptors that call for ICV comparison.
Note:
For details on configuring signaling, see Section 26.5.5.1, Channel Configuration
Registers for Channels 1–4 (CCR[1–4]), on page 26-89. For detail on the writeback
fields, see Section 26.2.1.1.2, Descriptor Header, on page 26-11.
26.1.3.4 Encryption and Hashing
Many security protocols involve both encryption and hashing of packet payloads. To accomplish
this without requiring two passes through the data, channels can configure data flows through
more than one EU. In such cases, one EU is designated as the primary EU, and the other as the
secondary EU. The primary EU receives its data from memory via the controller, and the
secondary EU receives its data by snooping the SEC buses.
26.1.3.5 Snooping
There are two types of snooping.
Input data can be fed to the primary EU and the same input data is snooped by the
secondary EU. This is called in-snooping.
Output data from the primary EU can be snooped by the secondary EU. This is called
out-snooping.
Note:
In the SEC, the secondary EU is always the MDEU. For details, see
Section 26.3, Channels, on page 26-20.
Note:
All SEC memory transactions are snooped by the device coherency module. This is
part of the SEC interface and requires no user intervention.
Summary of Contents for MSC8144E
Page 1: ...MSC8144E Reference Manual Quad Core Media Signal Processor MSC8144ERM Rev 3 July 2009 ...
Page 48: ...MSC8144E Reference Manual Rev 3 xlviii Freescale Semiconductor ...
Page 86: ...MSC8144E Reference Manual Rev 3 1 38 Freescale Semiconductor Overview ...
Page 168: ...MSC8144E Reference Manual Rev 3 3 60 Freescale Semiconductor External Signals ...
Page 242: ...MSC8144E Reference Manual Rev 3 5 26 Freescale Semiconductor Reset ...
Page 314: ...MSC8144E Reference Manual Rev 3 8 24 Freescale Semiconductor General Configuration Registers ...
Page 414: ...MSC8144E Reference Manual Rev 3 10 14 Freescale Semiconductor MSC8144E SC3400 DSP Subsystem ...
Page 452: ...MSC8144E Reference Manual Rev 3 11 38 Freescale Semiconductor Internal Memory Subsystem ...
Page 520: ...MSC8144E Reference Manual Rev 3 12 68 Freescale Semiconductor DDR SDRAM Memory Controller ...
Page 1070: ...MSC8144E Reference Manual Rev 3 21 28 Freescale Semiconductor Timers ...