linux-toradex.git/drivers/ata, branch v2.6.32.15

libata: ensure NCQ error result taskfile is fully initialized before returning it via qc->result_tf.

2010-05-12T21:57:00+00:00

commit a09bf4cd53b8ab000197ef81f15d50f29ecf973c upstream.

Signed-off-by: Jeff Garzik 
Signed-off-by: Greg Kroah-Hartman

libata: fix locking around blk_abort_request()

2010-05-12T21:56:59+00:00

commit fa41efdae7de61191a7bda3a00e88ef69afb5bb9 upstream.

blk_abort_request() expectes queue lock to be held by the caller.
Grab it before calling the function.

Lack of this synchronization led to infinite loop on corrupt
q->timeout_list.

Signed-off-by: Tejun Heo 
Cc: Jens Axboe 
Signed-off-by: Jeff Garzik 
Signed-off-by: Greg Kroah-Hartman

ahci: AHCI and RAID mode SATA patch for Intel Cougar Point DeviceIDs

2010-04-26T14:41:32+00:00

commit 5623cab83ea61e0420f2064216d83eab067a24c6 upstream.

Signed-off-by: Seth Heasley 
Signed-off-by: Jeff Garzik 
Cc: maximilian attems 
Signed-off-by: Greg Kroah-Hartman

ata_piix: IDE Mode SATA patch for Intel Cougar Point DeviceIDs

2010-04-26T14:41:31+00:00

commit 88e8201e67aace3d86de9e75122ea525f0e7248e upstream.

Signed-off-by: Seth Heasley 
Signed-off-by: Jeff Garzik 
Cc: maximilian attems 
Signed-off-by: Greg Kroah-Hartman

libata: disable NCQ on Crucial C300 SSD

2010-04-26T14:41:23+00:00

commit 68b0ddb289220b6d4d865be128939663be34959d upstream.

Crucial said,

  Thank you for contacting us. We know that with our M225 line of SSDs
  you sometimes need to disable NCQ (native command queuing) to avoid
  just the type of errors you're seeing. Our recommendation for the
  M225 is to add libata.force=noncq to your Linux kernel boot options,
  under the kernel ATA library option.

  I have sent your feedback to the engineers working on the C300, and
  asked them to please pass it on to the firmware team. I have been
  notified that they are in the process of testing and finalizing a
  new firmware version, that you can expect to see released around the
  end of April. We’ll keep you posted as to when it will be available
  for download.

So, turn off NCQ on the drive w/ the current firmware revision.

Reported in the following bug.

  https://bugzilla.kernel.org/show_bug.cgi?id=15573

Signed-off-by: Tejun Heo 
Reported-by: lethalwp@scarlet.be
Reported-by: Luke Macken 
Signed-off-by: Jeff Garzik 
Signed-off-by: Greg Kroah-Hartman

pata_via: Add VIA VX900 support

2010-04-26T14:41:21+00:00

commit 4f1deba435ef75380c1d06fda860c7a15ea16fdf upstream.

Signed-off-by: Joseph Chan 
Signed-off-by: Jeff Garzik 
Signed-off-by: Greg Kroah-Hartman

pata_ali: Fix regression with old devices

2010-04-26T14:41:18+00:00

commit d6250a03fa736c1bff4df4601f5af2dc21f2bf9e upstream.

Making the new stuff work broke some of the old chipsets. We need to go
back to the old set up values for these it seems. Unfortunately even with
documentation this is basically a mix of cargoculting and guesswork.

Chased down to the exact line by Gianluca.

Signed-off-by: Alan Cox 
Signed-off-by: Jeff Garzik 
Cc: Christoph Biedl 
Signed-off-by: Greg Kroah-Hartman

ahci: use BIOS date in broken_suspend list

2010-04-01T22:58:54+00:00

commit 9deb343189b3cf45e84dd08480f330575ffe2004 upstream.

HP is recycling both DMI_PRODUCT_NAME and DMI_BIOS_VERSION making
ahci_broken_suspend() trigger for later products which are not
affected by the original problems.  Match BIOS date instead of version
and add references to bko's so that full information can be found
easier later.

This fixes http://bugzilla.kernel.org/show_bug.cgi?id=15462

Signed-off-by: Tejun Heo 
Reported-by: tigerfishdaisy@gmail.com
Signed-off-by: Jeff Garzik 
Signed-off-by: Greg Kroah-Hartman

pata_hpt3x2n: always stretch UltraDMA timing

2010-03-15T15:49:58+00:00

commit 60661933995bc7a09686c901439e17c2a4ea7d5d upstream.

The UltraDMA Tss timing must be stretched with ATA clock of 66 MHz, but the
driver only does this when PCI clock is 66 MHz, whereas it always programs
DPLL clock (which is used as the ATA clock) to 66 MHz.

Signed-off-by: Sergei Shtylyov 
Signed-off-by: Jeff Garzik 
Signed-off-by: Greg Kroah-Hartman

ahci: disable FPDMA auto-activate optimization on NVIDIA AHCI

2010-03-15T15:49:35+00:00

commit 453d3131ec7aab82eaaa8401a50522a337092aa8 upstream.

Mike Cui reported that his system with an NVIDIA MCP79 (aka MCP7A)
chipset stopped working with 2.6.32. The problem appears to be that
2.6.32 now enables the FPDMA auto-activate optimization in the ahci
driver. The drive works fine with this enabled on an Intel AHCI so
this appears to be a chipset bug.  Since MCP79 is a fairly recent
NVIDIA chipset and we don't have any info on whether any other NVIDIA
chipsets have this issue, disable FPDMA AA optimization on all NVIDIA
AHCI controllers for now.

Should address http://bugzilla.kernel.org/show_bug.cgi?id=14922

Signed-off-by: Robert Hancock 
While-we-investigate-issue-this-patch-looks-good-to-me-by:
	Prajakta Gudadhe 
Signed-off-by: Jeff Garzik 
Signed-off-by: Greg Kroah-Hartman