struct_regulator_ops(9) [suse man page]
STRUCT
REGULATOR_OPS(9) API reference STRUCT REGULATOR_OPS(9) NAME
struct_regulator_ops - regulator operations. SYNOPSIS
struct regulator_ops { int (* list_voltage) (struct regulator_dev *, unsigned selector); int (* set_voltage) (struct regulator_dev *, int min_uV, int max_uV); int (* get_voltage) (struct regulator_dev *); int (* set_current_limit) (struct regulator_dev *,int min_uA, int max_uA); int (* get_current_limit) (struct regulator_dev *); int (* enable) (struct regulator_dev *); int (* disable) (struct regulator_dev *); int (* is_enabled) (struct regulator_dev *); int (* set_mode) (struct regulator_dev *, unsigned int mode); unsigned int (* get_mode) (struct regulator_dev *); int (* enable_time) (struct regulator_dev *); int (* get_status) (struct regulator_dev *); unsigned int (* get_optimum_mode) (struct regulator_dev *, int input_uV,int output_uV, int load_uA); int (* set_suspend_voltage) (struct regulator_dev *, int uV); int (* set_suspend_enable) (struct regulator_dev *); int (* set_suspend_disable) (struct regulator_dev *); int (* set_suspend_mode) (struct regulator_dev *, unsigned int mode); }; MEMBERS
list_voltage Return one of the supported voltages, in microvolts; zero if the selector indicates a voltage that is unusable on this system; or negative errno. Selectors range from zero to one less than regulator_desc.n_voltages. Voltages may be reported in any order. set_voltage Set the voltage for the regulator within the range specified. The driver should select the voltage closest to min_uV. get_voltage Return the currently configured voltage for the regulator. set_current_limit Configure a limit for a current-limited regulator. get_current_limit Get the configured limit for a current-limited regulator. enable Configure the regulator as enabled. disable Configure the regulator as disabled. is_enabled Return 1 if the regulator is enabled, 0 if not. May also return negative errno. set_mode Set the configured operating mode for the regulator. get_mode Get the configured operating mode for the regulator. enable_time Time taken for the regulator voltage output voltage to stabalise after being enabled, in microseconds. get_status Return actual (not as-configured) status of regulator, as a REGULATOR_STATUS value (or negative errno) get_optimum_mode Get the most efficient operating mode for the regulator when running with the specified parameters. set_suspend_voltage Set the voltage for the regulator when the system is suspended. set_suspend_enable Mark the regulator as enabled when the system is suspended. set_suspend_disable Mark the regulator as disabled when the system is suspended. set_suspend_mode Set the operating mode for the regulator when the system is suspended. DESCRIPTION
This struct describes regulator operations which can be implemented by regulator chip drivers. AUTHORS
Liam Girdwood <lrg@slimlogic.co.uk> Author. Mark Brown <broonie@opensource.wolfsonmicro.com> Wolfson Microelectronics, Author. COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 STRUCT REGULATOR_OPS(9)
Check Out this Related Man Page
STRUCT
USB_DRIVER(9) Host-Side Data Types and Macro STRUCT USB_DRIVER(9) NAME
struct_usb_driver - identifies USB interface driver to usbcore SYNOPSIS
struct usb_driver { const char * name; int (* probe) (struct usb_interface *intf,const struct usb_device_id *id); void (* disconnect) (struct usb_interface *intf); int (* ioctl) (struct usb_interface *intf, unsigned int code,void *buf); int (* suspend) (struct usb_interface *intf, pm_message_t message); int (* resume) (struct usb_interface *intf); int (* reset_resume) (struct usb_interface *intf); int (* pre_reset) (struct usb_interface *intf); int (* post_reset) (struct usb_interface *intf); const struct usb_device_id * id_table; struct usb_dynids dynids; struct usbdrv_wrap drvwrap; unsigned int no_dynamic_id:1; unsigned int supports_autosuspend:1; unsigned int soft_unbind:1; }; MEMBERS
name The driver name should be unique among USB drivers, and should normally be the same as the module name. probe Called to see if the driver is willing to manage a particular interface on a device. If it is, probe returns zero and uses usb_set_intfdata to associate driver-specific data with the interface. It may also use usb_set_interface to specify the appropriate altsetting. If unwilling to manage the interface, return -ENODEV, if genuine IO errors occured, an appropriate negative errno value. disconnect Called when the interface is no longer accessible, usually because its device has been (or is being) disconnected or the driver module is being unloaded. ioctl Used for drivers that want to talk to userspace through the "usbfs" filesystem. This lets devices provide ways to expose information to user space regardless of where they do (or don't) show up otherwise in the filesystem. suspend Called when the device is going to be suspended by the system. resume Called when the device is being resumed by the system. reset_resume Called when the suspended device has been reset instead of being resumed. pre_reset Called by usb_reset_device when the device is about to be reset. post_reset Called by usb_reset_device after the device has been reset id_table USB drivers use ID table to support hotplugging. Export this with MODULE_DEVICE_TABLE(usb,...). This must be set or your driver's probe function will never get called. dynids used internally to hold the list of dynamically added device ids for this driver. drvwrap Driver-model core structure wrapper. no_dynamic_id if set to 1, the USB core will not allow dynamic ids to be added to this driver by preventing the sysfs file from being created. supports_autosuspend if set to 0, the USB core will not allow autosuspend for interfaces bound to this driver. soft_unbind if set to 1, the USB core will not kill URBs and disable endpoints before calling the driver's disconnect method. DESCRIPTION
USB interface drivers must provide a name, probe and disconnect methods, and an id_table. Other driver fields are optional. The id_table is used in hotplugging. It holds a set of descriptors, and specialized data may be associated with each entry. That table is used by both user and kernel mode hotplugging support. The probe and disconnect methods are called in a context where they can sleep, but they should avoid abusing the privilege. Most work to connect to a device should be done when the device is opened, and undone at the last close. The disconnect code needs to address concurrency issues with respect to open and close methods, as well as forcing all pending I/O requests to complete (by unlinking them as necessary, and blocking until the unlinks complete). COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 STRUCT USB_DRIVER(9)