diff options
author | Sergei Shtylyov <sshtylyov@ru.mvista.com> | 2009-04-18 17:42:19 +0200 |
---|---|---|
committer | Chris Wright <chrisw@sous-sol.org> | 2009-04-27 10:37:01 -0700 |
commit | 2a3403fd95cbf6f548198be0fd37a056d12a56fe (patch) | |
tree | 763f4318c6fd73f808f0892bfef8573f1f219054 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 6c6737beae9981a707c1a4e1e9f1baf7cc47ce5f (diff) |
hpt366: fix HPT370 DMA timeouts
upstream commit: c018f1ee5cf81e58b93d9e93a2ee39cad13dc1ac
The big driver change in 2.4.19-rc1 introduced a regression for many HPT370[A]
chips -- DMA stopped to work completely, only causing endless timeouts...
The culprit has been identified (at last!): it turned to be the code resetting
the DMA state machine before each transfer. Stop doing it now as this counter-
measure has clearly caused more harm than good.
This should fix the kernel.org bug #7703.
Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Signed-off-by: Chris Wright <chrisw@sous-sol.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions