diff options
author | Sergei Shtylyov <sshtylyov@ru.mvista.com> | 2009-11-27 22:29:02 +0400 |
---|---|---|
committer | Jeff Garzik <jgarzik@redhat.com> | 2009-12-03 14:36:16 -0500 |
commit | 5600c70e576199a7552e1c0fff43f3fe16f5566e (patch) | |
tree | 811a21c65c52b1b166cc518b5200fab1d9991d73 /block/blk.h | |
parent | 8e182a90f91456335756d2ce304ad470795d98e1 (diff) | |
download | linux-5600c70e576199a7552e1c0fff43f3fe16f5566e.tar.bz2 |
pata_hpt{37x|3x2n}: fix timing register masks (take 2)
These drivers inherited from the older 'hpt366' IDE driver the buggy timing
register masks in their set_piomode() metods. As a result, too low command
cycle active time is programmed for slow PIO modes. Quite fortunately, it's
later "fixed up" by the set_dmamode() methods which also "helpfully" reprogram
the command timings, usually to PIO mode 4; unfortunately, setting an UltraDMA
mode #N also reprograms already set PIO data timings, usually to MWDMA mode #
max(N, 2) timings...
However, the drivers added some breakage of their own too: the bit that they
set/clear to control the FIFO is sometimes wrong -- it's actually the MSB of
the command cycle setup time; also, setting it in DMA mode is wrong as this
bit is only for PIO actually and clearing it for PIO modes is not needed as
no mode in any timing table has it set...
Fix all this, inverting the masks while at it, like in the 'hpt366' and
'pata_hpt366' drivers; bump the drivers' versions, accounting for recent
patches that forgot to do it...
Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: stable@kernel.org
Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
Diffstat (limited to 'block/blk.h')
0 files changed, 0 insertions, 0 deletions