linux-stable.git/drivers/ata, branch linux-2.6.19.y

pata_amd: fix an obvious bug in cable detection

2007-02-24T00:24:26+00:00

80c test mask is at bits 18 and 19 of EIDE Controller Configuration
not 22 and 23.  Fix it.

Signed-off-by: Tejun Heo 
Acked-by: Alan Cox

[PATCH] libata: use kmap_atomic(KM_IRQ0) in SCSI simulator

2007-02-05T16:31:44+00:00

We are inside spin_lock_irqsave().  quoth akpm's debug facility:

 [  231.948000] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
 [  232.232000] ata1.00: configured for UDMA/33
 [  232.404000] WARNING (1) at arch/i386/mm/highmem.c:47 kmap_atomic()
 [  232.404000]  [] kmap_atomic+0xa9/0x1ab
 [  232.404000]  [] ata_scsi_rbuf_get+0x1c/0x30
 [  232.404000]  [] ata_scsi_rbuf_fill+0x1a/0x87
 [  232.404000]  [] ata_scsiop_mode_sense+0x0/0x309
 [  232.404000]  [] end_bio_bh_io_sync+0x0/0x37
 [  232.404000]  [] scsi_done+0x0/0x16
 [  232.404000]  [] scsi_done+0x0/0x16
 [  232.404000]  [] ata_scsi_simulate+0xb0/0x13f
[...]

Signed-off-by: Jeff Garzik 
Cc: Andrew Morton 
Signed-off-by: Chris Wright

[PATCH] libata: handle 0xff status properly

2007-01-10T19:05:18+00:00

libata waits for !BSY even when the status register reports 0xff.
This causes long boot delays when D8 isn't pulled down properly.  This
patch does the followings.

* don't wait if status register is 0xff in all wait functions

* make ata_busy_sleep() return 0 on success and -errno on failure.
  -ENODEV is returned on 0xff status and -EBUSY on other failures.

* make ata_bus_softreset() succeed on 0xff status.  0xff status is not
  reset failure.  It indicates no device.  This removes unnecessary
  retries on such ports.  Note that the code change assumes unoccupied
  port reporting 0xff status does not produce valid device signature.

Signed-off-by: Tejun Heo 
Cc: Joe Jin 
Signed-off-by: Jeff Garzik 
Signed-off-by: Chris Wright

[PATCH] libata: Fixup ata_sas_queuecmd to handle __ata_scsi_queuecmd failure

2006-11-28T08:51:55+00:00

Fixes ata_sas_queuecmd to properly handle a failure from
__ata_scsi_queuecmd.

Signed-off-by: Brian King 
Signed-off-by: Jeff Garzik

[PATCH] ahci: AHCI mode SATA patch for Intel ICH9

2006-11-28T08:45:13+00:00

This patch adds the Intel ICH9 AHCI controller DID's for SATA support.

Signed-off-by:  Jason Gaston 
Signed-off-by: Jeff Garzik

[PATCH] libata: don't schedule EH on wcache on/off if old EH

2006-11-28T08:45:13+00:00

Do not schedule EH for revalidation on wcache on/off if old EH.  Old
EH cannot handle it and will result in WARN_ON()'s and oops.

This closes bug #7412.

Signed-off-by: Tejun Heo 
Signed-off-by: Jeff Garzik

Merge branch 'upstream-linus' of master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev

2006-11-14T23:15:31+00:00

* 'upstream-linus' of master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev:
  libata: fix double-completion on error
  [PATCH] pata_artop: fix "& (1 >>" typo
  [PATCH] hpt37x: Check the enablebits

[PATCH] libata: Convert from module_init to subsys_initcall

2006-11-14T23:08:50+00:00

When building a monolithic kernel, the load order of drivers does not
work for SAS libata users, resulting in a kernel oops.

Convert libata to use subsys_initcall instead of module_init, which
ensures that libata gets loaded before any LLDD.

This is the same thing that scsi core does to solve the problem.  The
load order problem was observed on ipr SAS adapters and should exist for
other SAS users as well.

Signed-off-by: Brian King 
Acked-by: Jeff Garzik 
Signed-off-by: Linus Torvalds

libata: fix double-completion on error

2006-11-14T14:55:41+00:00

A curious thing happens, however, when ata_qc_new_init fails to get
an ata_queued_cmd:

First, ata_qc_new_init handles the failure like this:
    cmd->result = (DID_OK << 16) | (QUEUE_FULL << 1);
    done(cmd);

Then, we return to ata_scsi_translate and do this:
    err_mem:
        cmd->result = (DID_ERROR << 16);
        done(cmd);

It appears to me that first we set a status code indicating that we're
ok but the device queue is full and finish the command,  but then
we blow away that status code and replace it with an error flag and
finish the command a second time!  That does not seem to be desirable
behavior since we merely want the I/O to wait until a command slot
frees up, not send errors up the block layer.

In the err_mem case, we should simply exit out of ata_scsi_translate
instead.

Signed-off-by: Darrick J. Wong 
Signed-off-by: Jeff Garzik

[PATCH] pata_artop: fix "& (1 >>" typo

2006-11-14T14:52:08+00:00

Signed-off-by: Alexey Dobriyan 
Signed-off-by: Jeff Garzik