Axis Kernel Driver Data Structures

Here are the data structures with brief descriptions:

_CRYPTO_OP	User applications submit DES operations using this structure and an IOCTL call
_KEY_OP	Contains a 3DES KEY passed by IOCTL call
access_control_entry	Associates a bitmask and an address
axis_component_instance	Associates a axis_pci_device_entry with a integer which can be used to identify individual components
axis_des_hardware_channel	Defines and controls one 3DES hardware channel
axis_des_hardware_key	Defines and controls the use of a key slot in the axis 3DES hardware
axis_des_key	Struct tracks a key and its properties
axis_des_op	Structure to contain a DES operation
axis_io_bitmap	Mirrors for Axis Parallel IO
axis_pci_device_entry	Hardware master control structure
axis_region	Stash information about the PCI IO/Mem region we intend to use
axis_w1
crypto_state	Associates a key (crypto session) and a hardware device
input_def	Properties on individual input
output_def	Properties on individual output
spi_channel	Controls an individual spi channel
spi_op	Structure submitted by SPI userland interface to SPI core code
sram_access_control	Wraps up the data needed to control the Axis read/write enables
sram_block	Sram memory control block
sram_config_entry	Defines a SRAM partition
text_to_int	Element in array that supports integer to string and string to integer lookup

---