|
Linux Kernel
3.7.1
|
All Data Structures Namespaces Files Functions Variables Typedefs Enumerations Enumerator Macros Groups Pages
|
Linux Kernel
3.7.1
|
Go to the source code of this file.
Data Structures | |
| struct | sci_timer |
| struct | sci_base_state_machine |
| struct | sci_base_state |
Typedefs | |
| typedef void(* | sci_state_transition_t )(struct sci_base_state_machine *sm) |
Functions | |
| irqreturn_t | isci_msix_isr (int vec, void *data) |
| irqreturn_t | isci_intx_isr (int vec, void *data) |
| irqreturn_t | isci_error_isr (int vec, void *data) |
| void | sci_init_sm (struct sci_base_state_machine *sm, const struct sci_base_state *state_table, u32 initial_state) |
| void | sci_change_state (struct sci_base_state_machine *sm, u32 next_state) |
Variables | |
| unsigned char | no_outbound_task_to |
| u16 | ssp_max_occ_to |
| u16 | stp_max_occ_to |
| u16 | ssp_inactive_to |
| u16 | stp_inactive_to |
| unsigned char | phy_gen |
| unsigned char | max_concurr_spinup |
| uint | cable_selection_override |
| #define ISCI_CAN_QUEUE_VAL 250 /* < SCI_MAX_IO_REQUESTS ? */ |
| #define SCI_MAX_DOMAINS SCI_MAX_PORTS |
| #define SCI_MAX_PORTS SCI_MAX_PHYS |
| #define SCI_MAX_SCATTER_GATHER_ELEMENTS 130 /* not silicon constrained */ |
| #define SCU_MAX_COMPLETION_QUEUE_ENTRIES |
| #define SCU_MAX_COMPLETION_QUEUE_SHIFT (ilog2(SCU_MAX_COMPLETION_QUEUE_ENTRIES)) |
| #define SCU_MAX_EVENTS (1 << SCU_MAX_EVENTS_SHIFT) |
| typedef void(* sci_state_transition_t)(struct sci_base_state_machine *sm) |
| enum sci_io_status |
enum sci_io_status - This enumeration depicts all of the possible IO completion status values. Each value in this enumeration maps directly to a value in the enum sci_status enumeration. Please refer to that enumeration for detailed comments concerning what the status represents.
Add the API to retrieve the SCU status from the core. Check to see that the following status are properly handled: - SCI_IO_FAILURE_UNSUPPORTED_PROTOCOL
| enum sci_status |
enum sci_status - This is the general return status enumeration for non-IO, non-task management related SCI interface methods.
| SCI_SUCCESS |
This member indicates successful completion. |
| SCI_SUCCESS_IO_COMPLETE_BEFORE_START |
This value indicates that the calling method completed successfully, but that the IO may have completed before having it's start method invoked. This occurs during SAT translation for requests that do not require an IO to the target or for any other requests that may be completed without having to submit IO. |
| SCI_SUCCESS_IO_DONE_EARLY |
This Value indicates that the SCU hardware returned an early response because the io request specified more data than is returned by the target device (mode pages, inquiry data, etc.). The completion routine will handle this case to get the actual number of bytes transferred. |
| SCI_WARNING_ALREADY_IN_STATE |
This member indicates that the object for which a state change is being requested is already in said state. |
| SCI_WARNING_TIMER_CONFLICT |
This member indicates interrupt coalescence timer may cause SAS specification compliance issues (i.e. SMP target mode response frames must be returned within 1.9 milliseconds). |
| SCI_WARNING_SEQUENCE_INCOMPLETE |
This field indicates a sequence of action is not completed yet. Mostly, this status is used when multiple ATA commands are needed in a SATI translation. |
| SCI_FAILURE |
This member indicates that there was a general failure. |
| SCI_FATAL_ERROR |
This member indicates that the SCI implementation is unable to complete an operation due to a critical flaw the prevents any further operation (i.e. an invalid pointer). |
| SCI_FAILURE_INVALID_STATE |
This member indicates the calling function failed, because the state of the controller is in a state that prevents successful completion. |
| SCI_FAILURE_INSUFFICIENT_RESOURCES |
This member indicates the calling function failed, because there is insufficient resources/memory to complete the request. |
| SCI_FAILURE_CONTROLLER_NOT_FOUND |
This member indicates the calling function failed, because the controller object required for the operation can't be located. |
| SCI_FAILURE_UNSUPPORTED_CONTROLLER_TYPE |
This member indicates the calling function failed, because the discovered controller type is not supported by the library. |
| SCI_FAILURE_UNSUPPORTED_INIT_DATA_VERSION |
This member indicates the calling function failed, because the requested initialization data version isn't supported. |
| SCI_FAILURE_UNSUPPORTED_PORT_CONFIGURATION |
This member indicates the calling function failed, because the requested configuration of SAS Phys into SAS Ports is not supported. |
| SCI_FAILURE_UNSUPPORTED_PROTOCOL |
This member indicates the calling function failed, because the requested protocol is not supported by the remote device, port, or controller. |
| SCI_FAILURE_UNSUPPORTED_INFORMATION_TYPE |
This member indicates the calling function failed, because the requested information type is not supported by the SCI implementation. |
| SCI_FAILURE_DEVICE_EXISTS |
This member indicates the calling function failed, because the device already exists. |
| SCI_FAILURE_ADDING_PHY_UNSUPPORTED |
This member indicates the calling function failed, because adding a phy to the object is not possible. |
| SCI_FAILURE_UNSUPPORTED_INFORMATION_FIELD |
This member indicates the calling function failed, because the requested information type is not supported by the SCI implementation. |
| SCI_FAILURE_UNSUPPORTED_TIME_LIMIT |
This member indicates the calling function failed, because the SCI implementation does not support the supplied time limit. |
| SCI_FAILURE_INVALID_PHY |
This member indicates the calling method failed, because the SCI implementation does not contain the specified Phy. |
| SCI_FAILURE_INVALID_PORT |
This member indicates the calling method failed, because the SCI implementation does not contain the specified Port. |
| SCI_FAILURE_RESET_PORT_PARTIAL_SUCCESS |
This member indicates the calling method was partly successful The port was reset but not all phys in port are operational |
| SCI_FAILURE_RESET_PORT_FAILURE |
This member indicates that calling method failed The port reset did not complete because none of the phys are operational |
| SCI_FAILURE_INVALID_REMOTE_DEVICE |
This member indicates the calling method failed, because the SCI implementation does not contain the specified remote device. |
| SCI_FAILURE_REMOTE_DEVICE_RESET_REQUIRED |
This member indicates the calling method failed, because the remote device is in a bad state and requires a reset. |
| SCI_FAILURE_INVALID_IO_TAG |
This member indicates the calling method failed, because the SCI implementation does not contain or support the specified IO tag. |
| SCI_FAILURE_IO_RESPONSE_VALID |
This member indicates that the operation failed and the user should check the response data associated with the IO. |
| SCI_FAILURE_CONTROLLER_SPECIFIC_IO_ERR |
This member indicates that the operation failed, the failure is controller implementation specific, and the response data associated with the request is not valid. You can query for the controller specific error information via sci_controller_get_request_status() |
| SCI_FAILURE_IO_TERMINATED |
This member indicated that the operation failed because the user requested this IO to be terminated. |
| SCI_FAILURE_IO_REQUIRES_SCSI_ABORT |
This member indicates that the operation failed and the associated request requires a SCSI abort task to be sent to the target. |
| SCI_FAILURE_DEVICE_NOT_FOUND |
This member indicates that the operation failed because the supplied device could not be located. |
| SCI_FAILURE_INVALID_ASSOCIATION |
This member indicates that the operation failed because the objects association is required and is not correctly set. |
| SCI_FAILURE_TIMEOUT |
This member indicates that the operation failed, because a timeout occurred. |
| SCI_FAILURE_INVALID_PARAMETER_VALUE |
This member indicates that the operation failed, because the user specified a value that is either invalid or not supported. |
| SCI_FAILURE_UNSUPPORTED_MESSAGE_COUNT |
This value indicates that the operation failed, because the number of messages (MSI-X) is not supported. |
| SCI_FAILURE_NO_NCQ_TAG_AVAILABLE |
This value indicates that the method failed due to a lack of available NCQ tags. |
| SCI_FAILURE_PROTOCOL_VIOLATION |
This value indicates that a protocol violation has occurred on the link. |
| SCI_FAILURE_RETRY_REQUIRED |
This value indicates a failure condition that retry may help to clear. |
| SCI_FAILURE_RETRY_LIMIT_REACHED |
This field indicates the retry limit was reached when a retry is attempted |
| SCI_FAILURE_RESET_DEVICE_PARTIAL_SUCCESS |
This member indicates the calling method was partly successful. Mostly, this status is used when a LUN_RESET issued to an expander attached STP device in READY NCQ substate needs to have RNC suspended/resumed before posting TC. |
| SCI_FAILURE_ILLEGAL_ROUTING_ATTRIBUTE_CONFIGURATION |
This field indicates an illegal phy connection based on the routing attribute of both expander phy attached to each other. |
| SCI_FAILURE_EXCEED_MAX_ROUTE_INDEX |
This field indicates a CONFIG ROUTE INFO command has a response with function result INDEX DOES NOT EXIST, usually means exceeding max route index. |
| SCI_FAILURE_UNSUPPORTED_PCI_DEVICE_ID |
This value indicates that an unsupported PCI device ID has been specified. This indicates that attempts to invoke sci_library_allocate_controller() will fail. |
| enum sci_task_status |
enum sci_task_status - This enumeration depicts all of the possible task completion status values. Each value in this enumeration maps directly to a value in the enum sci_status enumeration. Please refer to that enumeration for detailed comments concerning what the status represents.
Check to see that the following status are properly handled:
| irqreturn_t isci_error_isr | ( | int | vec, |
| void * | data | ||
| ) |
| irqreturn_t isci_intx_isr | ( | int | vec, |
| void * | data | ||
| ) |
| irqreturn_t isci_msix_isr | ( | int | vec, |
| void * | data | ||
| ) |
| void sci_change_state | ( | struct sci_base_state_machine * | sm, |
| u32 | next_state | ||
| ) |
| void sci_init_sm | ( | struct sci_base_state_machine * | sm, |
| const struct sci_base_state * | state_table, | ||
| u32 | initial_state | ||
| ) |
1.8.2