30      update information about a device in the controller after a device has
  31      been determined to be a hub during enumeration.  If a host controller
  32      does not need to take any specific action after enumerating a hub, then
  33      it should simply set this entry point in the usba_hcdi_ops(9S) structure
  34      to NULL.
  35 
  36      The nports and tt members provide relevant information from the device's
  37      hub class descriptor which can be used to help program the host
  38      controller.  Any programming should be performed synchronously and be
  39      completed before this function returns.
  40 
  41      This function will be called after usba_hcdi_device_init(9E) has been
  42      called.  Any private data registered with that function will be
  43      available.
  44 
  45      If this function fails, the enumeration of this device will fail, the hub
  46      driver will not attach to this USB device, and all devices plugged into
  47      this hub will not be detected by the system.
  48 
  49 CONTEXT
  50      This functin is called from kernel context only.
  51 
  52 RETURN VALUES
  53      Upon successful completion, the usba_hcdi_hub_update() function should
  54      return USB_SUCCESS.  Otherwise, it should return the appropriate USB
  55      error.  If uncertain, use USB_FAILURE.
  56 
  57 SEE ALSO
  58      usba_hcdi_device_init(9E), usba_device(9S), usba_hcdi_ops(9S)
  59 
  60 illumos                        December 20, 2016                       illumos

  30      update information about a device in the controller after a device has
  31      been determined to be a hub during enumeration.  If a host controller
  32      does not need to take any specific action after enumerating a hub, then
  33      it should simply set this entry point in the usba_hcdi_ops(9S) structure
  34      to NULL.
  35 
  36      The nports and tt members provide relevant information from the device's
  37      hub class descriptor which can be used to help program the host
  38      controller.  Any programming should be performed synchronously and be
  39      completed before this function returns.
  40 
  41      This function will be called after usba_hcdi_device_init(9E) has been
  42      called.  Any private data registered with that function will be
  43      available.
  44 
  45      If this function fails, the enumeration of this device will fail, the hub
  46      driver will not attach to this USB device, and all devices plugged into
  47      this hub will not be detected by the system.
  48 
  49 CONTEXT
  50      This function is called from kernel context only.
  51 
  52 RETURN VALUES
  53      Upon successful completion, the usba_hcdi_hub_update() function should
  54      return USB_SUCCESS.  Otherwise, it should return the appropriate USB
  55      error.  If uncertain, use USB_FAILURE.
  56 
  57 SEE ALSO
  58      usba_hcdi_device_init(9E), usba_device(9S), usba_hcdi_ops(9S)
  59 
  60 illumos                        February 15, 2020                       illumos