![]() |
Include dependency graph for SDIO.h:
|
valueP is a SDIOAccessDelayType |
|
valueP is a SDIOAPIVersionType |
|
This card has a standard SDIO file system in function 1 |
|
This card has a standard SDIO file system in function 2 |
|
This card has a standard SDIO file system in function 3 |
|
This card has a standard SDIO file system in function 4 |
|
This card has a standard SDIO file system in function 5 |
|
This card has a standard SDIO file system in function 6 |
|
This card has a standard SDIO file system in function 7 |
|
This card has a standard SDIO file system in the SD Memory section. |
|
This card has an Auto Run function driver in function 1 |
|
This card has an Auto Run function driver in function 2 |
|
This card has an Auto Run function driver in function 3 |
|
This card has an Auto Run function driver in function 4 |
|
This card has an Auto Run function driver in function 5 |
|
This card has an Auto Run function driver in function 6 |
|
This card has an Auto Run function driver in function 7 |
|
This card has an Auto Run function driver in the SD Memory section |
|
The write protect tab on the card indicates that this card is write protected |
|
Callback that occurs when the handheld wants to wake up. |
|
Callback that occurs when the bus width of the card is changed. |
|
The number of possible callbacks for a given SDIO card function. |
|
Callback that occurs when an SDIO card interrupts the handheld (Note: This callback is made during the processing of an interrupt.) |
|
Callback that occurs when the SDIO card power is turned off. |
|
Callback that occurs when the SDIO card power is turned on. |
|
Callback that occurs when the SDIO section of the card is reset. |
|
Callback that occurs when the handheld wants to go to sleep. |
|
Turn off the card, put the data signals in a low power state |
|
Power on and initialize the card |
|
This will force the SDMem portion of a SD combo card to be software reset by a CMD0, the function will return after the card is initialized. This value cannot be used with SDIOSetAutoPowerOff. |
|
Wait for the I/O portion of an SDIO card to be ready (after IO_SEND_OP_COND CMD5). Use this after resetting 1 or more function(s). This value cannot be used with SDIOSetAutoPowerOff. |
|
valueP is a SDIODebugOptionType |
|
Enable all options. |
|
Sends the data from commands that have command/response/data, warning, This is alot of data! |
|
Sends all commands that are issued to the card |
|
Sends the contents of Tuples and/or parts of the CSD (Card Specific Data register) when they are accessed just after card insertion |
|
Allows debug messages to be sent from within interrupt routines, Warning: keep stack small to avoid overflows |
|
Sends all commands that are issued to the card |
|
Disable all options. |
|
Sends the progress of the tests that are performed upon card insertion |
|
Sends rejection reasons |
|
valueP is a NULL |
|
valueP is a NULL |
|
This is for the SDIO function 0 area (CIA Common I/O Area). |
|
This is for the SDIO function 1 area |
|
This is for the SDIO function 2 area |
|
This is for the SDIO function 3 area |
|
This is for the SDIO function 4 area |
|
This is for the SDIO function 5 area |
|
This is for the SDIO function 6 area |
|
This is for the SDIO function 7 area |
|
The total number of SDIO function areas |
|
valueP is a SDIOAutoPowerOffType |
|
valueP is a AutoRunInfoType |
|
valueP is a SDIOCallbackType |
|
valueP is a SDIOCurrentLimitType |
|
valueP is a SDIOCardInfoType |
|
valueP is a SDIOPowerType |
|
valueP is a SDIOSlotInfoType |
|
valueP is a SDIOCurrentLimitType |
|
valueP is a SDIORWDirectType |
|
valueP is a SDIORWExtendedBlockType |
|
valueP is a SDIORWExtendedByteType |
|
Used in combination with sdioRWModeWrite, sdioRWModeRead, or sdioRWModeWriteRead to perform a multi-byte read or write to a single register address. Useful when transferring data using a FIFO inside the I/O device. |
|
Used in combination with sdioRWModeWrite, sdioRWModeRead, or sdioRWModeWriteRead to cause SDIORWExtendedBlock to always set the block size. This is useful if the driver resets and I/O only card or the I/O portion of a combo card, or if it alters the I/O block length in the FBR (Function Basic Registers). |
|
Read data from the card and place it in the specified buffer. |
|
Write data from the specified buffer to the card. |
|
Write data from the specified buffer to the card, then read the data from the card and place it back into the buffer. |
|
SDIO bit mode 1 (SD or SPI mode) |
|
SDIO bit mode 4 (SD mode only) |
|
valueP is a SDIOAutoPowerOffType |
|
valueP is a SDIOSDBitModeType, Note: this can be refused by expErrUnsupportedOperation |
|
valueP is a SDIOCallbackType |
|
valueP is a SDIOCurrentLimitType |
|
valueP is a SDIOPowerType |
|
This is for the SDIO function 1 Slot for SDIO cards |
|
This is for the SDIO function 2 Slot for SDIO cards |
|
This is for the SDIO function 3 Slot for SDIO cards |
|
This is for the SDIO function 4 Slot for SDIO cards |
|
This is for the SDIO function 5 Slot for SDIO cards |
|
This is for the SDIO function 6 Slot for SDIO cards |
|
This is for the SDIO function 7 Slot for SDIO cards |
|
This is for the SD Memory card slot (for regular memory cards or SD combo cards) |
|
valueP is a SDIOTupleType |
|
Creator code for the SDIO slot driver. |
|
The maximum timeout, in milliseconds, for reads and writes using the IO_RW_DIRECT and IO_RW_EXTENDED commands. The maximum timeout, in milliseconds, for reads and writes using the IO_RW_DIRECT and IO_RW_EXTENDED commands. |
|
Used to hold the version number of the SDIO slot driver |
|
Returned as part of an SDIOCardInfoType structure, each of the bits that makes up SDIOBitsOfFileSystemType indicates whether the corresponding function has a standard SDIO file system. Note that this file system may or may not be mounted.
|
|
Returned as part of an SDIOCardInfoType structure, each of the bits that makes up SDIOBitsOfStatusType indicates various status information about the SDIO card.
|
|
SDIOCallbackPtr - Perform driver-specific processing when one of the following occurs: -the SDIO interrupt is received -the handheld is going to sleep or has just awakened -the SDIO card was just turned off or on -the SDIO card was just reset -the bus width changed. Which of the above events causes a given callback function to be called, if any, depends on what was passed to SDIOSetCallback..
Your callback functions can be called from within an interrupt service routine, and interrupts can occur at any time. The interrupt can even generate a wakeup event if the handheld is asleep and power to the card is still on. As with an interrupt service routine, your callback functions can only call a limited set of system functions (those that are interrupt-safe) and must execute quickly. Your callback functions do have access to any slot driver functions accessible through the SlotCustomControl function. |
|
Values of type SDIOCallbackSelectType are used in an SDIOCallbackType structure to identify which of an SDIO card function's callbacks is needed or is to be set.
|
|
Used with SDIOPowerType and SDIOAutoPowerOffType to specify whether the SDIO card's power and data signals should be turned on or off, whether the SD Memory section of a combo card should be reset, or whether to wait for the SDIO portion of an SD card to be ready.
|
|
The ID of the SDIO function passed to the Slot Driver.
|
|
This is used with SDIODebugOptions and identifies which debug messages, if any, are to be sent to the serial or USB port. These messages are sent on debug ROMs and debug RAM patches only.
|
|
Used with the SDIORWDirect, SDIORWExtendedByte, and SDIORWExtendedBlock functions to specify the number of the SDIO card function area to be read or written, or with the SDIOTupleWalk function to specify the number of the function to be searched.
|
|
Specifies the particular operation to be performed when using SDIORWDirect, SDIORWExtendedBlock , and SDIORWExtendedByte.
|
|
Used in the SDIOCardInfoType and SDIOSDBitModeRequestType structures to indicate which SDIO bit mode is to be used when interacting with a particular SDIO card function.
|
|
Used with a number of types and functions to identify a specific function slot driver within an SDIO card.
|
|
SDIOAccessDelay - Change the SDIO card access timeout for reads and writes using IO_RW_DIRECT and IO_RW_EXTENDED from the 1 second default. If a card needs a slower (worst case) delay use this. Note: basic commands like read CCRCR, FBR's, and tuples MUST be readable within 1 second! If a file system is available, it will be mounted (accesssed) with this 1 second limitation too! Drivers only have access to this after their driver is started!
This function requires that an SDIO card be present in the slot. This function can safely be called from within an interrupt service routine. |
|
SDIOAPIVersion - This call is used to detect if the Slot Driver is SDIO aware and returns the SDIO slot driver version number. If it returns "errNone" the Slot driver is SDIO aware and the version number of the SDIO part of the slot driver is in the SDIOAPIVersionType.
|
|
SDIODebugOptions - Enable or disable the sending of debug messages to the serial or USB port. FOR DEBUG ROMS and DEBUG RAM patches only!
To deactivate debugging, perform a soft reset on the handheld or call SDIODebugOptions and specify sdioDebugOptionTraceNone. This is not a real time trace: the serial port slows down the card's response. Use a logic analyzer for real time tracing. This function can safely be called from within an interrupt service routine. |
|
SDIODisableHandheldInterrupt - Disables the interrupt on the handheld. This function does not turn off interrupts on the card. This call disables the interrupt on the handheld side (This does not turn off any interrupt on the card). The disable interrupt is implemented as an incrementing counter (like locking memory), thus making it re-entrant. However, for every call of SDIODisableHandheldInterrupt() there must be an equal number (or more) of SDIOEnableHandheldInterrupt() to actually re-enable interrupts.
This function can safely be called from within an interrupt service routine. |
|
SDIOEnableHandheldInterrupt - Enables the interrupt on the handheld. This function does not affect interrupts on the card. This call enables the interrupt on the handheld side For every call of SDIODisableHandheldInterrupt() there must be an equal number (or more) of SDIOEnableHandheldInterrupt() to actually re-enable interrupts. By default, when the card is inserted, this interrupt is enabled by this routine, but disabled internally until an interrupt callback is set.
This function requires that an SDIO card be present in the slot. This function can safely be called from within an interrupt service routine. |
|
SDIOGetAutoPowerOff - Get the current auto-power-off settings for the SD slot. Every time a card is inserted the card will default to: "ticksTillOff" = about 15 seconds "sleepPower" = sdioCardPowerOff Another default behavior of the card is when the handheld wakes up, it does not turn on the card. Instead it waits until there is a request to use the card. Then the card is turned on.
|
|
SDIOGetAutoRun - Provide a description of the SD/MMC memory card or SDIO card that is currently inserted. This fills in information for a Auto Run of a RAM based Application. Generally this is not for the Function Driver (since it is already executing).
This function can safely be called from within an interrupt service routine. |
|
SDIOGetCallback - Obtain pointers to an SDIO card function's callback routine and associated data.
When a situation arises that causes one of the above callback functions to be called, the corresponding callback for the SD Memory card slot is generally the first one called, followed by the corresponding callback functions for SDIO functions 1 through 7. Because the SD Memory card slot and each SDIO card function slot can have a separate callback function for each callback selector, each callback function can limit itself to dealing with a single selector and a single SDIO card function. Callback function information is automatically erased after a card is inserted or removed (before the card removal event). Because of this, SDIOGetCallback can only be used when a card is in the SD slot. To detect card removal, use the notification manager and register for sysNotifyCardRemovedEvent. SDIOGetCallback can safely be called from within an interrupt service routine. Warning: If you use any of these callbacks, you may not have control of the user interface or access to your variables. Always Set/Use the userDataP to access your user variables! Also, remember to lock memory for your callback routines and variables. |
|
SDIOGetCardInfo - Return information about the SDIO card obtained with the SDIO IO_QUERY command (ACMD57). All other information on the card can be obtained by the normal SDIO read & write calls.
This function requires that an SDIO card be present in the slot. Note, however, that information is cached in RAM. |
|
SDIOGetCurrentLimit - Get the maximum peak current allotted to one of the SDIO card's functions.
This function can safely be called from within an interrupt service routine. |
|
SDIOGetPower - Determine whether an SD card function is currently powered on or off.
|
|
SDIOGetSlotInfo - Obtain the slot driver reference number, the slot driver library reference number, and the volume reference number for the associated file system, if any, for one of the SDIO functions or for the SD Memory card slot driver.
|
|
SDIORemainingCurrentLimit - Get the remaining current for the entire SDIO card.
This function can safely be called from within an interrupt service routine. |
|
SDIORWDirect - Read or write a single byte to any I/O function, including the common I/O area (CIA), at any address using CMD52 (IO_RW_DIRECT).
This function can safely be called from within an interrupt service routine. |
|
SDIORWExtendedBlock - Read or write multiple blocks of a specified size to any I/O function, including the common I/O area (CIA), at any address using the optional block mode of CMD53 (IO_RW_EXTENDED).
The write protect tab on the SD card is ignored by the SDIO slot driver. Issuing a write request with this function always causes the write command to be sent to the card. This function can safely be called from within an interrupt service routine. |
|
SDIORWExtendedByte - Read or write multiple bytes to any I/O function, including the common I/O area (CIA), at any address using the byte mode of CMD53 (IO_RW_EXTENDED).
This function can safely be called from within an interrupt service routine. |
|
SDIOSetAutoPowerOff - Alter the auto-power-off settings for the SD slot.
This function only works with SDIO cards; it cannot be used when a memory card is in the slot. This function can safely be called from within an interrupt service routine. |
|
SDIOSetBitMode - Change the bus width.
This function requires that an SDIO card be present in the slot, and it may turn on and access the card. This function can safely be called from within an interrupt service routine. |
|
SDIOSetCallback - Set pointers to an SDIO card function's callback routine and associated data.
When a situation arises that causes one of the above callback functions to be called, the corresponding callback for the SD Memory card slot is generally the first one called, followed by the corresponding callback functions for SDIO functions 1 through 7. Because the SD Memory card slot and each SDIO card function slot can have a separate callback function for each callback selector, each callback function can limit itself to dealing with a single selector and a single SDIO card function. If you use any of these callbacks, you may not have control of the user interface or access to your variables. Make any necessary data available to your callback function through the use of userDataP. Be sure to lock memory for your callback functions and variables. Callback functions must be interrupt-safe: they should only call interrupt-safe functions. Your callback functions can be called from within an interrupt service routine, and interrupts can occur at any time. The interrupt can even generate a wakeup event if the handheld is asleep and power to the card is still on. As with an interrupt service routine, your callback functions can only call a limited set of system functions and must execute quickly. Your callback functions do have access to any slot driver functions accessible through the slotCustomControl function. Callback function information is automatically erased after a card is inserted or removed (before the card removal event). Because of this, SDIOSetCallback can only be used when a card is in the SD slot. To detect card removal, use the notification manager and register for sysNotifyCardRemovedEvent. SDIOSetCallback can safely be called from within an interrupt service routine. Warning: If you use any of these callbacks, you may not have control of the user interface or access to your variables. Always Set/Use the userDataP to access your user variables! Also, remember to lock memory for your callback routines and variables. |
|
SDIOSetCurrentLimit - Set the maximum peak current needed by one of the SDIO card's functions.
When a card is removed, all allocations of current are set to zero. Because of this, in order to operate properly this function requires an SDIO card in the slot. This function can safely be called from within an interrupt service routine. |
|
SDIOSetPower - Turns an SDIO card function on or off.
This function can safely be called from within an interrupt service routine. However, you should not call SDIOSetPower from your sdioCallbackSelectPowerOn or sdioCallbackSelectPowerOff callback functions. |
|
SDIOTupleWalk - Search an SDIO card function's Card Information Structure (CIS) for a particular data block (tuple) and return the contents of the data block.
|
Top | Developer Home © 2004, PalmOne, Inc. All rights reserved. Generated on Sun May 8 23:46:35 2005 for palmOne SDIO API |