This patch avoids that complaints similar to the following appear in
> the kernel log if runtime power management is enabled:
Applied to 4.18/scsi-fixes, thanks!
--
Martin K. Petersen Oracle Linux Engineering
On Fri, Aug 03, 2018 at 10:28:45AM +0200, Johannes Thumshirn wrote:
> On Thu, Aug 02, 2018 at 10:44:42AM -0700, Bart Van Assche wrote:
> > Surround scsi_execute() calls with scsi_autopm_get_device() and
> > scsi_autopm_put_device(). Note: removing sr_mutex protection from
> > the scsi_cd_get() and
to the following appear in
the kernel log if runtime power management is enabled:
INFO: task systemd-udevd:650 blocked for more than 120 seconds.
Not tainted 4.18.0-rc7-dbg+ #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
systemd-udevd D28176 650513 0x
rate clock source.
+- rpm-level: UFS Runtime power management level. Following PM
levels are supported:
+ 0 - Both UFS device and Link in active state (Highest
power consumption)
+ 1 - UFS device in active state but Link in Hibe
UFS device and link can be put in multiple different low power modes hence
UFS driver supports multiple different low power modes.
This change sets the default UFS power management level which should put
the link hibernate state and device in sleep state. This default power
management level gives
OFF state (Lowest power consumption)
+- spm-level : UFS System power management level. Allowed
PM
levels are same as rpm-level.
This looks like you are putting policy for Linux into DT.
What I would expect to see here is disabling of states that don't
work
due to some h/w lim
operties:
>>> -lanes-per-direction : number of lanes available per direction -
>>> either 1 or 2.
>>> Note that it is assume same number of lanes is
>>> used both
>>> directions at once. If not spe
assume same number of lanes is used
both
directions at once. If not specified, default is 2 lanes per
direction.
+- rpm-level : UFS Runtime power management level. Following PM
levels are supported:
+ 0 - Both UFS device and Link in active state (Highest power
consumption)
+
per direction - either 1 or
> 2.
> Note that it is assume same number of lanes is used
> both
> directions at once. If not specified, default is 2
> lanes per direction.
> +- rpm-level : UFS Runtime power management leve
2
lanes per direction.
+- rpm-level: UFS Runtime power management level. Following PM
levels are supported:
+ 0 - Both UFS device and Link in active state (Highest
power consumption)
+ 1 - UFS device in active state but Link in Hi
2
lanes per direction.
+- rpm-level: UFS Runtime power management level. Following PM
levels are supported:
+ 0 - Both UFS device and Link in active state (Highest
power consumption)
+ 1 - UFS device in active state but Link in Hi
in the array is "0" then it is
> assumed
> that the frequency is set by the parent clock or a
> fixed rate clock source.
> +- rpm-level : UFS Runtime power management level. Following PM
> leve
> 2015-09-13 23:52 GMT+09:00 Yaniv Gardi :
>> UFS device and link can be put in multiple different low power modes
>> hence UFS driver supports multiple different low power modes.
>> By default UFS driver selects the default (optimal) low power mode
>> (which gives moderate
: UFS Runtime power management level. Following PM
levels are supported:
+ 0 - Both UFS device and Link in active state (Highest
power consumption)
+ 1 - UFS device in active state but Link in Hibern8
state
+ 2 - UFS
2015-09-13 23:52 GMT+09:00 Yaniv Gardi :
> UFS device and link can be put in multiple different low power modes
> hence UFS driver supports multiple different low power modes.
> By default UFS driver selects the default (optimal) low power mode
> (which gives moderate power
et by the parent clock or a
fixed rate clock source.
+- rpm-level : UFS Runtime power management level. Following PM
levels are supported:
+ 0 - Both UFS device and Link in active state (Highest
power consumption)
+ 1 - UFS device in active sta
Description:
* .suspend() and .resume() routines implemented in the driver
* aac_release_resources() initiates firmware shutdown
* aac_acquire_resources re-initializes the host interface
Changes from V2:
Increased msleep(1) to msleep(20)
Reverted pci_enable_msix_exact() to
Rajashekhara
Subject: [PATCH V6 02/10] [SCSI] aacraid: Add Power Management support
Description:
* .suspend() and .resume() routines implemented in the driver
* aac_release_resources() initiates firmware shutdown
* aac_acquire_resources re-initializes the host interface
Changes from
Subject: RE: [PATCH V6 02/10] [SCSI] aacraid: Add Power Management support
Reviewed-by: Karthikeya Sunkesula karthikeya.sunkes...@pmcs.com
-Original Message-
From: Mahesh Rajashekhara
Sent: Tuesday, August 11, 2015 11:28 AM
To: Tomas Henzl; jbottom...@parallels.com; linux-scsi
On 11.8.2015 07:58, Mahesh Rajashekhara wrote:
Description:
* .suspend() and .resume() routines implemented in the driver
* aac_release_resources() initiates firmware shutdown
* aac_acquire_resources re-initializes the host interface
Changes from V2:
Increased msleep(1)
Description:
* .suspend() and .resume() routines implemented in the driver
* aac_release_resources() initiates firmware shutdown
* aac_acquire_resources re-initializes the host interface
Changes from V2:
Increased msleep(1) to msleep(20)
Reverted pci_enable_msix_exact() to
From: Rajinikanth Pandurangan rajinikanth.panduran...@pmcs.com
Description:
* .suspend() and .resume() routines implemented in the driver
* aac_release_resources() initiates firmware shutdown
* aac_acquire_resources re-initializes the host interface
Changes from V2:
From: Rajinikanth Pandurangan rajinikanth.panduran...@pmcs.com
Description:
* .suspend() and .resume() routines implemented in the driver
* aac_release_resources() initiates firmware shutdown
* aac_acquire_resources re-initializes the host interface
Changes from V2:
From: Rajinikanth Pandurangan rajinikanth.panduran...@pmcs.com
Description:
* .suspend() and .resume() routines implemented in the driver
* aac_release_resources() initiates firmware shutdown
* aac_acquire_resources re-initializes the host interface
Changes from V2:
On 06/11/2015 03:42 AM, rajinikanth.panduran...@pmcs.com wrote:
From: Rajinikanth Pandurangan rajinikanth.panduran...@pmcs.com
Description:
* .suspend() and .resume() routines implemented in the driver
* aac_release_resources() initiates firmware shutdown
*
; Mahesh Rajashekhara; Rich Bono; Achim
Leubner; Murthy Bhat
Subject: Re: [Patch V2 2/9] [SCSI] aacraid: Add Power Management support
On 06/11/2015 03:42 AM, rajinikanth.panduran...@pmcs.com wrote:
From: Rajinikanth Pandurangan rajinikanth.panduran...@pmcs.com
Description:
* .suspend
;
linux-scsi@vger.kernel.org
Cc: aacr...@pmc-sierra.com; Harry Yang; Mahesh Rajashekhara; Rich Bono; Achim
Leubner; Murthy Bhat
Subject: Re: [Patch V2 2/9] [SCSI] aacraid: Add Power Management support
On 06/11/2015 03:42 AM, rajinikanth.panduran...@pmcs.com wrote:
From: Rajinikanth Pandurangan
Leubner; Murthy Bhat; Rajinikanth Pandurangan
Subject: [Patch V2 2/9] [SCSI] aacraid: Add Power Management support
From: Rajinikanth Pandurangan rajinikanth.panduran...@pmcs.com
Description:
* .suspend() and .resume() routines implemented in the driver
* aac_release_resources
From: Rajinikanth Pandurangan rajinikanth.panduran...@pmcs.com
Description:
* .suspend() and .resume() routines implemented in the driver
* aac_release_resources() initiates firmware shutdown
* aac_acquire_resources re-initializes the host interface
Signed-off-by:
On Wed, 2015-05-13 at 17:12 -0700, rajinikanth.panduran...@pmcs.com
wrote:
diff --git a/drivers/scsi/aacraid/linit.c b/drivers/scsi/aacraid/linit.c
index 9eec027..be30e43 100644
--- a/drivers/scsi/aacraid/linit.c
+++ b/drivers/scsi/aacraid/linit.c
@@ -1317,6 +1317,149 @@ static int
] aacraid: Add Power Management support
On Wed, 2015-05-13 at 17:12 -0700, rajinikanth.panduran...@pmcs.com
wrote:
diff --git a/drivers/scsi/aacraid/linit.c
b/drivers/scsi/aacraid/linit.c index 9eec027..be30e43 100644
--- a/drivers/scsi/aacraid/linit.c
+++ b/drivers/scsi/aacraid/linit.c
; Rich
Bono; Achim Leubner; Murthy Bhat
Subject: Re: [PATCH 2/9] [SCSI] aacraid: Add Power Management support
On Wed, 2015-05-13 at 17:12 -0700, rajinikanth.panduran...@pmcs.com
wrote:
diff --git a/drivers/scsi/aacraid/linit.c
b/drivers/scsi/aacraid/linit.c index 9eec027..be30e43 100644
On 05/14/2015 02:12 AM, rajinikanth.panduran...@pmcs.com wrote:
From: Rajinikanth Pandurangan rajinikanth.panduran...@pmcs.com
Description:
* .suspend() and .resume() routines implemented in the driver
* aac_release_resources() initiates firmware shutdown
*
On 05/14/2015 02:12 AM, rajinikanth.panduran...@pmcs.com wrote:
From: Rajinikanth Pandurangan rajinikanth.panduran...@pmcs.com
Description:
* .suspend() and .resume() routines implemented in the driver
* aac_release_resources() initiates firmware shutdown
*
Message-
From: Dan Carpenter [mailto:dan.carpen...@oracle.com]
Sent: Thursday, October 02, 2014 6:31 PM
To: subha...@codeaurora.org
Cc: linux-scsi@vger.kernel.org
Subject: re: ufs: add UFS power management support
Hello Subhash Jadavani,
The patch 57d104c153d3: ufs: add UFS power management
On Thu, Oct 23, 2014 at 10:28:52AM +0300, Dolev Raviv wrote:
Hi Dan,
This seem like a false alarm, please let me know if it requires a fix.
It may not indicate a bug, but it is correct in that the code could be
re-written:
Old:
else if ((req_link_state == UIC_LINK_OFF_STATE)
Hello Subhash Jadavani,
The patch 57d104c153d3: ufs: add UFS power management support from
Sep 25, 2014, leads to the following static checker warning:
drivers/scsi/ufs/ufshcd.c:4746 ufshcd_link_state_transition()
warn: we tested 'check_for_bkops' before and it was 'true
I've had the series in a ufs-for-3.18 branch for a while, and the two
issues pointed out by the buildbot were quickly fixed. Unless I get
a loud complaint I will merge the entire series including the two core
patches into drivers-for-3.18 tomorrow.
--
To unsubscribe from this list: send the line
Thanks Mita,
You are right these are careless mistakes.
I will fix all of them and upload a new version shortly.
__ufshcd_send_uic_cmd() is called with host_lock held here, but
host_lock is acquired again in __ufshcd_send_uic_cmd(). So it causes
recursive deadlock.
Correct I forgot to
This patch seies introduces support for power management in the driver as well
as vendor specific initialization - registers, clocks, voltage regulators etc.
It includes also a rework for the init sequence and other PM pre-requisite such
as write protection support, handling well-known LUN
From: Subhash Jadavani subha...@codeaurora.org
This patch adds support for UFS device and UniPro link power management
during runtime/system PM.
Main idea is to define multiple UFS low power levels based on UFS device
and UFS link power states. This would allow any specific platform or pci
Please stop putting listname-owner (in this case linux-scsi-owner)
in the CC: list, that goes to me not the list.
--
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to majord...@vger.kernel.org
More majordomo info at
From: Subhash Jadavani subha...@codeaurora.org
This patch adds support for UFS device and UniPro link power management
during runtime/system PM.
Main idea is to define multiple UFS low power levels based on UFS device
and UFS link power states. This would allow any specific platform or pci
This patch seies introduces support for power management in the driver as well
as vendor specific initialization - registers, clocks, voltage regulators etc.
It includes also a rework for the init sequence and other PM pre-requisite such
as write protection support, handling well-known LUN
2014-09-25 0:14 GMT+09:00 Dolev Raviv dra...@codeaurora.org:
+int ufshcd_uic_pwr_ctrl(struct ufs_hba *hba, struct uic_command *cmd)
{
- struct uic_command uic_cmd = {0};
- struct completion pwr_done;
+ struct completion uic_async_done;
unsigned long flags;
This patch seies introduces support for power management in the driver as well
as vendor specific initialization - registers, clocks, voltage regulators etc.
It includes also a rework for the init sequence and other PM pre-requisite such
as write protection support, handling well-known LUN
From: Subhash Jadavani subha...@codeaurora.org
This patch adds support for UFS device and UniPro link power management
during runtime/system PM.
Main idea is to define multiple UFS low power levels based on UFS device
and UFS link power states. This would allow any specific platform or pci
Just from a quick glance this is missing the wlun type fixup we recently
talked about, do you plan to send this as a separate series?
Also I've already merged the first patch, in case the new one differs
from the merged one in any way (doesn't seem so), please send an
incremental diff for it.
--
);
+
+ /*
+ * For selecting the UFS device power mode (Active / UFS_Sleep /
+ * UFS_PowerDown), SCSI power management command (START STOP UNIT)
+ * needs to be sent to a UFS device Well known Logical Unit (W-LU).
+ * As this command would be sent during the UFS host controller
);
+
+/*
+ * For selecting the UFS device power mode (Active / UFS_Sleep /
+ * UFS_PowerDown), SCSI power management command (START STOP UNIT)
+ * needs to be sent to a UFS device Well known Logical Unit (W-LU).
+ * As this command would be sent during the UFS host controller
+ * runtime
previous mail (in response to [9/17] patch comments),
UFS driver power management is controlled via device W-LUN during the
suspend process.
As documented in the comment above:
* For selecting the UFS device power mode (Active / UFS_Sleep /
* UFS_PowerDown), SCSI power management command (START
...@codeaurora.org
This patch adds support for UFS device and UniPro link power management
during runtime/system PM.
snip
+vccq_lpm:
+ufshcd_config_vreg_lpm(hba, hba-vreg_info.vccq);
+vcc_disable:
+ufshcd_toggle_vreg(hba-dev, hba-vreg_info.vcc, false);
+out:
+return ret;
+}
+
+static
Hi Dolev,
On Wednesday 10 September 2014 05:24 PM, Dolev Raviv wrote:
From: Subhash Jadavani subha...@codeaurora.org
This patch adds support for UFS device and UniPro link power management
during runtime/system PM.
snip
+vccq_lpm:
+ ufshcd_config_vreg_lpm(hba, hba-vreg_info.vccq
2014-09-10 20:54 GMT+09:00 Dolev Raviv dra...@codeaurora.org:
+static int ufshcd_config_vreg_load(struct device *dev, struct ufs_vreg *vreg,
+ int ua)
+{
+ int ret = 0;
+ struct regulator *reg = vreg-reg;
+ const char *name = vreg-name;
+
2014-09-10 20:54 GMT+09:00 Dolev Raviv dra...@codeaurora.org:
+static inline void ufshcd_enable_irq(struct ufs_hba *hba)
+{
+ if (!hba-is_irq_enabled) {
+ enable_irq(hba-irq);
+ hba-is_irq_enabled = true;
+ }
+}
+
+static inline void
This patch seies introduces support for power management in the driver as well
as vendor specific initialization - registers, clocks, voltage regulators etc.
It includes also a rework for the init sequence and other PM pre-requisite such
as write protection support, handling well-known LUN
From: Subhash Jadavani subha...@codeaurora.org
This patch adds support for UFS device and UniPro link power management
during runtime/system PM.
Main idea is to define multiple UFS low power levels based on UFS device
and UFS link power states. This would allow any specific platform or pci
2014-09-10 20:54 GMT+09:00 Dolev Raviv dra...@codeaurora.org:
+static inline void ufshcd_enable_irq(struct ufs_hba *hba)
+{
+ if (!hba-is_irq_enabled) {
+ enable_irq(hba-irq);
+ hba-is_irq_enabled = true;
+ }
+}
+
+static inline void
Hi all,
Thanks for reviewing the patches, I'm sorry for the late replay. I was
waiting for some comments before I address all at once and re-send the
series.
+static int ufshcd_config_vreg_load(struct device *dev, struct ufs_vreg
*vreg,
+ int ua)
+{
+int
Hi all,
Thanks for reviewing the patches, I'm sorry for the late replay. I was
waiting for some comments before I address all at once and re-send the
series.
+/**
+ * ufshcd_resume - helper function for resume operations
+ * @hba: per adapter instance
+ * @pm_op: runtime PM or system PM
; linux-scsi-ow...@vger.kernel.org;
linux-arm-...@vger.kernel.org; santos...@gmail.com; Subhash Jadavani;
Sujit Reddy Thumma
Subject: RE: [PATCH/RFC V2 10/16] scsi: ufs: add UFS power management
support
-Original Message-
From: linux-scsi-ow...@vger.kernel.org
[mailto:linux-scsi-ow
FYI: I won't read your mails until you actually make them readable
by trimming the quotes back to provide just enough context.
Consider this mail (and the one you replied to) unread.
--
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to
...@vger.kernel.org;
linux-arm-...@vger.kernel.org; santos...@gmail.com; Subhash Jadavani;
Dolev Raviv; Sujit Reddy Thumma
Subject: [PATCH/RFC V2 10/16] scsi: ufs: add UFS power management support
From: Subhash Jadavani subha...@codeaurora.org
This patch adds support for UFS device and UniPro link
From: Subhash Jadavani subha...@codeaurora.org
This patch adds support for UFS device and UniPro link power management
during runtime/system PM.
Main idea is to define multiple UFS low power levels based on UFS device
and UFS link power states. This would allow any specific platform or pci
From: Subhash Jadavani subha...@codeaurora.org
This patch adds support for UFS device and UniPro link power management
during runtime/system PM.
Main idea is to define multiple UFS low power levels based on UFS device
and UFS link power states. This would allow any specific platform or pci
On Thursday 02 August 2012 11:43:44 James Bottomley wrote:
this should be inside the switch as
default:
return -EIO;
and no return statment outside of the switch.
OK
Don't you still want to handle BUSY and QUEUE_FULL as -EBUSY? Right at
the moment they'll fall through the
BUSY and QUEUE_FULL are retryable errors.
Signed-off-by: Oliver Neukum oneu...@suse.de
---
drivers/scsi/scsi_error.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/scsi_error.c b/drivers/scsi/scsi_error.c
index 195cc75..2f70a07 100644
---
Errors happening while sd devices are going to sleep need
to interpreted for the generic layer. In particular errors
for unplugged devices and removed media must be ignored.
This hits mostly users of eSATA devices who unplug external
drives right before the system is supposed to go to sleep.
--
To
Synchronizing caches may fail. The reason for these
failures need to be translated to the generic layer
so that it nows whether to ignore a failure, retry later
or give up, aborting sleep.
Signed-off-by: Oliver Neukum oneu...@suse.de
---
drivers/scsi/scsi_error.c | 33
On Thu, 2012-08-02 at 12:27 +0200, Oliver Neukum wrote:
Synchronizing caches may fail. The reason for these
failures need to be translated to the generic layer
so that it nows whether to ignore a failure, retry later
or give up, aborting sleep.
Signed-off-by: Oliver Neukum oneu...@suse.de
the driver to free
resources and allocate resources in power management entry points and to enable
MSI interrupts for SAS controllers
Signed-off-by: Sathya Prakash [EMAIL PROTECTED]
---
diff --git a/drivers/message/fusion/mptbase.c b/drivers/message/fusion/mptbase.c
index bfda731..b3b80bf 100644
are not happening
properly with 106XE controllers, this patch modifies the driver to free
resources and allocate resources in power management entry points and to
enable
MSI interrupts for SAS controllers
I really wish you hadn't done this. Both MSI and suspend/resume are
somewhat bug inducing
Management? Should there be
a stronger connection between the two?
Link Power Management seems to be hw stuff, and I do not think much
linking is neccessary.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky
On Tue, 15 Jan 2008, Pavel Machek wrote:
Hi!
This is my first attempt at ahci autosuspend. It is _very_ hacky at
this moment, I'll seriously need to clean it up. But it seems to work
here.
How does this interact with Link Power Management? Should there be
a stronger connection between
ata_port *a
}
#ifdef CONFIG_PM
+/* This disables link power management */
static void ata_lpm_enable(struct ata_host *host)
{
struct ata_link *link;
@@ -795,6 +796,7 @@ static void ata_lpm_enable(struct ata_ho
}
}
+/* This enables link power management */
static void
Am Mittwoch, 9. Januar 2008 21:36:20 schrieb Alan Stern:
On Wed, 9 Jan 2008, Oliver Neukum wrote:
Am Mittwoch, 9. Januar 2008 18:22:51 schrieb Alan Stern:
On Wed, 9 Jan 2008, Oliver Neukum wrote:
This has an interesting implication. As the storage driver can share
a device with
On Tue, 8 Jan 2008, Pavel Machek wrote:
In fact suspend methods already do take an argument specifying the
reason they were called. It wouldn't be hard to add a couple of extra
PM_EVENT_* values for manual suspend and autosuspend. The problem is
that resume methods don't take a
Am Montag, 7. Januar 2008 20:42:23 schrieb Alan Stern:
When all the devices under a host are suspended, the LLD is informed
(via a new autosuspend method in the host template) so that it can
put the host adapter in a low-power state. Likewise, a new
autoresume method is called when the
On Wed, 9 Jan 2008, Oliver Neukum wrote:
This has an interesting implication. As the storage driver can share
a device with in principle any other usb driver, we must audit all usb
drivers if we wish to adopt this patch.
All a device's interfaces must be resumed when the storage interface
is
Am Mittwoch, 9. Januar 2008 18:22:51 schrieb Alan Stern:
On Wed, 9 Jan 2008, Oliver Neukum wrote:
This has an interesting implication. As the storage driver can share
a device with in principle any other usb driver, we must audit all usb
drivers if we wish to adopt this patch.
All a
On Wed, 9 Jan 2008, Oliver Neukum wrote:
Am Mittwoch, 9. Januar 2008 18:22:51 schrieb Alan Stern:
On Wed, 9 Jan 2008, Oliver Neukum wrote:
This has an interesting implication. As the storage driver can share
a device with in principle any other usb driver, we must audit all usb
Am Dienstag, 8. Januar 2008 04:56:03 schrieb Alan Stern:
You'll have to add this method whenever a new subsystem is affected
by power management.
Sorry, I don't understand your point. If you mean that we'll have to
add autosuspend and autoresume code to every driver that wants to
support
Am Montag, 7. Januar 2008 20:42:23 schrieb Alan Stern:
/**
+ * autoresume - perform dynamic (runtime) host resume
+ [EMAIL PROTECTED]: host to resume
+ *
+ * Resume (return to an operational power level) the specified host.
+ * Return 0 if the resume was successful, otherwise a
Am Dienstag, 8. Januar 2008 16:06:53 schrieb Alan Stern:
Eventually parts of the autosuspend mechanism will go there. But first
I thought we should have a proof-of-concept version working for at
least two different subsystems (such as SCSI and USB), so that we can
understand what should go
On Tue, 8 Jan 2008, Oliver Neukum wrote:
Am Montag, 7. Januar 2008 20:42:23 schrieb Alan Stern:
/**
+ * autoresume - perform dynamic (runtime) host resume
+ [EMAIL PROTECTED]: host to resume
+ *
+ * Resume (return to an operational power level) the specified host.
+ *
Am Dienstag, 8. Januar 2008 16:12:52 schrieb Alan Stern:
On Tue, 8 Jan 2008, Oliver Neukum wrote:
Am Montag, 7. Januar 2008 20:42:23 schrieb Alan Stern:
/**
+ * autoresume - perform dynamic (runtime) host resume
+ [EMAIL PROTECTED]: host to resume
+ *
+ * Resume
On Tue, 8 Jan 2008, Oliver Neukum wrote:
Am Montag, 7. Januar 2008 20:42:23 schrieb Alan Stern:
This patch applies to 2.6.24-rc6. Comments and suggestions are
welcome.
What about the SG_IO ioctl() ? It seems to me that you must not autosuspend
a device after that ioctl() has been used
Am Montag, 7. Januar 2008 20:42:23 schrieb Alan Stern:
This patch applies to 2.6.24-rc6. Comments and suggestions are
welcome.
What about the SG_IO ioctl() ? It seems to me that you must not autosuspend
a device after that ioctl() has been used until the file handle is closed.
On Tue, 8 Jan 2008, Oliver Neukum wrote:
Am Dienstag, 8. Januar 2008 04:56:03 schrieb Alan Stern:
You'll have to add this method whenever a new subsystem is affected
by power management.
Sorry, I don't understand your point. If you mean that we'll have to
add autosuspend
Am Dienstag, 8. Januar 2008 16:16:43 schrieb Alan Stern:
What about the SG_IO ioctl() ? It seems to me that you must not autosuspend
a device after that ioctl() has been used until the file handle is closed.
That's an open problem. The patch does block autosuspends as long as
an sg file
Alan Stern wrote:
On Tue, 8 Jan 2008, Oliver Neukum wrote:
Am Montag, 7. Januar 2008 20:42:23 schrieb Alan Stern:
/**
+ * autoresume - perform dynamic (runtime) host resume
[...]
This seems to be a bit misleading. It seems to me that you must cancel
any outstanding request to
On Tue, 8 Jan 2008, Stefan Richter wrote:
How about something more like this:
* Resume (return to an operational power level) the specified host,
* and prevent autosuspends from other software layers until the
* template autosuspend method has been called again.
* Return 0 if
When all the devices under a host are suspended, the LLD is informed
(via a new autosuspend method in the host template) so that it can
That is most certainly a mistake.
Why?
Is there a good reason to not modify
to extend suspend() to take an extra argument for the reason it
===
--- 2.6.24-rc6.orig/drivers/scsi/Kconfig
+++ 2.6.24-rc6/drivers/scsi/Kconfig
@@ -57,6 +57,18 @@ config SCSI_PROC_FS
If unsure say Y.
+config SCSI_DYNAMIC_PM
+ bool SCSI dynamic Power Management support (EXPERIMENTAL)
+ depends on SCSI PM EXPERIMENTAL
+ ---help
Am Montag, 7. Januar 2008 20:42:23 schrieb Alan Stern:
When all the devices under a host are suspended, the LLD is informed
(via a new autosuspend method in the host template) so that it can
That is most certainly a mistake. Is there a good reason to not modify
to extend suspend() to take an
On Mon, 7 Jan 2008, Oliver Neukum wrote:
Am Montag, 7. Januar 2008 20:42:23 schrieb Alan Stern:
When all the devices under a host are suspended, the LLD is informed
(via a new autosuspend method in the host template) so that it can
That is most certainly a mistake.
Why?
Is there a
That is most certainly a mistake.
Why?
You'll have to add this method whenever a new subsystem is affected
by power management. Besides what are the semantics of this method?
May suspend() be called after autosuspend() ? If not, will resume() be
called or autoresume() ?
Regards
autosuspend method in the host template) so that it can
That is most certainly a mistake.
Why?
You'll have to add this method whenever a new subsystem is affected
by power management.
Sorry, I don't understand your point. If you mean that we'll have to
add autosuspend and autoresume code
On Mon, Nov 19 2007, Alan Stern wrote:
On Mon, 19 Nov 2007, Matthew Wilcox wrote:
On Mon, Nov 19, 2007 at 10:36:19AM -0500, Alan Stern wrote:
These are conflicting requirements. How can we send the START-STOP
UNIT commands to spin the disk up/down through the request queue while
past
this filter. Is this what the REQ_PREEMPT flag is intended for?
Um, that model is pretty host centric ... we wouldn't be able to use
that for power management of shared devices like SAS/SATA devices in an
expander or FC devices. The basic problem with power management
1 - 100 of 204 matches
Mail list logo