Searched hist:"5 fe4dffb" (Results 1 – 5 of 5) sorted by relevance
| /openbmc/linux/drivers/net/wireless/ath/ath6kl/ |
| H A D | bmi.c | 5fe4dffb Sun Oct 30 14:16:15 CDT 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: power down hardware when interface is down
The benefit from this is that user space can control hardware's power state
by putting interface up and down. This is handy if firmware gets to some
weird state.
The downside will be that putting interface up takes a bit longer,
I was measuring ~500 ms during interface up.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
5fe4dffb Sun Oct 30 14:16:15 CDT 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: power down hardware when interface is down
The benefit from this is that user space can control hardware's power state
by putting interface up and down. This is handy if firmware gets to some
weird state.
The downside will be that putting interface up takes a bit longer,
I was measuring ~500 ms during interface up.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
|
| H A D | bmi.h | 5fe4dffb Sun Oct 30 14:16:15 CDT 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: power down hardware when interface is down
The benefit from this is that user space can control hardware's power state
by putting interface up and down. This is handy if firmware gets to some
weird state.
The downside will be that putting interface up takes a bit longer,
I was measuring ~500 ms during interface up.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
5fe4dffb Sun Oct 30 14:16:15 CDT 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: power down hardware when interface is down
The benefit from this is that user space can control hardware's power state
by putting interface up and down. This is handy if firmware gets to some
weird state.
The downside will be that putting interface up takes a bit longer,
I was measuring ~500 ms during interface up.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
|
| H A D | main.c | 5fe4dffb Sun Oct 30 14:16:15 CDT 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: power down hardware when interface is down
The benefit from this is that user space can control hardware's power state
by putting interface up and down. This is handy if firmware gets to some
weird state.
The downside will be that putting interface up takes a bit longer,
I was measuring ~500 ms during interface up.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
5fe4dffb Sun Oct 30 14:16:15 CDT 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: power down hardware when interface is down
The benefit from this is that user space can control hardware's power state
by putting interface up and down. This is handy if firmware gets to some
weird state.
The downside will be that putting interface up takes a bit longer,
I was measuring ~500 ms during interface up.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
|
| H A D | init.c | 5fe4dffb Sun Oct 30 14:16:15 CDT 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: power down hardware when interface is down
The benefit from this is that user space can control hardware's power state
by putting interface up and down. This is handy if firmware gets to some
weird state.
The downside will be that putting interface up takes a bit longer,
I was measuring ~500 ms during interface up.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
5fe4dffb Sun Oct 30 14:16:15 CDT 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: power down hardware when interface is down
The benefit from this is that user space can control hardware's power state
by putting interface up and down. This is handy if firmware gets to some
weird state.
The downside will be that putting interface up takes a bit longer,
I was measuring ~500 ms during interface up.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
|
| H A D | core.h | 5fe4dffb Sun Oct 30 14:16:15 CDT 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: power down hardware when interface is down
The benefit from this is that user space can control hardware's power state
by putting interface up and down. This is handy if firmware gets to some
weird state.
The downside will be that putting interface up takes a bit longer,
I was measuring ~500 ms during interface up.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
5fe4dffb Sun Oct 30 14:16:15 CDT 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: power down hardware when interface is down
The benefit from this is that user space can control hardware's power state
by putting interface up and down. This is handy if firmware gets to some
weird state.
The downside will be that putting interface up takes a bit longer,
I was measuring ~500 ms during interface up.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
|