summaryrefslogtreecommitdiff
path: root/fs/jfs
diff options
context:
space:
mode:
authorStefan Richter <stefanr@s5r6.in-berlin.de>2008-05-10 22:34:07 (GMT)
committerStefan Richter <stefanr@s5r6.in-berlin.de>2008-07-14 11:00:17 (GMT)
commitd2886ea368a67704ecc13e69075f18a9d74cb12b (patch)
tree54593ba6b45d1a4cdec66da4aa7d8d813cc49a3a /fs/jfs
parentbce7f793daec3e65ec5c5705d2457b81fe7b5725 (diff)
downloadlinux-d2886ea368a67704ecc13e69075f18a9d74cb12b.tar.xz
scsi: sd: optionally set power condition in START STOP UNIT
Adds a new scsi_device flag, start_stop_pwr_cond: If enabled, the sd driver will not send plain START STOP UNIT commands but ones with the power condition field set to 3 (standby) or 1 (active) respectively. Some FireWire disk firmwares do not stop the motor if power condition is zero. Or worse, they become unresponsive after a START STOP UNIT with power condition = 0 and start = 0. http://lkml.org/lkml/2008/4/29/704 This patch only adds the necessary code to sd_mod but doesn't activate it. Follow-up patches to the FireWire drivers will add detection of affected devices and enable the code for them. I did not add power condition values to scsi_error.c::scsi_eh_try_stu() for now. The three firmwares which suffer from above mentioned problems do not need START STOP UNIT in the error handler, and they are not adversely affected by START STOP UNIT with power condition = 0 and start = 1 (like scsi_eh_try_stu() sends it if scsi_device.allow_restart is enabled). Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> Tested-by: Tino Keitel <tino.keitel@gmx.de>
Diffstat (limited to 'fs/jfs')
0 files changed, 0 insertions, 0 deletions