diff options
| author | Andrew Chew <achew@nvidia.com> | 2006-01-04 19:13:04 -0800 |
|---|---|---|
| committer | Jeff Garzik <jgarzik@pobox.com> | 2006-01-09 10:42:06 -0500 |
| commit | b887030aec0971a47ca97a18e93ff446bc7d049e (patch) | |
| tree | 77ecea6cce7d8047ad39feea2d0b0cbff1bdbad2 /sound | |
| parent | 5367f2d67c7d0bf1faae90e6e7b4e2ac3c9b5e0f (diff) | |
| download | linux-b887030aec0971a47ca97a18e93ff446bc7d049e.tar.gz linux-b887030aec0971a47ca97a18e93ff446bc7d049e.tar.bz2 linux-b887030aec0971a47ca97a18e93ff446bc7d049e.zip | |
[PATCH] sata_nv, spurious interrupts at system startup with MAXTOR 6H500F0 drive
This patch works around a problem with spurious interrupts seen at boot time when
a MAXTOR 6H500F0 drive is present. An ATA interrupt condition is mysteriously
present at start of day. If we took too long in issuing the first command,
the kernel would basically get tired of the spurious interrupts and turn the interrupt
off. Issuing the first command essentially causes the interrupt condition to
get acknowledged.
I haven't seen this happen with any other drives.
What I basically do is ack ATA status by reading it regardless of whether we're
expecting to have to handle an interrupt. This clears the start-of-day anomalous
interrupt condition, and keeps the kernel from disabling that interrupt due to
too many spurious interrupts.
Also, I fixed a bug where hotplug interrupts weren't getting acknowledged as handled
in the ISR. This was not the cause of the spurious interrupts, but it's the right
thing to do anyway.
Signed-Off-By: Andrew Chew
Signed-off-by: Jeff Garzik <jgarzik@pobox.com>
Diffstat (limited to 'sound')
0 files changed, 0 insertions, 0 deletions