Linux Kernel  3.7.1
 All Data Structures Namespaces Files Functions Variables Typedefs Enumerations Enumerator Macros Groups Pages
pointer Interface Reference

Detailed Description

struct subsys_private - structure to hold the private to the driver core portions of the bus_type/class structure.

- the struct kset that defines this subsystem - the subsystem's 'devices' directory - list of subsystem interfaces associated - protect the devices, and interfaces lists.

- the list of drivers associated - the klist to iterate over the - the klist to iterate over the - the bus notifier list for anything that cares about things on this bus. - pointer back to the struct bus_type that this structure is associated with.

- "glue" directory to put in-between the parent device to avoid namespace conflicts the struct class that this structure is associated with.

This structure is the one that is the actual kobject allowing struct bus_type/class to be statically allocated safely. Nothing outside of the driver core should ever touch these fields.

device_create_vargs - creates a device and registers it with sysfs struct class that this device should be registered to : pointer to the parent struct device of this new device, if any : the dev_t for the char device to be added : the data to be added to the device for callbacks : string for the device's name : va_list for the device's name

This function can be used by char device classes. A struct device will be created in sysfs, registered to the specified class.

A "dev" file will be created, showing the dev_t for the device, if the dev_t is not 0,0. If a pointer to a parent struct device is passed in, the newly created struct device will be a child of that device in sysfs. The pointer to the struct device will be returned from the call. Any further sysfs files that might be required can be created using this pointer.

Returns &struct device pointer on success, or ERR_PTR() on error.

Note: the struct class passed to this function must have previously been created with a call to class_create().

device_create - creates a device and registers it with sysfs struct class that this device should be registered to : pointer to the parent struct device of this new device, if any : the dev_t for the char device to be added : the data to be added to the device for callbacks : string for the device's name

This function can be used by char device classes. A struct device will be created in sysfs, registered to the specified class.

A "dev" file will be created, showing the dev_t for the device, if the dev_t is not 0,0. If a pointer to a parent struct device is passed in, the newly created struct device will be a child of that device in sysfs. The pointer to the struct device will be returned from the call. Any further sysfs files that might be required can be created using this pointer.

Returns &struct device pointer on success, or ERR_PTR() on error.

Note: the struct class passed to this function must have previously been created with a call to class_create().

device_destroy - removes a device that was created with device_create() struct class that this device was registered with : the dev_t of the device that was previously registered

This call unregisters and cleans up a device that was created with a call to device_create().

usb_serial - structure used by the usb-serial core for a device : pointer to the struct usb_device for this device : pointer to the struct usb_serial_driver for this device struct usb_interface for this device : the starting minor number for this device : the number of ports this device has : number of interrupt in endpoints we have : number of interrupt out endpoints we have : number of bulk in endpoints we have : number of bulk out endpoints we have : array of struct usb_serial_port structures for the different ports. : place to put any driver specific information that is needed. The usb-serial driver is required to manage this data, the usb-serial core will not touch this. Use usb_get_serial_data() and usb_set_serial_data() to access this.


The documentation for this interface was generated from the following file: