Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 81b182a7 authored by Dirk Brandewie's avatar Dirk Brandewie Committed by Inaky Perez-Gonzalez
Browse files

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



Fixing comments from original cut and paste error

Signed-off-by: default avatarDirk Brandewie <dirk.j.brandewie@intel.com>
Signed-off-by: default avatarInaky Perez-Gonzalez <inaky@linux.intel.com>
parent abb30733

drivers/net/wimax/i2400m/sdio.c

+6 −7
Original line number Diff line number Diff line
@@ -233,18 +233,17 @@ int __i2400ms_send_barker(struct i2400ms *i2400ms, 
 * Warm reset:

 *

 * 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.

 *

 * The device will send a reboot barker in the notification endpoint

 * that will trigger the driver to reinitialize the state

 * automatically from notif.c:i2400m_notification_grok() into

 * i2400m_dev_bootstrap_delayed().

 * The device will send a reboot barker that will trigger the driver

 * to reinitialize the state via __i2400m_dev_reset_handle.

 *

 * Cold and bus (USB) reset:

 *

 * Cold and bus reset:

 *

 * 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

 * reinitialization, as we are going to be fully disconnected and

 * reenumerated.