struct_usb_interface - what usb device drivers talk to
2. SYNOPSIS ▲
*usb_dev; atomic_t pm_usage_cnt;
3. MEMBERS ▲
array of interface structures, one for each alternate setting that may be selected. Each one includes a set of endpoint configurations. They will be in no particular order.
the current altsetting.
number of altsettings defined.
interface association descriptor
the minor number assigned to this interface, if this interface is bound to a driver that uses the USB major number. If this interface does not use the USB major, this field should be unused. The driver should set this value in the probe function of the driver, after it has been assigned a minor number from the USB core by calling usb_register_dev.
binding state of the interface: not bound, binding (in probe), bound to a driver, or unbinding (in disconnect)
sysfs attributes exist
endpoint child pseudo-devices exist
flag set when the interface is being unregistered
flag set when the driver requires remote-wakeup capability during autosuspend.
flag set when a set-interface request for altsetting 0 has been deferred.
flag set when the driver should be re-probed or unbound following a reset or suspend operation it doesnAqt support.
set to 1 if the interface is currently running a queued reset so that usb_cancel_queued_reset doesnAqt try to remove from the workqueue when running inside the worker thread. See __usb_queue_reset_device.
USB core reset the device, so use alt setting 0 as current; needs bandwidth alloc after reset.
driver modelAqs view of this device
if an interface is bound to the USB major, this will point to the sysfs representation for that device.
PM usage counter for this interface
Used for scheduling resets from atomic context.
4. DESCRIPTION ▲
USB device drivers attach to interfaces on a physical device. Each interface encapsulates a single high level function, such as feeding an audio stream to a speaker or reporting a change in a volume control. Many USB devices only have one interface. The protocol used to talk to an interfaceAqs endpoints can be defined in a usb « class » specification, or by a productAqs vendor. The (default) control endpoint is part of every interface, but is never listed among the interfaceAqs descriptors.
The driver that is bound to the interface can use standard driver model calls such as dev_get_drvdata on the dev member of this structure.
Each interface may have alternate settings. The initial configuration of a device sets altsetting 0, but the device driver can change that setting using usb_set_interface. Alternate settings are often used to control the use of periodic endpoints, such as by having different endpoints use different amounts of reserved USB bandwidth. All standards-conformant USB devices that use isochronous endpoints will use them in non-default settings.
The USB specification says that alternate setting numbers must run from 0 to one less than the total number of alternate settings. But some devices manage to mess this up, and the structures arenAqt necessarily stored in numerical order anyhow. Use usb_altnum_to_altsetting to look up an alternate setting in the altsetting array based on its number.
5. COPYRIGHT ▲