aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorStephen Warren2014-05-19 14:21:18 -0600
committerMarek Vasut2014-06-01 19:20:07 +0200
commit77b83e6d099cb2149e5b2c33a700003227d99297 (patch)
tree70b71935bbd5913695262cd06bd8ca6789d3f79d /README
parent0d437bcaf9be36d7bb954cb261635678c790dff7 (diff)
usb: hub: remove CONFIG_USB_HUB_MIN_POWER_ON_DELAY
Now that we wait the correct specification-mandated time at the end of usb_hub_power_on(), I suspect that CONFIG_USB_HUB_MIN_POWER_ON_DELAY has no purpose. For cm_t35.h, we already wait longer than the original MIN_POWER_ON_DELAY, so this change is safe. For gw_ventana.h, we will wait as long as the original MIN_POWER_ON_DELAY iff pgood_delay was at least 200ms. I'm not sure if this is the case or not, hence I've CC'd relevant people to test this change. Cc: Igor Grinberg <grinberg@compulab.co.il> Cc: Tim Harvey <tharvey@gateworks.com> Signed-off-by: Stephen Warren <swarren@nvidia.com>
Diffstat (limited to 'README')
-rw-r--r--README3
1 files changed, 0 insertions, 3 deletions
diff --git a/README b/README
index a280435e9fb..a085625841c 100644
--- a/README
+++ b/README
@@ -1432,9 +1432,6 @@ The following options need to be configured:
CONFIG_USB_EHCI_TXFIFO_THRESH enables setting of the
txfilltuning field in the EHCI controller on reset.
- CONFIG_USB_HUB_MIN_POWER_ON_DELAY defines the minimum
- interval for usb hub power-on delay.(minimum 100msec)
-
- USB Device:
Define the below if you wish to use the USB console.
Once firmware is rebuilt from a serial console issue the