| commit | c018f1ee5cf81e58b93d9e93a2ee39cad13dc1ac | |
| author | Sergei Shtylyov <sshtylyov@ru.mvista.com> | |
| Sat, 18 Apr 2009 15:42:19 +0000 (18 17:42 +0200) | ||
| committer | Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> | |
| Sat, 18 Apr 2009 15:42:19 +0000 (18 17:42 +0200) | ||
| tree | 01b468a57d95471c28be378868ebadaac481412b | treesnapshot (tar.gz zip) |
| parent | aefe6475720bd5eb8aacbc881488f3aa65618562 | commitdiff |
hpt366: fix HPT370 DMA timeouts
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>
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>
| drivers/ide/hpt366.c | diffblobblamehistory |