linux-stable.git/drivers/ata/libata-core.c, branch v3.6

libata: Add a space to " 2GB ATA Flash Disk" DMA blacklist entry

2012-08-25T14:16:45+00:00

commit d70e551c8e1ecb6f20422f8db6bfe6a0049edcb8, Add " 2GB ATA Flash
Disk"/"ADMA428M" to DMA blacklist, should have added a space before 2GB.

Signed-off-by: Prarit Bhargava 
Signed-off-by: Jeff Garzik

[libata] new quirk, lift bridge limits for Buffalo DriveStation Quattro

2012-08-17T17:36:59+00:00

Michael Eitelwein writes:

I have an external SATA drive that was slowed down by bridge limits. I
found a solution in a thread on this list posted in 2008: It introduces
whitelist entries in libata-core.c for devices with well working bridges
(e.g. email on Fri, 31 Oct 2008 01:45:27 -0400).

I added my device to this whitelist in a custom built kernel and it
works fine for weeks now. How can I have this device added on the
whitelist within the official kernel? Is this whitelist mechanism still
supported or is there a smarter way to achieve whitelisting?

I added the following whitelist entry for my Buffalo DriveStation
Quattro "BUFFALO HD-QSU2/R5":

        /* Devices that do not need bridging limits applied */
        { "MTRON MSP-SATA*",            NULL,   ATA_HORKAGE_BRIDGE_OK, },
        { "BUFFALO HD-QSU2/R5",         NULL,   ATA_HORKAGE_BRIDGE_OK, },

Reported-by: Michael Eitelwein 
Signed-off-by: Jeff Garzik

Merge branch 'master' [vanilla Linus master] into libata-dev.git/upstream

2012-07-25T19:58:48+00:00

Two bits were appended to the end of the bitfield
list in struct scsi_device.  Resolve that conflict
by including both bits.

Conflicts:
	include/scsi/scsi_device.h

[libata] Prevent interface errors with Seagate FreeAgent GoFlex

2012-07-25T18:34:42+00:00

When using my Seagate FreeAgent GoFlex eSATAp external disk enclosure,
interface errors are always seen until 1.5Gbps is negotiated [1]. This
occurs using any disk in the enclosure, and when the disk is connected
directly with a generic passive eSATAp cable, we see stable 3Gbps
operation as expected.

Blacklist 3Gbps mode to avoid dataloss and the ~30s delay bus reset
and renegotiation incurs.

Signed-off-by: Daniel J Blueman 
Signed-off-by: Jeff Garzik

[SCSI] libata, libsas: introduce sched_eh and end_eh port ops

2012-07-20T07:58:45+00:00

When managing shost->host_eh_scheduled libata assumes that there is a
1:1 shost-to-ata_port relationship.  libsas creates a 1:N relationship
so it needs to manage host_eh_scheduled cumulatively at the host level.
The sched_eh and end_eh port port ops allow libsas to track when domain
devices enter/leave the "eh-pending" state under ha->lock (previously
named ha->state_lock, but it is no longer just a lock for ha->state
changes).

Since host_eh_scheduled indicates eh without backing commands pinning
the device it can be deallocated at any time.  Move the taking of the
domain_device reference under the port_lock to guarantee that the
ata_port stays around for the duration of eh.

Reviewed-by: Jacek Danecki 
Acked-by: Jeff Garzik 
Signed-off-by: Dan Williams 
Signed-off-by: James Bottomley

libata: detect Device Attention support

2012-06-29T15:38:17+00:00

Add a new flag ATA_DFLAG_DA to indicate that device supports "Device
Attention".

Acked-by: Aaron Lu 
Signed-off-by: Lin Ming 
Signed-off-by: Jeff Garzik

libata: migrate ACPI code over to new bindings

2012-06-29T15:38:11+00:00

Now that we have the ability to directly glue the ACPI namespace to the
driver model in libata, we don't need the custom code to handle the same
thing. Remove it and migrate the functions over to the new code.

Signed-off-by: Matthew Garrett 
Signed-off-by: Holger Macht 
Signed-off-by: Lin Ming 
Signed-off-by: Jeff Garzik

libata: bind the Linux device tree to the ACPI device tree

2012-06-29T15:38:10+00:00

Associate the ACPI device tree and libata devices.
This patch uses the generic ACPI glue framework to do so.

Signed-off-by: Matthew Garrett 
Signed-off-by: Holger Macht 
Signed-off-by: Lin Ming 
Signed-off-by: Jeff Garzik

[libata] Add " 2GB ATA Flash Disk"/"ADMA428M" to DMA blacklist

2012-05-22T20:02:14+00:00

A user has several systems with a couple of models of flash disks with IDE
connectors.  These disks work fine in 2.6.18-ish kernels but corrupt data on
new kernels.

The difference appears to be with the default I/O method used by the IDE
controller driver between the kernels.  In the older kernels, the
configuration is very conservative and the driver stays in PIO mode.  With
new kernels, the ata driver (pata_serverworks) attempts to use UDMA/66
which the drive claims to support.  This mode, however, does not appear to
work in DMA mode.  The drive does work correctly and no corruption is
seen if the kernel parameter "libata.force=5:pio0,6:pio0" is used to force
the driver to use PIO instead of DMA mode.

Blacklist these drives.  Unfortunately the model name of the drive is very
generic, " 2GB ATA Flash Disk", but the revision is specific, "ADMA428M".

Signed-off-by: Prarit Bhargava 
Signed-off-by: Jeff Garzik

libata: add a host flag to ignore detected ATA devices

2012-05-07T19:32:23+00:00

Where devices are visible via more than one host we sometimes wish to
indicate that cirtain devices should be ignored on a specific host.  Add a
host flag indicating that this host wishes to ignore ATA specific devices.

Signed-off-by: Andy Whitcroft 
Signed-off-by: Jeff Garzik