| blob | c9460ed063c9ca5ed368f6c81ee71e50b8e51642 |
1 '\" te
2 .\" Copyright (c) 2006, Sun Microsystems, Inc. All Rights Reserved
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH HUBD 7D "May 13, 2017"
7 .SH NAME
8 hubd \- USB hub driver
9 .SH SYNOPSIS
10 .LP
11 .nf
12 \fBhub@unit-address\fR
13 .fi
15 .SH DESCRIPTION
16 .LP
17 The \fBhubd\fR is a USBA (illumos USB Architecture) compliant client driver
18 that supports USB hubs conforming to the \fIUniversal Serial Bus Specification
19 3.0\fR. The \fBhubd\fR driver supports bus-powered and self-powered hubs. The
20 driver supports hubs with individual port power, ganged power and no power
21 switching.
22 .sp
23 .LP
24 When a device is attached to a hub port, the \fBhubd\fR driver enumerates the
25 device by determining its type and assigning an address to it. For
26 multi-configuration devices, \fBhubd\fR sets the preferred configuration (refer
27 to \fBcfgadm_usb\fR(8) to select a configuration). The \fBhubd\fR driver
28 attaches a driver to the device if one is available for the default or selected
29 configuration. When the device is disconnected from the hub port, the
30 \fBhubd\fR driver offlines any driver instance attached to the device.
31 .SH FILES
32 .ne 2
33 .na
34 \fB\fB/kernel/drv/hubd\fR\fR
35 .ad
36 .RS 28n
37 32- bit x86 ELF kernel module
38 .RE
40 .sp
41 .ne 2
42 .na
43 \fB\fB/kernel/drv/amd64/hubd\fR\fR
44 .ad
45 .RS 28n
46 64- bit x86 ELF kernel module
47 .RE
49 .sp
50 .ne 2
51 .na
52 \fB\fB/kernel/drv/sparcv9/hubd\fR\fR
53 .ad
54 .RS 28n
55 64-bit SPARC ELF kernel module
56 .RE
58 .SH ATTRIBUTES
59 .LP
60 See \fBattributes\fR(5) for a description of the following attributes:
61 .sp
63 .sp
64 .TS
65 box;
66 c | c
67 l | l .
68 ATTRIBUTE TYPE ATTRIBUTE VALUE
69 _
70 Architecture SPARC, x86, PCI-based systems
71 .TE
73 .SH SEE ALSO
74 .LP
75 \fBcfgadm_usb\fR(8), \fBattributes\fR(5), \fBusba\fR(7D)
76 .sp
77 .LP
78 \fIWriting Device Drivers\fR
79 .sp
80 .LP
81 \fIUniversal Serial Bus Specification 2.0\fR
82 .sp
83 .LP
84 \fISystem Administration Guide: Basic Administration\fR
85 .SH DIAGNOSTICS
86 .LP
87 In addition to being logged, the following messages may also appear on the
88 system console. Messages are formatted in the following manner:
89 .sp
90 .in +2
91 .nf
92 WARNING: <device path> <hubd<instance number>): Message...
93 .fi
94 .in -2
95 .sp
97 .sp
98 .LP
99 where \fB<instance number>\fR is the instance number of \fBhubd\fR and
100 \fB<device path>\fR is the physical path to the device in \fB/devices\fR
101 directory. Messages from the root hub are displayed with a \fBusb<instance
102 number>\fR prefix instead of \fBhub<instance number>\fR as the root hub is an
103 integrated part of the host controller.
104 .sp
105 .ne 2
106 .na
107 \fBConnecting device on port \fI<number>\fR failed.\fR
108 .ad
109 .sp .6
110 .RS 4n
111 The driver failed to enumerate the device connected on port \fI<number>\fR of
112 hub. If enumeration fails, disconnect and re-connect.
113 .RE
115 .sp
116 .ne 2
117 .na
118 \fBUse of a USB 1.0 hub behind a high speed port may cause unexpected
119 failures.\fR
120 .ad
121 .sp .6
122 .RS 4n
123 Devices connected to a USB 1.0 hub which are in turn connected to an external
124 USB 2.0 hub, may misbehave unexpectedly or suddenly go offline. This is due to
125 a documented incompatibility between USB 1.0 hubs and USB 2.0 hub Transaction
126 Translators. Please use only USB 2.0 or USB 1.1 hubs behind high-speed ports.
127 .RE
129 .sp
130 .ne 2
131 .na
132 \fBConnecting a high speed device to a non-high speed hub (port x) will result
133 in a loss of performance. Please connect the device to a high speed port to get
134 the maximum performance.\fR
135 .ad
136 .sp .6
137 .RS 4n
138 USB 2.0 devices connected to USB 1.0 or 1.1 hubs cannot run at their highest
139 speed, even when the hub is in turn connected to a high-speed port. For best
140 performance, reconnect without going through a USB 1.0 or 1.1 hub.
141 .RE
143 .sp
144 .ne 2
145 .na
146 \fBCannot access <device>. Please reconnect.\fR
147 .ad
148 .sp .6
149 .RS 4n
150 This hub has been disconnected because a device other than the original one has
151 been inserted. The driver informs you of this fact by displaying the name of
152 the original device.
153 .RE
155 .sp
156 .ne 2
157 .na
158 \fBPort <n> overcurrent. \fR
159 .ad
160 .sp .6
161 .RS 4n
162 An overcurrent condition was detected. Please remove the device on this port.
163 .RE
165 .sp
166 .ne 2
167 .na
168 \fBDevices not identical to the previous one on this port. Please disconnect
169 and reconnect.\fR
170 .ad
171 .sp .6
172 .RS 4n
173 Same condition as described above; however in this case, the driver is unable
174 to identify the original device with a name string.
175 .RE
177 .sp
178 .ne 2
179 .na
180 \fBHub driver supports max of \fI<n>\fR ports on hub. Hence, using the first
181 \fI<number of physical ports>\fR of \fI<n>\fR ports available.\fR
182 .ad
183 .sp .6
184 .RS 4n
185 The current hub driver supports hubs that have \fI<n>\fR ports or less. A hub
186 with more than \fI<n>\fR ports has been plugged in. Only the first \fI<n>\fR
187 out of the total \fI<number of physical ports>\fR ports are usable.
188 .RE
190 .sp
191 .ne 2
192 .na
193 \fBHub global over current condition, please disconnect the devices connected
194 to the hub to clear the condition. You may need to re-connect the hub if the
195 ports do not work.\fR
196 .ad
197 .sp .6
198 .RS 4n
199 An overcurrent condition was detected on the hub. This means that the
200 aggregate current being drawn by the devices on the downstream ports exceeds a
201 preset value. Refer to section 7.2.1.2 and 11.13 of the \fIUniversal Serial Bus
202 Specification 2.0\fR. If this message continues to display, you may need to
203 remove downstream devices to eliminate the problem. If any port does not work
204 after the overcurrent condition is cleared, re-connect the hub to re-enable the
205 ports.
206 .RE
208 .sp
209 .ne 2
210 .na
211 \fBRoot hub over current condition, please check your system to clear the
212 condition as soon as possible. You may need to reboot the system if the root
213 hub does not recover automatically.\fR
214 .ad
215 .sp .6
216 .RS 4n
217 An overcurrent condition was detected on the root hub, indicating that
218 malfunctioning devices on the downstream ports are drawing too much current.
219 Please disconnect the problematic downstream devices to eliminate the problem.
220 If the root hub doesn't work after the overcurrent condition is cleared, you
221 may need to reboot the system.
222 .RE
224 .sp
225 .LP
226 The following messages may be logged into the system log. They are formatted in
227 the following manner:
228 .sp
229 .in +2
230 .nf
231 <device path><hubd<instance number>): message...
232 .fi
233 .in -2
234 .sp
236 .sp
237 .ne 2
238 .na
239 \fBLocal power has been lost, please disconnect hub.\fR
240 .ad
241 .sp .6
242 .RS 4n
243 A USB self-powered hub has lost external power. All USB devices connected
244 down-stream from this hub will cease to function. Disconnect the hub, plug in
245 the external power-supply and then plug in the hub again.
246 .RE
248 .sp
249 .ne 2
250 .na
251 \fBLocal power has been lost, the hub could draw <x> mA power from the USB
252 bus.\fR
253 .ad
254 .sp .6
255 .RS 4n
256 A USB self/bus-powered hub has lost external power. Some USB devices connected
257 down-stream from this hub may cease to function. Disconnect the
258 external power-supply and then plug in the hub again.
259 .RE
261 .sp
262 .ne 2
263 .na
264 \fBTwo bus-powered hubs cannot be concatenated.\fR
265 .ad
266 .sp .6
267 .RS 4n
268 A bus-powered hub was connected to a bus powered hub port. Please remove this
269 bus-powered hub and connect it to a self-powered hub or a root hub port.
270 .RE
272 .sp
273 .ne 2
274 .na
275 \fBConfiguration <n> for device <device> at port <m> exceeds power available
276 for this port. Please re-insert your device into another hub port which has
277 enough power.\fR
278 .ad
279 .sp .6
280 .RS 4n
281 The device requires more power than is available on this port.
282 .RE
284 .sp
285 .ne 2
286 .na
287 \fBPort <\fIn\fR\fB> in over current condition, please check the attached device
288 to clear the condition. The system will try to recover the port, but if not
289 successful, you need to re-connect the hub or reboot the system to bring the
290 port back to work.\fR
291 .ad
292 .sp .6
293 .RS 4n
294 An overcurrent condition was detected on port <\fIn\fR>. This means the device
295 connected to the port is drawing more current than the hub can supply. If this
296 message continues to display, please disconnect the device to eliminate the
297 problem. If the port doesn't work after the overcurrent condition is cleared,
298 please re-connect the hub or reboot the system to enable the port again.
299 .RE
301 .sp
302 .ne 2
303 .na
304 \fBUnable to attach USB 3.x hub <vendor> <device>. A maximum of 5 hubs
305 may be cascaded.\fR
306 .ad
307 .sp .6
308 .RS 4n
309 USB 3.0 has an upper bound on the number of hubs that may be chained
310 together. If this limit is exceeded, a hub may not be detected or
311 attached. The hub will be functional if plugged into a different part of
312 the USB topology. To determine the depth of the hub, count the number of
313 devices between it and the host controller.
314 .RE