2005-04-16 16:20:36 -06:00
|
|
|
/*
|
2007-02-22 17:37:53 -07:00
|
|
|
* This file holds USB constants and structures that are needed for
|
|
|
|
* USB device APIs. These are used by the USB device model, which is
|
|
|
|
* defined in chapter 9 of the USB 2.0 specification and in the
|
|
|
|
* Wireless USB 1.0 (spread around). Linux has several APIs in C that
|
|
|
|
* need these:
|
2005-04-16 16:20:36 -06:00
|
|
|
*
|
|
|
|
* - the master/host side Linux-USB kernel driver API;
|
|
|
|
* - the "usbfs" user space API; and
|
[PATCH] USB: wireless usb <linux/usb_ch9.h> declarations
This provides declarations for new requests, descriptors, and bitfields as
defined in the Wireless USB 1.0 spec. Device support will involve a new
"Wire Adapter" device class, connecting a USB Host to a cluster of wireless
USB devices. There will be two adapter types:
* Host Wireless Adapter (HWA): the downstream link is wireless, which
connects a wireless USB host to wireless USB devices (not unlike like
a hub) including to the second type of adapter.
* Device Wireless Adapter (DWA): the upstream link is wireless, for
connecting existing USB devices through wired links into the cluser.
All wireless USB devices will need persistent (and secure!) key storage, and
it's probable that Linux -- or device firmware -- will need to be involved
with that to bootstrap the initial secure key exchange.
Some user interface is required in that initial key exchange, and since the
most "hands-off" one is a wired USB link, I suspect wireless operation will
usually not be the only mode for wireless USB devices. (Plus, devices can
recharge batteries using wired USB...) All other key exchange protocols need
error prone user interactions, like copying and/or verifying keys.
It'll likely be a while before we have commercial Wireless USB hardware,
much less Linux implementations that know how to use it.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2005-05-31 11:21:11 -06:00
|
|
|
* - the Linux "gadget" slave/device/peripheral side driver API.
|
2005-04-16 16:20:36 -06:00
|
|
|
*
|
|
|
|
* USB 2.0 adds an additional "On The Go" (OTG) mode, which lets systems
|
|
|
|
* act either as a USB master/host or as a USB slave/device. That means
|
[PATCH] USB: wireless usb <linux/usb_ch9.h> declarations
This provides declarations for new requests, descriptors, and bitfields as
defined in the Wireless USB 1.0 spec. Device support will involve a new
"Wire Adapter" device class, connecting a USB Host to a cluster of wireless
USB devices. There will be two adapter types:
* Host Wireless Adapter (HWA): the downstream link is wireless, which
connects a wireless USB host to wireless USB devices (not unlike like
a hub) including to the second type of adapter.
* Device Wireless Adapter (DWA): the upstream link is wireless, for
connecting existing USB devices through wired links into the cluser.
All wireless USB devices will need persistent (and secure!) key storage, and
it's probable that Linux -- or device firmware -- will need to be involved
with that to bootstrap the initial secure key exchange.
Some user interface is required in that initial key exchange, and since the
most "hands-off" one is a wired USB link, I suspect wireless operation will
usually not be the only mode for wireless USB devices. (Plus, devices can
recharge batteries using wired USB...) All other key exchange protocols need
error prone user interactions, like copying and/or verifying keys.
It'll likely be a while before we have commercial Wireless USB hardware,
much less Linux implementations that know how to use it.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2005-05-31 11:21:11 -06:00
|
|
|
* the master and slave side APIs benefit from working well together.
|
|
|
|
*
|
|
|
|
* There's also "Wireless USB", using low power short range radios for
|
|
|
|
* peripheral interconnection but otherwise building on the USB framework.
|
2007-02-22 17:37:53 -07:00
|
|
|
*
|
|
|
|
* Note all descriptors are declared '__attribute__((packed))' so that:
|
|
|
|
*
|
|
|
|
* [a] they never get padded, either internally (USB spec writers
|
|
|
|
* probably handled that) or externally;
|
|
|
|
*
|
|
|
|
* [b] so that accessing bigger-than-a-bytes fields will never
|
|
|
|
* generate bus errors on any platform, even when the location of
|
|
|
|
* its descriptor inside a bundle isn't "naturally aligned", and
|
|
|
|
*
|
|
|
|
* [c] for consistency, removing all doubt even when it appears to
|
|
|
|
* someone that the two other points are non-issues for that
|
|
|
|
* particular descriptor type.
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
|
|
|
#ifndef __LINUX_USB_CH9_H
|
|
|
|
#define __LINUX_USB_CH9_H
|
|
|
|
|
2012-10-09 02:49:07 -06:00
|
|
|
#include <uapi/linux/usb/ch9.h>
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2011-08-30 09:11:19 -06:00
|
|
|
|
|
|
|
/**
|
|
|
|
* usb_speed_string() - Returns human readable-name of the speed.
|
|
|
|
* @speed: The speed to return human-readable name for. If it's not
|
|
|
|
* any of the speeds defined in usb_device_speed enum, string for
|
|
|
|
* USB_SPEED_UNKNOWN will be returned.
|
|
|
|
*/
|
|
|
|
extern const char *usb_speed_string(enum usb_device_speed speed);
|
|
|
|
|
2013-01-24 13:29:48 -07:00
|
|
|
|
|
|
|
/**
|
|
|
|
* usb_state_string - Returns human readable name for the state.
|
|
|
|
* @state: The state to return a human-readable name for. If it's not
|
|
|
|
* any of the states devices in usb_device_state_string enum,
|
|
|
|
* the string UNKNOWN will be returned.
|
|
|
|
*/
|
|
|
|
extern const char *usb_state_string(enum usb_device_state state);
|
|
|
|
|
2008-03-07 11:45:32 -07:00
|
|
|
#endif /* __LINUX_USB_CH9_H */
|