aboutsummaryrefslogtreecommitdiffstats
path: root/crypto/twofish_generic.c
diff options
context:
space:
mode:
authorSarah Sharp <sarah.a.sharp@linux.intel.com>2010-07-29 22:13:00 -0700
committerGreg Kroah-Hartman <gregkh@suse.de>2010-08-10 14:35:45 -0700
commitc21599a36165dbc78b380846b254017a548b9de5 (patch)
treef6e0cdf815e2e1a991f39489e6bd02c10afa22f1 /crypto/twofish_generic.c
parent257d585aaec469ded6ec15d8a8e7ebada21d7277 (diff)
downloadkernel_samsung_smdk4412-c21599a36165dbc78b380846b254017a548b9de5.zip
kernel_samsung_smdk4412-c21599a36165dbc78b380846b254017a548b9de5.tar.gz
kernel_samsung_smdk4412-c21599a36165dbc78b380846b254017a548b9de5.tar.bz2
USB: xhci: Reduce reads and writes of interrupter registers.
The interrupter register set includes a register that says whether interrupts are pending for each event ring (the IP bit). Each MSI-X vector will get its own interrupter set with separate IP bits. The status register includes an "Event Interrupt (EINT)" bit that is set when an IP bit is set in any of the interrupters. When PCI interrupts are used, the EINT bit exactly mirrors the IP bit in the single interrupter set, and it is a waste of time to check both registers when trying to figure out if the xHC interrupted or another device on the shared IRQ line interrupted. Only check the IP bit to reduce register reads. The IP bit is automatically cleared by the xHC when MSI or MSI-X is enabled. It doesn't make sense to read that register to check for shared interrupts (since MSI and MSI-X aren't shared). It also doesn't make sense to write to that register to clear the IP bit, since it is cleared by the hardware. We can tell whether MSI or MSI-X is enabled by looking at the irq number in hcd->irq. If it's -1, we know MSI or MSI-X is enabled. Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'crypto/twofish_generic.c')
0 files changed, 0 insertions, 0 deletions