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

[libata] add DVRTD08A and DVR-215 to NOSETXFER device quirk list

2012-01-18T01:50:07+00:00

Signed-off-by: Jeff Garzik

ata: add ata port hibernate callbacks

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

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

ata: update ata port's runtime status during system resume

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

The ata port is brought back to full power state during system resume.
So its runtime PM status will have to be updated to reflect
the actual post-system sleep status.

This also fixes below warning during system suspend/resume.

WARNING: at /work/linux/drivers/ata/libata-eh.c:4034
ata_scsi_port_error_handler+0x89/0x557()

4034         WARN_ON(!(ap->pflags & ATA_PFLAG_SUSPENDED));

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

libata-core: kill duplicate statement in ata_do_set_mode()

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

Commit b3a706014e56b1356e7b275fd25b833c63175bf0 (libata: Add a
drivers/ide style DMA disable) neglected to remove the line in
ata_do_set_mode() it has obviously made useless/duplicated.  Do this
now, and make a line added back then wrapped properly...

Signed-off-by: Sergei Shtylyov 
Signed-off-by: Jeff Garzik

ata: add ata port runtime PM callbacks

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

Add ata port runtime suspend/resume/idle callbacks.
Set ->eh_noresume to skip the runtime PM calls on scsi host
in the error handler to avoid dead lock.

Acked-by: Tejun Heo 
Signed-off-by: Lin Ming 
Signed-off-by: Jeff Garzik

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

Merge git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6

2011-10-28T23:44:18+00:00

* git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6: (204 commits)
  [SCSI] qla4xxx: export address/port of connection (fix udev disk names)
  [SCSI] ipr: Fix BUG on adapter dump timeout
  [SCSI] megaraid_sas: Fix instance access in megasas_reset_timer
  [SCSI] hpsa: change confusing message to be more clear
  [SCSI] iscsi class: fix vlan configuration
  [SCSI] qla4xxx: fix data alignment and use nl helpers
  [SCSI] iscsi class: fix link local mispelling
  [SCSI] iscsi class: Replace iscsi_get_next_target_id with IDA
  [SCSI] aacraid: use lower snprintf() limit
  [SCSI] lpfc 8.3.27: Change driver version to 8.3.27
  [SCSI] lpfc 8.3.27: T10 additions for SLI4
  [SCSI] lpfc 8.3.27: Fix queue allocation failure recovery
  [SCSI] lpfc 8.3.27: Change algorithm for getting physical port name
  [SCSI] lpfc 8.3.27: Changed worst case mailbox timeout
  [SCSI] lpfc 8.3.27: Miscellanous logic and interface fixes
  [SCSI] megaraid_sas: Changelog and version update
  [SCSI] megaraid_sas: Add driver workaround for PERC5/1068 kdump kernel panic
  [SCSI] megaraid_sas: Add multiple MSI-X vector/multiple reply queue support
  [SCSI] megaraid_sas: Add support for MegaRAID 9360/9380 12GB/s controllers
  [SCSI] megaraid_sas: Clear FUSION_IN_RESET before enabling interrupts
  ...

libata: ata_timing_compute() fixup

2011-10-14T17:21:54+00:00

XFER_SW_DMA_0 mode should be excluded from the extended cycle timing
computations.

Acked-by: Alan Cox 
Noticed-by: Sergei Shtylyov 
Signed-off-by: Bartlomiej Zolnierkiewicz 
Signed-off-by: Jeff Garzik

[SCSI] libsas,libata: fix ->change_queue_{depth|type} for sata devices

2011-10-02T17:30:30+00:00

Pass queue_depth change requests to libata, and prevent queue_type
changes for ATA devices.

Otherwise:
1/ we do not honor the libata specific restrictions on the queue depth
2/ libsas drivers that do not set sdev->tagged_supported are unable to
   change the queue_depth of ata devices via sysfs

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

libata: report link resume failure as KERN_WARNING instead of ERR

2011-07-23T22:02:51+00:00

Link resume failure in itself isn't an error condition and may happen
regularly depending on hardware configuration.  Reporting it as
KERN_ERR makes the condition unnecessarily prominent (e.g. reported
during boot).  Use KERN_WARNING instead.

Signed-off-by: Tejun Heo 
Reported-by: David Shaw 
Signed-off-by: Jeff Garzik