Table of Contents
Advertisement
Control/Configuration Driver
45.3 Control/Configuration Driver
The control and configuration driver is responsible for initializing and setting up the
master register page, initializing early-on feature initialization, providing limited debug
and monitoring capability, and generally ensuring that all other dependent driver
subsystems can connect to a correctly-configured device.
Step by step, it performs the following actions at startup:
• Allocates a private storage block for this level.
• Maps a virtual address to the full CAAM register page.
• Maps a virtual address for the SNVS register page.
• Maps a virtual (cache coherent) address for Secure Memory.
• Registers the security violation interrupt.
• Selects the correct DMA address size for the platform, and sets DMA address masks
to match.
• Identifies other pertinent interrupt connections
• Initializes all job ring instances
• If the system configuration includes a DPAA Queue Interface, that interface has
frame-pop enabled.
i.MX 6 configurations do not contain this logic.
• If the instance contains a TRNG, it's oscillator/entropy configuration is set and then
"kickstarted".
• Configuration information is sent to the system console to indicate that the driver is
alive, and what configuration it has assumed.
• If CONFIG_DEBUG_FS is selected in the kernel configuration, then entries are
added to enable debugfs views to useful registers in the performance monitor.
Register views are accessible under the caam/ctl directory at the debugfs root entry.
45.4 Job Ring Driver
The Job Ring driver is responsible for providing job execution service to higher-level
drivers. It takes care of overall management of both input and output rings and interrupt
service driving the output ring.
One driver call is available for higher layers to use for queueing jobs to a ring for
execution:
i.MX 6Solo/6DualLite Linux Reference Manual, Rev. L3.0.35_4.1.0, 09/2013
312
NOTE
Freescale Semiconductor, Inc.
Advertisement
Table of Contents
