wimax/i2400m: Update comments to talk about SDIO reset and not USB.

Fixing comments from original cut and paste error

Signed-off-by: Dirk Brandewie <dirk.j.brandewie@intel.com>
Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
This commit is contained in:
Dirk Brandewie 2009-07-24 09:04:33 -07:00 committed by Inaky Perez-Gonzalez
parent abb3073383
commit 81b182a754

View file

@ -233,18 +233,17 @@ error_kzalloc:
* Warm reset: * Warm reset:
* *
* The device will be fully reset internally, but won't be * The device will be fully reset internally, but won't be
* disconnected from the USB bus (so no reenumeration will * disconnected from the bus (so no reenumeration will
* happen). Firmware upload will be neccessary. * happen). Firmware upload will be neccessary.
* *
* The device will send a reboot barker in the notification endpoint * The device will send a reboot barker that will trigger the driver
* that will trigger the driver to reinitialize the state * to reinitialize the state via __i2400m_dev_reset_handle.
* automatically from notif.c:i2400m_notification_grok() into
* i2400m_dev_bootstrap_delayed().
* *
* Cold and bus (USB) reset: *
* Cold and bus reset:
* *
* The device will be fully reset internally, disconnected from the * The device will be fully reset internally, disconnected from the
* USB bus an a reenumeration will happen. Firmware upload will be * bus an a reenumeration will happen. Firmware upload will be
* neccessary. Thus, we don't do any locking or struct * neccessary. Thus, we don't do any locking or struct
* reinitialization, as we are going to be fully disconnected and * reinitialization, as we are going to be fully disconnected and
* reenumerated. * reenumerated.