aboutsummaryrefslogtreecommitdiffstats
path: root/net/bluetooth
diff options
context:
space:
mode:
authorSarah Sharp <sarah.a.sharp@linux.intel.com>2012-03-16 13:19:35 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-04-22 16:21:42 -0700
commit4f4227f37036c13f42dac881b8bed4ca5e8e414f (patch)
tree0c41ea088f81c037c92e06a8c9474a587005cffe /net/bluetooth
parent64bc099c97abc7b2657351629615a8e9f43d6458 (diff)
downloadkernel_samsung_smdk4412-4f4227f37036c13f42dac881b8bed4ca5e8e414f.zip
kernel_samsung_smdk4412-4f4227f37036c13f42dac881b8bed4ca5e8e414f.tar.gz
kernel_samsung_smdk4412-4f4227f37036c13f42dac881b8bed4ca5e8e414f.tar.bz2
xhci: Fix register save/restore order.
commit c7713e736526d8c9f6f87716fb90562a8ffaff2c upstream. The xHCI 1.0 spec errata released on June 13, 2011, changes the ordering that the xHCI registers are saved and restored in. It moves the interrupt pending (IMAN) and interrupt control (IMOD) registers to be saved and restored last. I believe that's because the host controller may attempt to fetch the event ring table when interrupts are re-enabled. Therefore we need to restore the event ring registers before we re-enable interrupts. This should be backported to kernels as old as 2.6.37, that contain the commit 5535b1d5f8885695c6ded783c692e3c0d0eda8ca "USB: xHCI: PCI power management implementation" Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com> Tested-by: Elric Fu <elricfu1@gmail.com> Cc: Andiry Xu <andiry.xu@amd.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/bluetooth')
0 files changed, 0 insertions, 0 deletions