summaryrefslogtreecommitdiffstats
path: root/drivers/firewire/Kconfig
diff options
context:
space:
mode:
authorStefan Richter <stefanr@s5r6.in-berlin.de>2014-04-16 01:08:08 +0200
committerStefan Richter <stefanr@s5r6.in-berlin.de>2014-05-29 19:02:22 +0200
commitd151f9854f21fbb6a2df73553a27f9b664ecd10c (patch)
tree6100e8a5f831971d8ac0a74146658b4955f82177 /drivers/firewire/Kconfig
parentb3d681a4fc108f9653bbb44e4f4e72db2b8a5734 (diff)
downloadlinux-d151f9854f21fbb6a2df73553a27f9b664ecd10c.tar.gz
linux-d151f9854f21fbb6a2df73553a27f9b664ecd10c.tar.bz2
linux-d151f9854f21fbb6a2df73553a27f9b664ecd10c.zip
firewire: ohci: enable MSI for VIA VT6315 rev 1, drop cycle timer quirk
Commit af0cdf494781 "firewire: ohci: fix regression with VIA VT6315, disable MSI" acted upon a report against VT6315 rev 0: http://linux.derkeiler.com/Mailing-Lists/Kernel/2010-12/msg02301.html $ lspci -nn VIA Technologies, Inc. VT6315 Series Firewire Controller [1106:3403] I now got a card with $ lspci -nn VIA Technologies, Inc. VT6315 Series Firewire Controller [1106:3403] (rev 01) and this works fine with MSI enabled. Second, I tested this VT6315 rev 1 without CYCLE_TIMER quirk flag using http://me.in-berlin.de/~s5r6/linux1394/utils/test_cycle_time_v20100125.c and found that this chip does in fact access the cycle timer atomically. Things I can't test because I don't have the hardware: - whether VT6315 rev 0 really needs QUIRK_CYCLE_TIMER, - whether the VT6320 PCI device needs QUIRK_CYCLE_TIMER, - whether the VT6325 and VT6330 PCIe devices need QUIRK_CYCLE_TIMER and QUIRK_NO_MSI. Hence, just add a whitelist entry specifically for VT6315 rev >= 1 without any quirk flags. Before this entry we need an extra entry to catch VT6315 rev <= 0 due to how our ID matching logic works. Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Diffstat (limited to 'drivers/firewire/Kconfig')
0 files changed, 0 insertions, 0 deletions