]>
Commit | Line | Data |
---|---|---|
1da177e4 | 1 | /* |
9454a57a | 2 | * <linux/usb/gadget.h> |
1da177e4 LT |
3 | * |
4 | * We call the USB code inside a Linux-based peripheral device a "gadget" | |
5 | * driver, except for the hardware-specific bus glue. One USB host can | |
6 | * master many USB gadgets, but the gadgets are only slaved to one host. | |
7 | * | |
8 | * | |
9 | * (C) Copyright 2002-2004 by David Brownell | |
10 | * All Rights Reserved. | |
11 | * | |
12 | * This software is licensed under the GNU GPL version 2. | |
13 | */ | |
14 | ||
15 | #ifndef __LINUX_USB_GADGET_H | |
16 | #define __LINUX_USB_GADGET_H | |
17 | ||
5a0e3ad6 | 18 | #include <linux/slab.h> |
325fd182 | 19 | #include <linux/usb/ch9.h> |
5a0e3ad6 | 20 | |
1da177e4 LT |
21 | struct usb_ep; |
22 | ||
23 | /** | |
24 | * struct usb_request - describes one i/o request | |
25 | * @buf: Buffer used for data. Always provide this; some controllers | |
efc9052e | 26 | * only use PIO, or don't use DMA for some endpoints. |
1da177e4 | 27 | * @dma: DMA address corresponding to 'buf'. If you don't set this |
efc9052e DB |
28 | * field, and the usb controller needs one, it is responsible |
29 | * for mapping and unmapping the buffer. | |
1da177e4 LT |
30 | * @length: Length of that data |
31 | * @no_interrupt: If true, hints that no completion irq is needed. | |
32 | * Helpful sometimes with deep request queues that are handled | |
33 | * directly by DMA controllers. | |
34 | * @zero: If true, when writing data, makes the last packet be "short" | |
35 | * by adding a zero length packet as needed; | |
36 | * @short_not_ok: When reading data, makes short packets be | |
37 | * treated as errors (queue stops advancing till cleanup). | |
38 | * @complete: Function called when request completes, so this request and | |
f579c2b4 AS |
39 | * its buffer may be re-used. The function will always be called with |
40 | * interrupts disabled, and it must not sleep. | |
1da177e4 LT |
41 | * Reads terminate with a short packet, or when the buffer fills, |
42 | * whichever comes first. When writes terminate, some data bytes | |
43 | * will usually still be in flight (often in a hardware fifo). | |
44 | * Errors (for reads or writes) stop the queue from advancing | |
45 | * until the completion function returns, so that any transfers | |
46 | * invalidated by the error may first be dequeued. | |
47 | * @context: For use by the completion callback | |
48 | * @list: For use by the gadget driver. | |
49 | * @status: Reports completion code, zero or a negative errno. | |
efc9052e DB |
50 | * Normally, faults block the transfer queue from advancing until |
51 | * the completion callback returns. | |
52 | * Code "-ESHUTDOWN" indicates completion caused by device disconnect, | |
53 | * or when the driver disabled the endpoint. | |
1da177e4 | 54 | * @actual: Reports bytes transferred to/from the buffer. For reads (OUT |
efc9052e DB |
55 | * transfers) this may be less than the requested length. If the |
56 | * short_not_ok flag is set, short reads are treated as errors | |
57 | * even when status otherwise indicates successful completion. | |
58 | * Note that for writes (IN transfers) some data bytes may still | |
59 | * reside in a device-side FIFO when the request is reported as | |
1da177e4 LT |
60 | * complete. |
61 | * | |
62 | * These are allocated/freed through the endpoint they're used with. The | |
63 | * hardware's driver can add extra per-request data to the memory it returns, | |
64 | * which often avoids separate memory allocations (potential failures), | |
65 | * later when the request is queued. | |
66 | * | |
67 | * Request flags affect request handling, such as whether a zero length | |
68 | * packet is written (the "zero" flag), whether a short read should be | |
69 | * treated as an error (blocking request queue advance, the "short_not_ok" | |
70 | * flag), or hinting that an interrupt is not required (the "no_interrupt" | |
71 | * flag, for use with deep request queues). | |
72 | * | |
73 | * Bulk endpoints can use any size buffers, and can also be used for interrupt | |
74 | * transfers. interrupt-only endpoints can be much less functional. | |
41dceed5 | 75 | * |
25985edc | 76 | * NOTE: this is analogous to 'struct urb' on the host side, except that |
41dceed5 | 77 | * it's thinner and promotes more pre-allocation. |
1da177e4 | 78 | */ |
1da177e4 LT |
79 | |
80 | struct usb_request { | |
81 | void *buf; | |
82 | unsigned length; | |
83 | dma_addr_t dma; | |
84 | ||
85 | unsigned no_interrupt:1; | |
86 | unsigned zero:1; | |
87 | unsigned short_not_ok:1; | |
88 | ||
89 | void (*complete)(struct usb_ep *ep, | |
90 | struct usb_request *req); | |
91 | void *context; | |
92 | struct list_head list; | |
93 | ||
94 | int status; | |
95 | unsigned actual; | |
96 | }; | |
97 | ||
98 | /*-------------------------------------------------------------------------*/ | |
99 | ||
100 | /* endpoint-specific parts of the api to the usb controller hardware. | |
101 | * unlike the urb model, (de)multiplexing layers are not required. | |
102 | * (so this api could slash overhead if used on the host side...) | |
103 | * | |
104 | * note that device side usb controllers commonly differ in how many | |
105 | * endpoints they support, as well as their capabilities. | |
106 | */ | |
107 | struct usb_ep_ops { | |
108 | int (*enable) (struct usb_ep *ep, | |
109 | const struct usb_endpoint_descriptor *desc); | |
110 | int (*disable) (struct usb_ep *ep); | |
111 | ||
112 | struct usb_request *(*alloc_request) (struct usb_ep *ep, | |
55016f10 | 113 | gfp_t gfp_flags); |
1da177e4 LT |
114 | void (*free_request) (struct usb_ep *ep, struct usb_request *req); |
115 | ||
1da177e4 | 116 | int (*queue) (struct usb_ep *ep, struct usb_request *req, |
55016f10 | 117 | gfp_t gfp_flags); |
1da177e4 LT |
118 | int (*dequeue) (struct usb_ep *ep, struct usb_request *req); |
119 | ||
120 | int (*set_halt) (struct usb_ep *ep, int value); | |
a5e54b0d DL |
121 | int (*set_wedge) (struct usb_ep *ep); |
122 | ||
1da177e4 LT |
123 | int (*fifo_status) (struct usb_ep *ep); |
124 | void (*fifo_flush) (struct usb_ep *ep); | |
125 | }; | |
126 | ||
127 | /** | |
128 | * struct usb_ep - device side representation of USB endpoint | |
129 | * @name:identifier for the endpoint, such as "ep-a" or "ep9in-bulk" | |
130 | * @ops: Function pointers used to access hardware-specific operations. | |
131 | * @ep_list:the gadget's ep_list holds all of its endpoints | |
132 | * @maxpacket:The maximum packet size used on this endpoint. The initial | |
133 | * value can sometimes be reduced (hardware allowing), according to | |
134 | * the endpoint descriptor used to configure the endpoint. | |
135 | * @driver_data:for use by the gadget driver. all other fields are | |
efc9052e | 136 | * read-only to gadget drivers. |
1da177e4 LT |
137 | * |
138 | * the bus controller driver lists all the general purpose endpoints in | |
139 | * gadget->ep_list. the control endpoint (gadget->ep0) is not in that list, | |
140 | * and is accessed only in response to a driver setup() callback. | |
141 | */ | |
142 | struct usb_ep { | |
143 | void *driver_data; | |
144 | ||
145 | const char *name; | |
146 | const struct usb_ep_ops *ops; | |
147 | struct list_head ep_list; | |
148 | unsigned maxpacket:16; | |
149 | }; | |
150 | ||
151 | /*-------------------------------------------------------------------------*/ | |
152 | ||
153 | /** | |
154 | * usb_ep_enable - configure endpoint, making it usable | |
155 | * @ep:the endpoint being configured. may not be the endpoint named "ep0". | |
efc9052e | 156 | * drivers discover endpoints through the ep_list of a usb_gadget. |
1da177e4 | 157 | * @desc:descriptor for desired behavior. caller guarantees this pointer |
efc9052e DB |
158 | * remains valid until the endpoint is disabled; the data byte order |
159 | * is little-endian (usb-standard). | |
1da177e4 LT |
160 | * |
161 | * when configurations are set, or when interface settings change, the driver | |
162 | * will enable or disable the relevant endpoints. while it is enabled, an | |
163 | * endpoint may be used for i/o until the driver receives a disconnect() from | |
164 | * the host or until the endpoint is disabled. | |
165 | * | |
166 | * the ep0 implementation (which calls this routine) must ensure that the | |
167 | * hardware capabilities of each endpoint match the descriptor provided | |
168 | * for it. for example, an endpoint named "ep2in-bulk" would be usable | |
169 | * for interrupt transfers as well as bulk, but it likely couldn't be used | |
170 | * for iso transfers or for endpoint 14. some endpoints are fully | |
171 | * configurable, with more generic names like "ep-a". (remember that for | |
172 | * USB, "in" means "towards the USB master".) | |
173 | * | |
174 | * returns zero, or a negative error code. | |
175 | */ | |
41dceed5 GKH |
176 | static inline int usb_ep_enable(struct usb_ep *ep, |
177 | const struct usb_endpoint_descriptor *desc) | |
1da177e4 | 178 | { |
41dceed5 | 179 | return ep->ops->enable(ep, desc); |
1da177e4 LT |
180 | } |
181 | ||
182 | /** | |
183 | * usb_ep_disable - endpoint is no longer usable | |
184 | * @ep:the endpoint being unconfigured. may not be the endpoint named "ep0". | |
185 | * | |
186 | * no other task may be using this endpoint when this is called. | |
187 | * any pending and uncompleted requests will complete with status | |
188 | * indicating disconnect (-ESHUTDOWN) before this call returns. | |
189 | * gadget drivers must call usb_ep_enable() again before queueing | |
190 | * requests to the endpoint. | |
191 | * | |
192 | * returns zero, or a negative error code. | |
193 | */ | |
41dceed5 | 194 | static inline int usb_ep_disable(struct usb_ep *ep) |
1da177e4 | 195 | { |
41dceed5 | 196 | return ep->ops->disable(ep); |
1da177e4 LT |
197 | } |
198 | ||
199 | /** | |
200 | * usb_ep_alloc_request - allocate a request object to use with this endpoint | |
201 | * @ep:the endpoint to be used with with the request | |
202 | * @gfp_flags:GFP_* flags to use | |
203 | * | |
204 | * Request objects must be allocated with this call, since they normally | |
205 | * need controller-specific setup and may even need endpoint-specific | |
206 | * resources such as allocation of DMA descriptors. | |
207 | * Requests may be submitted with usb_ep_queue(), and receive a single | |
208 | * completion callback. Free requests with usb_ep_free_request(), when | |
209 | * they are no longer needed. | |
210 | * | |
211 | * Returns the request, or null if one could not be allocated. | |
212 | */ | |
41dceed5 GKH |
213 | static inline struct usb_request *usb_ep_alloc_request(struct usb_ep *ep, |
214 | gfp_t gfp_flags) | |
1da177e4 | 215 | { |
41dceed5 | 216 | return ep->ops->alloc_request(ep, gfp_flags); |
1da177e4 LT |
217 | } |
218 | ||
219 | /** | |
220 | * usb_ep_free_request - frees a request object | |
221 | * @ep:the endpoint associated with the request | |
222 | * @req:the request being freed | |
223 | * | |
224 | * Reverses the effect of usb_ep_alloc_request(). | |
225 | * Caller guarantees the request is not queued, and that it will | |
226 | * no longer be requeued (or otherwise used). | |
227 | */ | |
41dceed5 GKH |
228 | static inline void usb_ep_free_request(struct usb_ep *ep, |
229 | struct usb_request *req) | |
1da177e4 | 230 | { |
41dceed5 | 231 | ep->ops->free_request(ep, req); |
1da177e4 LT |
232 | } |
233 | ||
1da177e4 LT |
234 | /** |
235 | * usb_ep_queue - queues (submits) an I/O request to an endpoint. | |
236 | * @ep:the endpoint associated with the request | |
237 | * @req:the request being submitted | |
238 | * @gfp_flags: GFP_* flags to use in case the lower level driver couldn't | |
efc9052e | 239 | * pre-allocate all necessary memory with the request. |
1da177e4 LT |
240 | * |
241 | * This tells the device controller to perform the specified request through | |
242 | * that endpoint (reading or writing a buffer). When the request completes, | |
243 | * including being canceled by usb_ep_dequeue(), the request's completion | |
244 | * routine is called to return the request to the driver. Any endpoint | |
245 | * (except control endpoints like ep0) may have more than one transfer | |
246 | * request queued; they complete in FIFO order. Once a gadget driver | |
247 | * submits a request, that request may not be examined or modified until it | |
248 | * is given back to that driver through the completion callback. | |
249 | * | |
250 | * Each request is turned into one or more packets. The controller driver | |
251 | * never merges adjacent requests into the same packet. OUT transfers | |
252 | * will sometimes use data that's already buffered in the hardware. | |
253 | * Drivers can rely on the fact that the first byte of the request's buffer | |
254 | * always corresponds to the first byte of some USB packet, for both | |
255 | * IN and OUT transfers. | |
256 | * | |
257 | * Bulk endpoints can queue any amount of data; the transfer is packetized | |
258 | * automatically. The last packet will be short if the request doesn't fill it | |
259 | * out completely. Zero length packets (ZLPs) should be avoided in portable | |
260 | * protocols since not all usb hardware can successfully handle zero length | |
261 | * packets. (ZLPs may be explicitly written, and may be implicitly written if | |
262 | * the request 'zero' flag is set.) Bulk endpoints may also be used | |
263 | * for interrupt transfers; but the reverse is not true, and some endpoints | |
264 | * won't support every interrupt transfer. (Such as 768 byte packets.) | |
265 | * | |
266 | * Interrupt-only endpoints are less functional than bulk endpoints, for | |
267 | * example by not supporting queueing or not handling buffers that are | |
268 | * larger than the endpoint's maxpacket size. They may also treat data | |
269 | * toggle differently. | |
270 | * | |
271 | * Control endpoints ... after getting a setup() callback, the driver queues | |
272 | * one response (even if it would be zero length). That enables the | |
25985edc | 273 | * status ack, after transferring data as specified in the response. Setup |
1da177e4 LT |
274 | * functions may return negative error codes to generate protocol stalls. |
275 | * (Note that some USB device controllers disallow protocol stall responses | |
276 | * in some cases.) When control responses are deferred (the response is | |
277 | * written after the setup callback returns), then usb_ep_set_halt() may be | |
f579c2b4 AS |
278 | * used on ep0 to trigger protocol stalls. Depending on the controller, |
279 | * it may not be possible to trigger a status-stage protocol stall when the | |
280 | * data stage is over, that is, from within the response's completion | |
281 | * routine. | |
1da177e4 LT |
282 | * |
283 | * For periodic endpoints, like interrupt or isochronous ones, the usb host | |
284 | * arranges to poll once per interval, and the gadget driver usually will | |
285 | * have queued some data to transfer at that time. | |
286 | * | |
287 | * Returns zero, or a negative error code. Endpoints that are not enabled | |
288 | * report errors; errors will also be | |
289 | * reported when the usb peripheral is disconnected. | |
290 | */ | |
41dceed5 GKH |
291 | static inline int usb_ep_queue(struct usb_ep *ep, |
292 | struct usb_request *req, gfp_t gfp_flags) | |
1da177e4 | 293 | { |
41dceed5 | 294 | return ep->ops->queue(ep, req, gfp_flags); |
1da177e4 LT |
295 | } |
296 | ||
297 | /** | |
298 | * usb_ep_dequeue - dequeues (cancels, unlinks) an I/O request from an endpoint | |
299 | * @ep:the endpoint associated with the request | |
300 | * @req:the request being canceled | |
301 | * | |
302 | * if the request is still active on the endpoint, it is dequeued and its | |
303 | * completion routine is called (with status -ECONNRESET); else a negative | |
304 | * error code is returned. | |
305 | * | |
306 | * note that some hardware can't clear out write fifos (to unlink the request | |
307 | * at the head of the queue) except as part of disconnecting from usb. such | |
308 | * restrictions prevent drivers from supporting configuration changes, | |
309 | * even to configuration zero (a "chapter 9" requirement). | |
310 | */ | |
41dceed5 | 311 | static inline int usb_ep_dequeue(struct usb_ep *ep, struct usb_request *req) |
1da177e4 | 312 | { |
41dceed5 | 313 | return ep->ops->dequeue(ep, req); |
1da177e4 LT |
314 | } |
315 | ||
316 | /** | |
317 | * usb_ep_set_halt - sets the endpoint halt feature. | |
318 | * @ep: the non-isochronous endpoint being stalled | |
319 | * | |
320 | * Use this to stall an endpoint, perhaps as an error report. | |
321 | * Except for control endpoints, | |
322 | * the endpoint stays halted (will not stream any data) until the host | |
323 | * clears this feature; drivers may need to empty the endpoint's request | |
324 | * queue first, to make sure no inappropriate transfers happen. | |
325 | * | |
326 | * Note that while an endpoint CLEAR_FEATURE will be invisible to the | |
327 | * gadget driver, a SET_INTERFACE will not be. To reset endpoints for the | |
328 | * current altsetting, see usb_ep_clear_halt(). When switching altsettings, | |
329 | * it's simplest to use usb_ep_enable() or usb_ep_disable() for the endpoints. | |
330 | * | |
331 | * Returns zero, or a negative error code. On success, this call sets | |
332 | * underlying hardware state that blocks data transfers. | |
333 | * Attempts to halt IN endpoints will fail (returning -EAGAIN) if any | |
334 | * transfer requests are still queued, or if the controller hardware | |
335 | * (usually a FIFO) still holds bytes that the host hasn't collected. | |
336 | */ | |
41dceed5 | 337 | static inline int usb_ep_set_halt(struct usb_ep *ep) |
1da177e4 | 338 | { |
41dceed5 | 339 | return ep->ops->set_halt(ep, 1); |
1da177e4 LT |
340 | } |
341 | ||
342 | /** | |
343 | * usb_ep_clear_halt - clears endpoint halt, and resets toggle | |
344 | * @ep:the bulk or interrupt endpoint being reset | |
345 | * | |
346 | * Use this when responding to the standard usb "set interface" request, | |
347 | * for endpoints that aren't reconfigured, after clearing any other state | |
348 | * in the endpoint's i/o queue. | |
349 | * | |
350 | * Returns zero, or a negative error code. On success, this call clears | |
351 | * the underlying hardware state reflecting endpoint halt and data toggle. | |
352 | * Note that some hardware can't support this request (like pxa2xx_udc), | |
353 | * and accordingly can't correctly implement interface altsettings. | |
354 | */ | |
41dceed5 | 355 | static inline int usb_ep_clear_halt(struct usb_ep *ep) |
1da177e4 | 356 | { |
41dceed5 | 357 | return ep->ops->set_halt(ep, 0); |
1da177e4 LT |
358 | } |
359 | ||
a5e54b0d DL |
360 | /** |
361 | * usb_ep_set_wedge - sets the halt feature and ignores clear requests | |
362 | * @ep: the endpoint being wedged | |
363 | * | |
364 | * Use this to stall an endpoint and ignore CLEAR_FEATURE(HALT_ENDPOINT) | |
365 | * requests. If the gadget driver clears the halt status, it will | |
366 | * automatically unwedge the endpoint. | |
367 | * | |
368 | * Returns zero on success, else negative errno. | |
369 | */ | |
370 | static inline int | |
371 | usb_ep_set_wedge(struct usb_ep *ep) | |
372 | { | |
373 | if (ep->ops->set_wedge) | |
374 | return ep->ops->set_wedge(ep); | |
375 | else | |
376 | return ep->ops->set_halt(ep, 1); | |
377 | } | |
378 | ||
1da177e4 LT |
379 | /** |
380 | * usb_ep_fifo_status - returns number of bytes in fifo, or error | |
381 | * @ep: the endpoint whose fifo status is being checked. | |
382 | * | |
383 | * FIFO endpoints may have "unclaimed data" in them in certain cases, | |
384 | * such as after aborted transfers. Hosts may not have collected all | |
385 | * the IN data written by the gadget driver (and reported by a request | |
386 | * completion). The gadget driver may not have collected all the data | |
387 | * written OUT to it by the host. Drivers that need precise handling for | |
388 | * fault reporting or recovery may need to use this call. | |
389 | * | |
390 | * This returns the number of such bytes in the fifo, or a negative | |
391 | * errno if the endpoint doesn't use a FIFO or doesn't support such | |
392 | * precise handling. | |
393 | */ | |
41dceed5 | 394 | static inline int usb_ep_fifo_status(struct usb_ep *ep) |
1da177e4 LT |
395 | { |
396 | if (ep->ops->fifo_status) | |
41dceed5 | 397 | return ep->ops->fifo_status(ep); |
1da177e4 LT |
398 | else |
399 | return -EOPNOTSUPP; | |
400 | } | |
401 | ||
402 | /** | |
403 | * usb_ep_fifo_flush - flushes contents of a fifo | |
404 | * @ep: the endpoint whose fifo is being flushed. | |
405 | * | |
406 | * This call may be used to flush the "unclaimed data" that may exist in | |
407 | * an endpoint fifo after abnormal transaction terminations. The call | |
408 | * must never be used except when endpoint is not being used for any | |
409 | * protocol translation. | |
410 | */ | |
41dceed5 | 411 | static inline void usb_ep_fifo_flush(struct usb_ep *ep) |
1da177e4 LT |
412 | { |
413 | if (ep->ops->fifo_flush) | |
41dceed5 | 414 | ep->ops->fifo_flush(ep); |
1da177e4 LT |
415 | } |
416 | ||
417 | ||
418 | /*-------------------------------------------------------------------------*/ | |
419 | ||
420 | struct usb_gadget; | |
421 | ||
422 | /* the rest of the api to the controller hardware: device operations, | |
423 | * which don't involve endpoints (or i/o). | |
424 | */ | |
425 | struct usb_gadget_ops { | |
426 | int (*get_frame)(struct usb_gadget *); | |
427 | int (*wakeup)(struct usb_gadget *); | |
428 | int (*set_selfpowered) (struct usb_gadget *, int is_selfpowered); | |
429 | int (*vbus_session) (struct usb_gadget *, int is_active); | |
430 | int (*vbus_draw) (struct usb_gadget *, unsigned mA); | |
431 | int (*pullup) (struct usb_gadget *, int is_on); | |
432 | int (*ioctl)(struct usb_gadget *, | |
433 | unsigned code, unsigned long param); | |
434 | }; | |
435 | ||
436 | /** | |
437 | * struct usb_gadget - represents a usb slave device | |
438 | * @ops: Function pointers used to access hardware-specific operations. | |
439 | * @ep0: Endpoint zero, used when reading or writing responses to | |
efc9052e | 440 | * driver setup() requests |
1da177e4 LT |
441 | * @ep_list: List of other endpoints supported by the device. |
442 | * @speed: Speed of current connection to USB host. | |
443 | * @is_dualspeed: True if the controller supports both high and full speed | |
444 | * operation. If it does, the gadget driver must also support both. | |
445 | * @is_otg: True if the USB device port uses a Mini-AB jack, so that the | |
446 | * gadget driver must provide a USB OTG descriptor. | |
447 | * @is_a_peripheral: False unless is_otg, the "A" end of a USB cable | |
448 | * is in the Mini-AB jack, and HNP has been used to switch roles | |
449 | * so that the "A" device currently acts as A-Peripheral, not A-Host. | |
450 | * @a_hnp_support: OTG device feature flag, indicating that the A-Host | |
451 | * supports HNP at this port. | |
452 | * @a_alt_hnp_support: OTG device feature flag, indicating that the A-Host | |
453 | * only supports HNP on a different root port. | |
454 | * @b_hnp_enable: OTG device feature flag, indicating that the A-Host | |
455 | * enabled HNP support. | |
456 | * @name: Identifies the controller hardware type. Used in diagnostics | |
efc9052e | 457 | * and sometimes configuration. |
1da177e4 LT |
458 | * @dev: Driver model state for this abstract device. |
459 | * | |
460 | * Gadgets have a mostly-portable "gadget driver" implementing device | |
461 | * functions, handling all usb configurations and interfaces. Gadget | |
462 | * drivers talk to hardware-specific code indirectly, through ops vectors. | |
463 | * That insulates the gadget driver from hardware details, and packages | |
464 | * the hardware endpoints through generic i/o queues. The "usb_gadget" | |
465 | * and "usb_ep" interfaces provide that insulation from the hardware. | |
466 | * | |
467 | * Except for the driver data, all fields in this structure are | |
468 | * read-only to the gadget driver. That driver data is part of the | |
469 | * "driver model" infrastructure in 2.6 (and later) kernels, and for | |
470 | * earlier systems is grouped in a similar structure that's not known | |
471 | * to the rest of the kernel. | |
472 | * | |
473 | * Values of the three OTG device feature flags are updated before the | |
474 | * setup() call corresponding to USB_REQ_SET_CONFIGURATION, and before | |
475 | * driver suspend() calls. They are valid only when is_otg, and when the | |
476 | * device is acting as a B-Peripheral (so is_a_peripheral is false). | |
477 | */ | |
478 | struct usb_gadget { | |
479 | /* readonly to gadget driver */ | |
480 | const struct usb_gadget_ops *ops; | |
481 | struct usb_ep *ep0; | |
482 | struct list_head ep_list; /* of usb_ep */ | |
483 | enum usb_device_speed speed; | |
484 | unsigned is_dualspeed:1; | |
485 | unsigned is_otg:1; | |
486 | unsigned is_a_peripheral:1; | |
487 | unsigned b_hnp_enable:1; | |
488 | unsigned a_hnp_support:1; | |
489 | unsigned a_alt_hnp_support:1; | |
490 | const char *name; | |
491 | struct device dev; | |
492 | }; | |
493 | ||
41dceed5 GKH |
494 | static inline void set_gadget_data(struct usb_gadget *gadget, void *data) |
495 | { dev_set_drvdata(&gadget->dev, data); } | |
496 | static inline void *get_gadget_data(struct usb_gadget *gadget) | |
497 | { return dev_get_drvdata(&gadget->dev); } | |
f48cf80f FC |
498 | static inline struct usb_gadget *dev_to_usb_gadget(struct device *dev) |
499 | { | |
500 | return container_of(dev, struct usb_gadget, dev); | |
501 | } | |
1da177e4 LT |
502 | |
503 | /* iterates the non-control endpoints; 'tmp' is a struct usb_ep pointer */ | |
0858a3a5 | 504 | #define gadget_for_each_ep(tmp, gadget) \ |
1da177e4 LT |
505 | list_for_each_entry(tmp, &(gadget)->ep_list, ep_list) |
506 | ||
507 | ||
a4e3ef55 DB |
508 | /** |
509 | * gadget_is_dualspeed - return true iff the hardware handles high speed | |
fd39c86b | 510 | * @g: controller that might support both high and full speeds |
a4e3ef55 DB |
511 | */ |
512 | static inline int gadget_is_dualspeed(struct usb_gadget *g) | |
513 | { | |
514 | #ifdef CONFIG_USB_GADGET_DUALSPEED | |
515 | /* runtime test would check "g->is_dualspeed" ... that might be | |
516 | * useful to work around hardware bugs, but is mostly pointless | |
517 | */ | |
518 | return 1; | |
519 | #else | |
520 | return 0; | |
521 | #endif | |
522 | } | |
523 | ||
524 | /** | |
525 | * gadget_is_otg - return true iff the hardware is OTG-ready | |
fd39c86b | 526 | * @g: controller that might have a Mini-AB connector |
a4e3ef55 DB |
527 | * |
528 | * This is a runtime test, since kernels with a USB-OTG stack sometimes | |
529 | * run on boards which only have a Mini-B (or Mini-A) connector. | |
530 | */ | |
531 | static inline int gadget_is_otg(struct usb_gadget *g) | |
532 | { | |
533 | #ifdef CONFIG_USB_OTG | |
534 | return g->is_otg; | |
535 | #else | |
536 | return 0; | |
537 | #endif | |
538 | } | |
539 | ||
1da177e4 LT |
540 | /** |
541 | * usb_gadget_frame_number - returns the current frame number | |
542 | * @gadget: controller that reports the frame number | |
543 | * | |
544 | * Returns the usb frame number, normally eleven bits from a SOF packet, | |
545 | * or negative errno if this device doesn't support this capability. | |
546 | */ | |
41dceed5 | 547 | static inline int usb_gadget_frame_number(struct usb_gadget *gadget) |
1da177e4 | 548 | { |
41dceed5 | 549 | return gadget->ops->get_frame(gadget); |
1da177e4 LT |
550 | } |
551 | ||
552 | /** | |
553 | * usb_gadget_wakeup - tries to wake up the host connected to this gadget | |
554 | * @gadget: controller used to wake up the host | |
555 | * | |
556 | * Returns zero on success, else negative error code if the hardware | |
557 | * doesn't support such attempts, or its support has not been enabled | |
558 | * by the usb host. Drivers must return device descriptors that report | |
559 | * their ability to support this, or hosts won't enable it. | |
560 | * | |
561 | * This may also try to use SRP to wake the host and start enumeration, | |
562 | * even if OTG isn't otherwise in use. OTG devices may also start | |
563 | * remote wakeup even when hosts don't explicitly enable it. | |
564 | */ | |
41dceed5 | 565 | static inline int usb_gadget_wakeup(struct usb_gadget *gadget) |
1da177e4 LT |
566 | { |
567 | if (!gadget->ops->wakeup) | |
568 | return -EOPNOTSUPP; | |
41dceed5 | 569 | return gadget->ops->wakeup(gadget); |
1da177e4 LT |
570 | } |
571 | ||
572 | /** | |
573 | * usb_gadget_set_selfpowered - sets the device selfpowered feature. | |
574 | * @gadget:the device being declared as self-powered | |
575 | * | |
576 | * this affects the device status reported by the hardware driver | |
577 | * to reflect that it now has a local power supply. | |
578 | * | |
579 | * returns zero on success, else negative errno. | |
580 | */ | |
41dceed5 | 581 | static inline int usb_gadget_set_selfpowered(struct usb_gadget *gadget) |
1da177e4 LT |
582 | { |
583 | if (!gadget->ops->set_selfpowered) | |
584 | return -EOPNOTSUPP; | |
41dceed5 | 585 | return gadget->ops->set_selfpowered(gadget, 1); |
1da177e4 LT |
586 | } |
587 | ||
588 | /** | |
589 | * usb_gadget_clear_selfpowered - clear the device selfpowered feature. | |
590 | * @gadget:the device being declared as bus-powered | |
591 | * | |
592 | * this affects the device status reported by the hardware driver. | |
593 | * some hardware may not support bus-powered operation, in which | |
594 | * case this feature's value can never change. | |
595 | * | |
596 | * returns zero on success, else negative errno. | |
597 | */ | |
41dceed5 | 598 | static inline int usb_gadget_clear_selfpowered(struct usb_gadget *gadget) |
1da177e4 LT |
599 | { |
600 | if (!gadget->ops->set_selfpowered) | |
601 | return -EOPNOTSUPP; | |
41dceed5 | 602 | return gadget->ops->set_selfpowered(gadget, 0); |
1da177e4 LT |
603 | } |
604 | ||
605 | /** | |
606 | * usb_gadget_vbus_connect - Notify controller that VBUS is powered | |
607 | * @gadget:The device which now has VBUS power. | |
c2344f13 | 608 | * Context: can sleep |
1da177e4 LT |
609 | * |
610 | * This call is used by a driver for an external transceiver (or GPIO) | |
611 | * that detects a VBUS power session starting. Common responses include | |
612 | * resuming the controller, activating the D+ (or D-) pullup to let the | |
613 | * host detect that a USB device is attached, and starting to draw power | |
614 | * (8mA or possibly more, especially after SET_CONFIGURATION). | |
615 | * | |
616 | * Returns zero on success, else negative errno. | |
617 | */ | |
41dceed5 | 618 | static inline int usb_gadget_vbus_connect(struct usb_gadget *gadget) |
1da177e4 LT |
619 | { |
620 | if (!gadget->ops->vbus_session) | |
621 | return -EOPNOTSUPP; | |
41dceed5 | 622 | return gadget->ops->vbus_session(gadget, 1); |
1da177e4 LT |
623 | } |
624 | ||
625 | /** | |
626 | * usb_gadget_vbus_draw - constrain controller's VBUS power usage | |
627 | * @gadget:The device whose VBUS usage is being described | |
628 | * @mA:How much current to draw, in milliAmperes. This should be twice | |
629 | * the value listed in the configuration descriptor bMaxPower field. | |
630 | * | |
631 | * This call is used by gadget drivers during SET_CONFIGURATION calls, | |
632 | * reporting how much power the device may consume. For example, this | |
633 | * could affect how quickly batteries are recharged. | |
634 | * | |
635 | * Returns zero on success, else negative errno. | |
636 | */ | |
41dceed5 | 637 | static inline int usb_gadget_vbus_draw(struct usb_gadget *gadget, unsigned mA) |
1da177e4 LT |
638 | { |
639 | if (!gadget->ops->vbus_draw) | |
640 | return -EOPNOTSUPP; | |
41dceed5 | 641 | return gadget->ops->vbus_draw(gadget, mA); |
1da177e4 LT |
642 | } |
643 | ||
644 | /** | |
645 | * usb_gadget_vbus_disconnect - notify controller about VBUS session end | |
646 | * @gadget:the device whose VBUS supply is being described | |
c2344f13 | 647 | * Context: can sleep |
1da177e4 LT |
648 | * |
649 | * This call is used by a driver for an external transceiver (or GPIO) | |
650 | * that detects a VBUS power session ending. Common responses include | |
651 | * reversing everything done in usb_gadget_vbus_connect(). | |
652 | * | |
653 | * Returns zero on success, else negative errno. | |
654 | */ | |
41dceed5 | 655 | static inline int usb_gadget_vbus_disconnect(struct usb_gadget *gadget) |
1da177e4 LT |
656 | { |
657 | if (!gadget->ops->vbus_session) | |
658 | return -EOPNOTSUPP; | |
41dceed5 | 659 | return gadget->ops->vbus_session(gadget, 0); |
1da177e4 LT |
660 | } |
661 | ||
662 | /** | |
663 | * usb_gadget_connect - software-controlled connect to USB host | |
664 | * @gadget:the peripheral being connected | |
665 | * | |
666 | * Enables the D+ (or potentially D-) pullup. The host will start | |
667 | * enumerating this gadget when the pullup is active and a VBUS session | |
668 | * is active (the link is powered). This pullup is always enabled unless | |
669 | * usb_gadget_disconnect() has been used to disable it. | |
670 | * | |
671 | * Returns zero on success, else negative errno. | |
672 | */ | |
41dceed5 | 673 | static inline int usb_gadget_connect(struct usb_gadget *gadget) |
1da177e4 LT |
674 | { |
675 | if (!gadget->ops->pullup) | |
676 | return -EOPNOTSUPP; | |
41dceed5 | 677 | return gadget->ops->pullup(gadget, 1); |
1da177e4 LT |
678 | } |
679 | ||
680 | /** | |
681 | * usb_gadget_disconnect - software-controlled disconnect from USB host | |
682 | * @gadget:the peripheral being disconnected | |
683 | * | |
684 | * Disables the D+ (or potentially D-) pullup, which the host may see | |
685 | * as a disconnect (when a VBUS session is active). Not all systems | |
686 | * support software pullup controls. | |
687 | * | |
688 | * This routine may be used during the gadget driver bind() call to prevent | |
689 | * the peripheral from ever being visible to the USB host, unless later | |
690 | * usb_gadget_connect() is called. For example, user mode components may | |
691 | * need to be activated before the system can talk to hosts. | |
692 | * | |
693 | * Returns zero on success, else negative errno. | |
694 | */ | |
41dceed5 | 695 | static inline int usb_gadget_disconnect(struct usb_gadget *gadget) |
1da177e4 LT |
696 | { |
697 | if (!gadget->ops->pullup) | |
698 | return -EOPNOTSUPP; | |
41dceed5 | 699 | return gadget->ops->pullup(gadget, 0); |
1da177e4 LT |
700 | } |
701 | ||
702 | ||
1da177e4 LT |
703 | /*-------------------------------------------------------------------------*/ |
704 | ||
705 | /** | |
706 | * struct usb_gadget_driver - driver for usb 'slave' devices | |
707 | * @function: String describing the gadget's function | |
708 | * @speed: Highest speed the driver handles. | |
1da177e4 | 709 | * @setup: Invoked for ep0 control requests that aren't handled by |
efc9052e DB |
710 | * the hardware level driver. Most calls must be handled by |
711 | * the gadget driver, including descriptor and configuration | |
712 | * management. The 16 bit members of the setup data are in | |
713 | * USB byte order. Called in_interrupt; this may not sleep. Driver | |
1da177e4 LT |
714 | * queues a response to ep0, or returns negative to stall. |
715 | * @disconnect: Invoked after all transfers have been stopped, | |
efc9052e DB |
716 | * when the host is disconnected. May be called in_interrupt; this |
717 | * may not sleep. Some devices can't detect disconnect, so this might | |
1da177e4 LT |
718 | * not be called except as part of controller shutdown. |
719 | * @unbind: Invoked when the driver is unbound from a gadget, | |
efc9052e DB |
720 | * usually from rmmod (after a disconnect is reported). |
721 | * Called in a context that permits sleeping. | |
1da177e4 LT |
722 | * @suspend: Invoked on USB suspend. May be called in_interrupt. |
723 | * @resume: Invoked on USB resume. May be called in_interrupt. | |
724 | * @driver: Driver model state for this driver. | |
725 | * | |
726 | * Devices are disabled till a gadget driver successfully bind()s, which | |
727 | * means the driver will handle setup() requests needed to enumerate (and | |
728 | * meet "chapter 9" requirements) then do some useful work. | |
729 | * | |
730 | * If gadget->is_otg is true, the gadget driver must provide an OTG | |
731 | * descriptor during enumeration, or else fail the bind() call. In such | |
732 | * cases, no USB traffic may flow until both bind() returns without | |
733 | * having called usb_gadget_disconnect(), and the USB host stack has | |
734 | * initialized. | |
735 | * | |
736 | * Drivers use hardware-specific knowledge to configure the usb hardware. | |
737 | * endpoint addressing is only one of several hardware characteristics that | |
738 | * are in descriptors the ep0 implementation returns from setup() calls. | |
739 | * | |
740 | * Except for ep0 implementation, most driver code shouldn't need change to | |
741 | * run on top of different usb controllers. It'll use endpoints set up by | |
742 | * that ep0 implementation. | |
743 | * | |
744 | * The usb controller driver handles a few standard usb requests. Those | |
745 | * include set_address, and feature flags for devices, interfaces, and | |
746 | * endpoints (the get_status, set_feature, and clear_feature requests). | |
747 | * | |
748 | * Accordingly, the driver's setup() callback must always implement all | |
749 | * get_descriptor requests, returning at least a device descriptor and | |
750 | * a configuration descriptor. Drivers must make sure the endpoint | |
751 | * descriptors match any hardware constraints. Some hardware also constrains | |
752 | * other descriptors. (The pxa250 allows only configurations 1, 2, or 3). | |
753 | * | |
754 | * The driver's setup() callback must also implement set_configuration, | |
755 | * and should also implement set_interface, get_configuration, and | |
756 | * get_interface. Setting a configuration (or interface) is where | |
757 | * endpoints should be activated or (config 0) shut down. | |
758 | * | |
759 | * (Note that only the default control endpoint is supported. Neither | |
760 | * hosts nor devices generally support control traffic except to ep0.) | |
761 | * | |
762 | * Most devices will ignore USB suspend/resume operations, and so will | |
763 | * not provide those callbacks. However, some may need to change modes | |
764 | * when the host is not longer directing those activities. For example, | |
765 | * local controls (buttons, dials, etc) may need to be re-enabled since | |
766 | * the (remote) host can't do that any longer; or an error state might | |
767 | * be cleared, to make the device behave identically whether or not | |
768 | * power is maintained. | |
769 | */ | |
770 | struct usb_gadget_driver { | |
771 | char *function; | |
772 | enum usb_device_speed speed; | |
1da177e4 LT |
773 | void (*unbind)(struct usb_gadget *); |
774 | int (*setup)(struct usb_gadget *, | |
775 | const struct usb_ctrlrequest *); | |
776 | void (*disconnect)(struct usb_gadget *); | |
777 | void (*suspend)(struct usb_gadget *); | |
778 | void (*resume)(struct usb_gadget *); | |
779 | ||
41dceed5 | 780 | /* FIXME support safe rmmod */ |
1da177e4 LT |
781 | struct device_driver driver; |
782 | }; | |
783 | ||
784 | ||
785 | ||
786 | /*-------------------------------------------------------------------------*/ | |
787 | ||
788 | /* driver modules register and unregister, as usual. | |
789 | * these calls must be made in a context that can sleep. | |
790 | * | |
791 | * these will usually be implemented directly by the hardware-dependent | |
792 | * usb bus interface driver, which will only support a single driver. | |
793 | */ | |
794 | ||
795 | /** | |
b0fca50f UKK |
796 | * usb_gadget_probe_driver - probe a gadget driver |
797 | * @driver: the driver being registered | |
798 | * @bind: the driver's bind callback | |
c2344f13 | 799 | * Context: can sleep |
1da177e4 LT |
800 | * |
801 | * Call this in your gadget driver's module initialization function, | |
802 | * to tell the underlying usb controller driver about your driver. | |
b0fca50f UKK |
803 | * The @bind() function will be called to bind it to a gadget before this |
804 | * registration call returns. It's expected that the @bind() function will | |
805 | * be in init sections. | |
1da177e4 | 806 | */ |
b0fca50f UKK |
807 | int usb_gadget_probe_driver(struct usb_gadget_driver *driver, |
808 | int (*bind)(struct usb_gadget *)); | |
1da177e4 LT |
809 | |
810 | /** | |
811 | * usb_gadget_unregister_driver - unregister a gadget driver | |
812 | * @driver:the driver being unregistered | |
c2344f13 | 813 | * Context: can sleep |
1da177e4 LT |
814 | * |
815 | * Call this in your gadget driver's module cleanup function, | |
816 | * to tell the underlying usb controller that your driver is | |
817 | * going away. If the controller is connected to a USB host, | |
818 | * it will first disconnect(). The driver is also requested | |
819 | * to unbind() and clean up any device state, before this procedure | |
329af28b DB |
820 | * finally returns. It's expected that the unbind() functions |
821 | * will in in exit sections, so may not be linked in some kernels. | |
1da177e4 | 822 | */ |
41dceed5 | 823 | int usb_gadget_unregister_driver(struct usb_gadget_driver *driver); |
1da177e4 LT |
824 | |
825 | /*-------------------------------------------------------------------------*/ | |
826 | ||
827 | /* utility to simplify dealing with string descriptors */ | |
828 | ||
829 | /** | |
830 | * struct usb_string - wraps a C string and its USB id | |
831 | * @id:the (nonzero) ID for this string | |
832 | * @s:the string, in UTF-8 encoding | |
833 | * | |
834 | * If you're using usb_gadget_get_string(), use this to wrap a string | |
835 | * together with its ID. | |
836 | */ | |
837 | struct usb_string { | |
838 | u8 id; | |
839 | const char *s; | |
840 | }; | |
841 | ||
842 | /** | |
843 | * struct usb_gadget_strings - a set of USB strings in a given language | |
844 | * @language:identifies the strings' language (0x0409 for en-us) | |
845 | * @strings:array of strings with their ids | |
846 | * | |
847 | * If you're using usb_gadget_get_string(), use this to wrap all the | |
848 | * strings for a given language. | |
849 | */ | |
850 | struct usb_gadget_strings { | |
851 | u16 language; /* 0x0409 for en-us */ | |
852 | struct usb_string *strings; | |
853 | }; | |
854 | ||
855 | /* put descriptor for string with that id into buf (buflen >= 256) */ | |
41dceed5 | 856 | int usb_gadget_get_string(struct usb_gadget_strings *table, int id, u8 *buf); |
1da177e4 LT |
857 | |
858 | /*-------------------------------------------------------------------------*/ | |
859 | ||
860 | /* utility to simplify managing config descriptors */ | |
861 | ||
862 | /* write vector of descriptors into buffer */ | |
863 | int usb_descriptor_fillbuf(void *, unsigned, | |
864 | const struct usb_descriptor_header **); | |
865 | ||
866 | /* build config descriptor from single descriptor vector */ | |
867 | int usb_gadget_config_buf(const struct usb_config_descriptor *config, | |
868 | void *buf, unsigned buflen, const struct usb_descriptor_header **desc); | |
869 | ||
a4c39c41 DB |
870 | /* copy a NULL-terminated vector of descriptors */ |
871 | struct usb_descriptor_header **usb_copy_descriptors( | |
872 | struct usb_descriptor_header **); | |
873 | ||
874 | /* return copy of endpoint descriptor given original descriptor set */ | |
875 | struct usb_endpoint_descriptor *usb_find_endpoint( | |
876 | struct usb_descriptor_header **src, | |
877 | struct usb_descriptor_header **copy, | |
878 | struct usb_endpoint_descriptor *match); | |
879 | ||
880 | /** | |
881 | * usb_free_descriptors - free descriptors returned by usb_copy_descriptors() | |
882 | * @v: vector of descriptors | |
883 | */ | |
884 | static inline void usb_free_descriptors(struct usb_descriptor_header **v) | |
885 | { | |
886 | kfree(v); | |
887 | } | |
888 | ||
1da177e4 LT |
889 | /*-------------------------------------------------------------------------*/ |
890 | ||
891 | /* utility wrapping a simple endpoint selection policy */ | |
892 | ||
41dceed5 | 893 | extern struct usb_ep *usb_ep_autoconfig(struct usb_gadget *, |
3ab810f1 | 894 | struct usb_endpoint_descriptor *); |
1da177e4 | 895 | |
3ab810f1 | 896 | extern void usb_ep_autoconfig_reset(struct usb_gadget *); |
1da177e4 | 897 | |
dda43a0e | 898 | #endif /* __LINUX_USB_GADGET_H */ |