Freescale Semiconductor SEC2SWUG Bedienungsanleitung Seite 5
- Seite / 44
- Inhaltsverzeichnis
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
SEC 2.0 Reference Device Driver User’s Guide, Rev. 0
Freescale Semiconductor PRELIMINARY—SUBJECT TO CHANGE WITHOUT NOTICE 5
User Interface
2.1.5 Deferred Service Routine
The ProcessingComplete() routine completes the request outside of the interrupt service routine, and runs in a
non-ISR context. This routine depends on the IsrMsgQId queue and processes messages written to the queue by
the interrupt service routine. This function will determine which request is complete, and notify the calling task
using any handler specified by that calling task. It will then check the remaining content of the process request
queue, and schedule any queued requests.
3 User Interface
3.1 Application Interface
In order to make a request of the SEC2 device, the calling application populates a request structure with information
describing the request. These structures are described in Section 4, “Individual Request Type Descriptions,” and
include items such as operation ID, channel, callback routines (success and error), and data.
Once the request is prepared, the application calls
ioctl() with the prepared request. This function is a standard
system call used by operating system I/O subsystems to implement special-purpose functions. It typically follows
the format:
int ioctl(int fd, /* file descriptor */
int function, /* function code */
int arg /* arbitrary argument (driver dependent) */
The function code (second argument) is defined as the I/O control code. This code will specify the driver-specific
operation to be performed by the device in question. The third argument is the pointer to the SEC2 user request
structure which contains information needed by the driver to perform the function requested.
The following is a list of guidelines to be followed by the end-user application when preparing a request structure:
• The first member of every request structure is an operation ID (opID). The operation ID is used by the
device driver to determine the format of the request structure.
• While all requests have a “channel” member, it's presence is a holdover from earlier variations of the
security engine. For SEC2, it no longer has a valid use, and is retained solely to maintaining request
compatibility for applications written for older security engines.
• All process request structures have a status member. This value is filled in by the device driver when the
interrupt for the operation occurs and it reflects the status of the operation as indicated by the interrupt. The
valid values for this status member are DONE (normal status) or ERROR (error status).
• All process request structures have two notify members, notify and notify_on_error. These notify
members can be used by the device driver to notify the application when its request has been completed.
They may be the same function, or different, as required by the caller's operational requirements.
• All process request structures have a
next request member. This allows the application to chain multiple
process requests together.
• It is the application's choice to use a notifier function or to poll the status member.
- User’s Guide 1
- 2 Device Driver Components 3
- 2.1.3 Process Request Routine 4
- 3 User Interface 5
- 3.2 Error Handling 6
- 3.3 Global Definitions 7
- 3.3.4 Return Codes 8
- 3.3.5.1 STATUS_REQ Structure 10
- 4.1 Random Number Requests 14
- 4.2 DES Requests 14
- 4.3 ARC4 Requests 15
- 4.4 Hash Requests 17
- 4.5 HMAC Requests 18
- 4.6 AES Requests 19
- 4.7.1 MOD_EXP_REQ 20
- 4.7.2 MOD_SS_EXP_REQ 21
- 4.7.3 MOD_R2MODN_REQ 21
- 4.7.4 MOD_RRMODP_REQ 22
- 4.7.5 MOD_2OP_REQ 22
- 4.8 ECC Public Key Requests 24
- 4.8.2 ECC_2OP_REQ 25
- 4.8.3 ECC_SPKBUILD_REQ 26
- 4.9 IPSec Requests 27
- 4.9.2 IPSEC_ECB_REQ 29
- 4.9.3 IPSEC_AES_CBC_REQ 30
- 4.9.4 IPSEC_AES_ECB_REQ 31
- 4.9.5 IPSEC_ESP_REQ 32
- 4.10 802.11 Protocol Requests 35
- 4.11 SRTP Protocol Requests 35
- 5 Sample Code 36
- 5.2 IPSEC Sample 37
- 6Linux Environment 39
- 7 VxWorks Environment 40
- 8 Porting 41
- 8.1 Header Files 42
- 8.2 C Source Files 42
- 8.3 Interrupt Service Routine 42
- 8.4 Conditional Compilation 43
- 8.5 Debug Messaging 43
- 8.6 Distribution Archive 43
- How to Reach Us: 44
Verwandte Produkte und Handbücher für Nein Freescale Semiconductor SEC2SWUG
(66 Seiten)Tiffen Lowel Prime LED 200 manuály
Uživatelské manuály a uživatelské příručky pro Osvětlení Tiffen Lowel Prime LED 200.
Poskytujeme 1 manuály pdf Tiffen Lowel Prime LED 200 ke stažení zdarma podle typů dokumentů: Uživatelský manuál
Kommentare zu diesen Handbüchern