diff options
| author | Stanislaw Gruszka <sgruszka@redhat.com> | 2013-09-09 12:37:37 +0200 |
|---|---|---|
| committer | John W. Linville <linville@tuxdriver.com> | 2013-09-09 14:44:34 -0400 |
| commit | f4e1a4d3ecbb9e42bdf8e7869ee8a4ebfa27fb20 (patch) | |
| tree | 8387f2af05e0e200c71ca788e02605658115ea1e /drivers/bluetooth/btusb.c | |
| parent | aaa2ced15ad8dca8048666c9f70736424d696a6b (diff) | |
| download | talos-op-linux-f4e1a4d3ecbb9e42bdf8e7869ee8a4ebfa27fb20.tar.gz talos-op-linux-f4e1a4d3ecbb9e42bdf8e7869ee8a4ebfa27fb20.zip | |
rt2800: change initialization sequence to fix system freeze
My commit
commit c630ccf1a127578421a928489d51e99c05037054
Author: Stanislaw Gruszka <stf_xl@wp.pl>
Date: Sat Mar 16 19:19:46 2013 +0100
rt2800: rearrange bbp/rfcsr initialization
make Maxim machine freeze when try to start wireless device.
Initialization order and sending MCU_BOOT_SIGNAL request, changed in
above commit, is important. Doing things incorrectly make PCIe bus
problems, which can froze the machine.
This patch change initialization sequence like vendor driver do:
function NICInitializeAsic() from
2011_1007_RT5390_RT5392_Linux_STA_V2.5.0.3_DPO (PCI devices) and
DPO_RT5572_LinuxSTA_2.6.1.3_20121022 (according Mediatek, latest driver
for RT8070/RT3070/RT3370/RT3572/RT5370/RT5372/RT5572 USB devices).
It fixes freezes on Maxim system.
Resolve:
https://bugzilla.redhat.com/show_bug.cgi?id=1000679
Reported-and-tested-by: Maxim Polyakov <polyakov@dexmalabs.com>
Bisected-by: Igor Gnatenko <i.gnatenko.brain@gmail.com>
Cc: stable@vger.kernel.org # 3.10+
Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/bluetooth/btusb.c')
0 files changed, 0 insertions, 0 deletions
