From: Len Brown <lenb@kernel.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] ACPI: Fix acpi_pm_device_sleep_state()
Date: Sat, 12 Jan 2008 18:24:31 -0500 [thread overview]
Message-ID: <200801121824.31193.lenb@kernel.org> (raw)
In-Reply-To: <200801121236.52430.rjw@sisk.pl>
> > BTW. We currently don't use *d_min_p
> > and I can't imagine when and why we ever would,
> > so it would be fine with me if you simplify by deleting it.
>
> It was requested by someone. I can imagine that if _SxW > _SxD, a driver can
> decide which state to choose on the basis of some policy we don't know of.
I think that for the S3 and S4 states, we'll always use the deepest
state that the constraints allow while not breaking system wake.
I haven't thought much about "device wake" -- ie _PRW in S0.
Maybe some non-trivial device specific policy would be useful there
some day. Of course the device would have to know the relative latency
of the different D-states for such a policy to make a useful.
And I guess they can infer that Dx state latency on a class basis...
-Len
> > Also, the last line of this block comment can be deleted,
> > though that was true before this patch also:
>
> Not sure what you mean here ...
>
> > acpi_pci_choose_state() block comment can now be updated to delete this line:
> >
> > * currently we simply return _SxD, if present.
>
> Yes, I'll do that in a separate patch.
>
> Thanks,
> Rafael
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2008-01-12 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 23:10 [PATCH] ACPI: Fix acpi_pm_device_sleep_state() Rafael J. Wysocki
2008-01-12 4:46 ` Len Brown
2008-01-12 11:36 ` Rafael J. Wysocki
2008-01-12 23:24 ` Len Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200801121824.31193.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.