linux-toradex.git/drivers/ata/libata.h, branch v3.6.1

libata-acpi: add missing inlines in libata.h

2012-07-25T18:15:03+00:00

Adds inline for ata_acpi_unregister/ata_acpi_bind/ata_acpi_unbind
in drivers/ata/libata.h for !CONFIG_ATA_ACPI to fix below warnings.

warning: 'ata_acpi_unregister' defined but not used [-Wunused-function]
warning: 'ata_acpi_bind' defined but not used [-Wunused-function]
warning: 'ata_acpi_unbind' defined but not used [-Wunused-function]

Reported-by: Stephen Rothwell 
Signed-off-by: Lin Ming 
Signed-off-by: Jeff Garzik

libata-acpi: add ata port runtime D3Cold support

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

ATA port may support runtime D3Cold state, for example, Zero-power ODD case.
This patch adds wakeup notifier and enable/disable run_wake during
supend/resume.

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: make ata_print_id atomic

2012-04-12T19:57:51+00:00

This variable is incremented from multiple contexts (module_init via
libata-lldds and the libsas discovery thread).  Make it atomic to head
off any chance of libsas and libata creating duplicate ids.

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

[SCSI] libsas: async ata scanning

2012-02-29T21:35:41+00:00

libsas ata error handling is already async but this does not help the
scan case.  Move initial link recovery out from under host->scan_mutex,
and delay synchronization with eh until after all port probe/recovery
work has been queued.

Device ordering is maintained with scan order by still calling
sas_rphy_add() in order of domain discovery.

Since we now scan the domain list when invoking libata-eh we need to be
careful to check for fully initialized ata ports.

Acked-by: Jack Wang 
Acked-by: Jeff Garzik 
Signed-off-by: Dan Williams 
Signed-off-by: James Bottomley

[SCSI] libsas: execute transport link resets with libata-eh via host workqueue

2012-02-19T20:13:51+00:00

Link resets leave ata affiliations intact, so arrange for libsas to make
an effort to avoid dropping the device due to a slow-to-recover link.
Towards this end carry out reset in the host workqueue so that it can
check for ata devices and kick the reset request to libata.  Hard
resets, in contrast, bypass libata since they are meant for associating
an ata device with another initiator in the domain (tears down
affiliations).

Need to add a new transport_sas_phy_reset() since the current
sas_phy_reset() is a utility function to libsas lldds.  They are not
prepared for it to loop back into eh.

Signed-off-by: Dan Williams 
Signed-off-by: James Bottomley

ata: add ata port system PM callbacks

2012-01-09T00:14:58+00:00

Change ata_host_request_pm to ata_port_request_pm which performs
port suspend/resume.

Add ata port type driver which implements port PM callbacks.

Signed-off-by: Lin Ming 
Signed-off-by: Jeff Garzik

libata: plumb sas port scan into standard libata paths

2011-03-02T07:36:45+00:00

The function ata_sas_port_init() has always really done its own thing.
However, as a precursor to moving to the libata new eh, it has to be
properly using the standard libata scan paths.  This means separating
the current libata scan paths into pieces which can be shared with
libsas and pieces which cant (really just the async call and the host
scan).

Signed-off-by: James Bottomley 
Signed-off-by: Jeff Garzik

libata: implement cross-port EH exclusion

2010-10-22T00:21:05+00:00

In libata, the non-EH code paths should always take and release
ap->lock explicitly when accessing hardware or shared data structures.
However, once EH is active, it's assumed that the port is owned by EH
and EH methods don't explicitly take ap->lock unless race from irq
handler or other code paths are expected.  However, libata EH didn't
guarantee exclusion among EHs for ports of the same host.  IOW,
multiple EHs may execute in parallel on multiple ports of the same
controller.

In many cases, especially in SATA, the ports are completely
independent of each other and this doesn't cause problems; however,
there are cases where different ports share the same resource, which
lead to obscure timing related bugs such as the one fixed by commit
213373cf (ata_piix: fix locking around SIDPR access).

This patch implements exclusion among EHs of the same host.  When EH
begins, it acquires per-host EH ownership by calling ata_eh_acquire().
When EH finishes, the ownership is released by calling
ata_eh_release().  EH ownership is also released whenever the EH
thread goes to sleep from ata_msleep() or explicitly and reacquired
after waking up.

This ensures that while EH is actively accessing the hardware, it has
exclusive access to it while allowing EHs to interleave and progress
in parallel as they hit waiting stages, which dominate the time spent
in EH.  This achieves cross-port EH exclusion without pervasive and
fragile changes while still allowing parallel EH for the most part.

This was first reported by yuanding02@gmail.com more than three years
ago in the following bugzilla.  :-)

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

Signed-off-by: Tejun Heo 
Cc: Alan Cox 
Reported-by: yuanding02@gmail.com
Signed-off-by: Jeff Garzik