2 .\" This file and its contents are supplied under the terms of the
3 .\" Common Development and Distribution License ("CDDL"), version 1.0.
4 .\" You may only use this file in accordance with the terms of version
7 .\" A full copy of the text of the CDDL should have accompanied this
8 .\" source. A copy of the CDDL is also available via the Internet at
9 .\" http://www.illumos.org/license/CDDL.
12 .\" Copyright 2016 Joyent, Inc.
15 .Dt USBA_HCDI_DEVICE_INIT 9E
18 .Nm usba_hcdi_device_init ,
19 .Nm usba_hcdi_device_fini
20 .Nd USB device initialization and finalization
22 .In sys/usb/usba/hcdi.h
24 .Fo prefix_hcdi_device_init
25 .Fa "usba_device_t *usb_device"
27 .Fa "void **hcd_privatep"
30 .Fo prefix_hcdi_device_fini
31 .Fa "usba_device_t *usb_device"
33 .Fa "void *hcd_private"
37 illumos USB HCD private function
39 This is a private function that is not part of the stable DDI.
40 It may be removed or changed at any time.
44 Pointer to a USB device structure.
46 The port number the device was detected on.
48 Pointer to storage space for a HCD driver to store private data for the
51 Pointer to the HCD driver's private data for the device.
55 .Fn usba_hcdi_device_init
56 entry point is an optional entry point.
57 It will be called when child devices of the root hub are being initialized.
58 A call to this entry point will occur before any calls to open a pipe to the
59 child device through the
60 .Xr usba_hcdi_pipe_open 9E
63 During this time, the HCD driver should do any required initialization
64 required by the host controller.
65 The HCD may also opt to store private data for this device as a result of
66 whatever initialization it performed.
67 The data should be stored in the
70 Data stored this will be accessible to the HCD driver through the
71 .Xr usba_hcdi_get_device_private 9F
75 .Fn usba_hcdi_device_fini
76 entry point is an optional entry point.
77 It will be called when child devices of the root hub are being removed.
78 The HCD should perform any necessary work with the root controller to finish
79 tearing down the device.
80 In addition, if the HCD stored private data it will a pointer to it in the
83 The HCD driver must release any resources associated with its private data.
84 If it does not, the resources will be leaked.
87 .Fn usba_hcdi_device_fini
88 is called, all associated pipes should have been closed through the
89 .Xr usba_hcdi_pipe_close 9E
92 The HCD driver is guaranteed that no other entry points will be invoked
95 while a call to either function is ongoing.
96 However, the entry point may be called in parallel on behalf of separate
99 This function is called from kernel context only.
101 Upon successful completion, the
102 .Fn usba_hcdi_device_init
103 function should return
105 Otherwise, it should return the appropriate error.
108 .Xr usba_hcdi_pipe_close 9E ,
109 .Xr usba_hcdi_pipe_open 9E