|
Linux Kernel
3.7.1
|
All Data Structures Namespaces Files Functions Variables Typedefs Enumerations Enumerator Macros Groups Pages
|
Linux Kernel
3.7.1
|
Initialize and start the SPI interface.
the packet interface to configure and use as a SPI interface. : The operating mode for the SPI interface. The interface can operate as a full duplex (both Tx and Rx data paths active) or as a halfplex (either the Tx data path is active or the Rx data path is active, but not both). : Timeout to wait for clock synchronization in seconds : Number of SPI ports to configure
Returns Zero on success, negative of failure.
This routine restarts the SPI interface after it has lost synchronization with its correspondent system.
the packet interface to configure and use as a SPI interface. : The operating mode for the SPI interface. The interface can operate as a full duplex (both Tx and Rx data paths active) or as a halfplex (either the Tx data path is active or the Rx data path is active, but not both). : Timeout to wait for clock synchronization in seconds
Returns Zero on success, negative of failure.
Callback to perform SPI4 reset
the packet interface to configure and use as a SPI interface. : The operating mode for the SPI interface. The interface can operate as a full duplex (both Tx and Rx data paths active) or as a halfplex (either the Tx data path is active or the Rx data path is active, but not both).
Returns Zero on success, non-zero error code on failure (will cause SPI initialization to abort)
Callback to setup calendar and miscellaneous settings before clock detection
the packet interface to configure and use as a SPI interface. : The operating mode for the SPI interface. The interface can operate as a full duplex (both Tx and Rx data paths active) or as a halfplex (either the Tx data path is active or the Rx data path is active, but not both). : Number of ports to configure on SPI
Returns Zero on success, non-zero error code on failure (will cause SPI initialization to abort)
Callback to perform clock detection
the packet interface to configure and use as a SPI interface. : The operating mode for the SPI interface. The interface can operate as a full duplex (both Tx and Rx data paths active) or as a halfplex (either the Tx data path is active or the Rx data path is active, but not both). : Timeout to wait for clock synchronization in seconds
Returns Zero on success, non-zero error code on failure (will cause SPI initialization to abort)
Callback to perform link training
the packet interface to configure and use as a SPI interface. : The operating mode for the SPI interface. The interface can operate as a full duplex (both Tx and Rx data paths active) or as a halfplex (either the Tx data path is active or the Rx data path is active, but not both). : Timeout to wait for link to be trained (in seconds)
Returns Zero on success, non-zero error code on failure (will cause SPI initialization to abort)
Callback to perform calendar data synchronization
the packet interface to configure and use as a SPI interface. : The operating mode for the SPI interface. The interface can operate as a full duplex (both Tx and Rx data paths active) or as a halfplex (either the Tx data path is active or the Rx data path is active, but not both). : Timeout to wait for calendar data in seconds
Returns Zero on success, non-zero error code on failure (will cause SPI initialization to abort)
Callback to handle interface up
the packet interface to configure and use as a SPI interface. : The operating mode for the SPI interface. The interface can operate as a full duplex (both Tx and Rx data paths active) or as a halfplex (either the Tx data path is active or the Rx data path is active, but not both).
Returns Zero on success, non-zero error code on failure (will cause SPI initialization to abort)
This routine restarts the SPI interface after it has lost synchronization with its corespondant system.
the packet interface to configure and use as a SPI interface. : The operating mode for the SPI interface. The interface can operate as a full duplex (both Tx and Rx data paths active) or as a halfplex (either the Tx data path is active or the Rx data path is active, but not both). : Timeout to wait for clock synchronization in seconds Returns Zero on success, negative of failure.
ps3_spe_irq_setup - Setup an spe virq. : enum ps3_cpu_binding indicating the cpu the interrupt should be serviced on. : The spe_id returned from lv1_construct_logical_spe(). class {0,1,2}. : The assigned Linux virq.
fc_exch_mgr_alloc() - Allocate an exchange manager : The local port that the new EM will be associated with class for new exchanges : The minimum XID for exchanges from the new EM : The maximum XID for exchanges from the new EM : The match routine for the new EM
struct device - The basic device structure : The device's "parent" device, the device to which it is attached. In most cases, a parent device is some sort of bus or host controller. If parent is NULL, the device, is a top-level device, which is not usually what you want. : Holds the private data of the driver core portions of the device. See the comment of the struct device_private for detail. : A top-level, abstract class from which other classes are derived. : Initial name of the device. : The type of device. This identifies the device type and carries type-specific information. : Mutex to synchronize calls to its driver. : Type of bus device is on. : Which driver has allocated this : Platform data specific to the device. Example: For devices on custom boards, as typical of embedded and SOC based hardware, Linux often uses platform_data to point to board-specific structures describing devices and how they are wired. That can include what ports are available, chip variants, which GPIO pins act in what additional roles, and so on. This shrinks the "Board Support Packages" (BSPs) and minimizes board-specific #ifdefs in drivers. : For device power management. See Documentation/power/devices.txt for details. : Provide callbacks that are executed during system suspend, hibernation, system resume and during runtime PM transitions along with subsystem-level and driver-level callbacks. : NUMA node this device is close to. : Dma mask (if dma'ble device). : Like dma_mask, but for alloc_coherent mapping as not all hardware supports 64-bit addresses for consistent allocations such descriptors. : A low level driver may set these to teach IOMMU code about segment limitations. : Dma pools (if dma'ble device). : Internal for coherent mem override. : For arch-specific additions. : Associated device tree node. : For creating the sysfs "dev". : device instance : Spinlock to protect the resource of the device. : The resources list of the device. : The node used to add the device to the class list. the device. : Optional attribute groups. : Callback to free the device after all references have gone away. This should be set by the allocator of the device (i.e. the bus driver that discovered the device).
At the lowest level, every device in a Linux system is represented by an instance of struct device. The device structure contains the information that the device model core needs to model the system. Most subsystems, however, track additional information about the devices they host. As a result, it is rare for devices to be represented by bare device structures; instead, that structure, like kobject structures, is usually embedded within a higher-level representation of the device.
struct fc_exch - Fibre Channel Exchange : Exchange manager : Exchange pool : The exchange's state : The exchange ID : Handle used by the EM to track free exchanges : Lock that protects the exchange : Reference count : Handle for timeout handler : The local port that this exchange is on : Originator's exchange ID : Responder's exchange ID : Originator's FCID : Source FCID : Destination FCID : ESB exchange status : Resouce allocation time out value (in msecs) : The next sequence ID to use : encapsulation information for lower-level driver : F_CTL flags for the sequence : The frame type service : The sequence in use on this exchange : Callback for responses on this exchange : Called when destroying the exchange
Locking notes: The ex_lock protects following items: state, esb_stat, f_ctl, seq.ssb_stat seq_id sequence allocation
1.8.2