On Sun, 2013-01-27 at 16:45 +0100, Daniel Vetter wrote:
> On Sun, Jan 27, 2013 at 4:21 PM, Zhang Rui wrote:
> > i915 driver needs to do modeset when
> > 1. system resumes from sleep
> > 2. lid is opened
> >
> > In PM_SUSPEND_MEM state, all the GPEs are cleared when system resumes,
> > thus it is t
On Mon, Jan 28, 2013 at 1:16 AM, Sedat Dilek wrote:
> On Mon, Jan 28, 2013 at 12:52 AM, Sedat Dilek wrote:
>> Hi,
>>
>> From [1]:
>> ...
>> static struct intel_quirk intel_quirks[] = {
>> /* HP Mini needs pipe A force quirk (LP: #322104) */
>> { 0x27ae, 0x103c, 0x361a, quirk_pipea
On Mon, Jan 28, 2013 at 12:52 AM, Sedat Dilek wrote:
> Hi,
>
> From [1]:
> ...
> static struct intel_quirk intel_quirks[] = {
> /* HP Mini needs pipe A force quirk (LP: #322104) */
> { 0x27ae, 0x103c, 0x361a, quirk_pipea_force },
> ...
> }
>
> Triple - which value is what?
>
> 00:0
Hi,
>From [1]:
...
static struct intel_quirk intel_quirks[] = {
/* HP Mini needs pipe A force quirk (LP: #322104) */
{ 0x27ae, 0x103c, 0x361a, quirk_pipea_force },
...
}
Triple - which value is what?
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd
Generation Core
On Fri, Jan 25, 2013 at 04:59:14PM -0200, Paulo Zanoni wrote:
> From: Paulo Zanoni
>
> If the power well is disabled, we should not try to read its
> registers, otherwise we'll get "unclaimed register" messages.
>
> V2: Don't check whether the power well is enabled or not, just check
> whether w
On Sun, Jan 27, 2013 at 11:21 PM, Rafael J. Wysocki wrote:
>> Given that this essentially requires users to manually set this module
>> option to make stuff work I don't like this.
>>
>> I see a few possible options:
>> - plug the races between all the different parts - I've never really
>> unders
On Sunday, January 27, 2013 04:45:51 PM Daniel Vetter wrote:
> On Sun, Jan 27, 2013 at 4:21 PM, Zhang Rui wrote:
> > i915 driver needs to do modeset when
> > 1. system resumes from sleep
> > 2. lid is opened
> >
> > In PM_SUSPEND_MEM state, all the GPEs are cleared when system resumes,
> > thus it
On Sun, Jan 27, 2013 at 4:21 PM, Zhang Rui wrote:
> i915 driver needs to do modeset when
> 1. system resumes from sleep
> 2. lid is opened
>
> In PM_SUSPEND_MEM state, all the GPEs are cleared when system resumes,
> thus it is the i915_resume code does the modeset rather than
> intel_lid_notify()
i915 driver needs to do modeset when
1. system resumes from sleep
2. lid is opened
In PM_SUSPEND_MEM state, all the GPEs are cleared when system resumes,
thus it is the i915_resume code does the modeset rather than intel_lid_notify().
In PM_SUSPEND_FREEZE state, system is still resposive to the l
Enable ACPI SCI during suspend so that SCI can be used
as wake events for PM_SUSPEND_FREEZE.
For S3/S4 transition,
We disable all GPEs in suspend_ops->prepare_late() to
fix a problem that GPEs may trigger SCI before
arch_suspend_disable_irqs() is run.
So it is safe to leave the SCI enabled until
PM_SUSPEND_FREEZE state is a general state that
does not need any platform specific support, it equals
frozen processes + suspended devices + idle processors.
Compared with PM_SUSPEND_MEMORY,
PM_SUSPEND_FREEZE saves less power
because the system is still in a running state.
PM_SUSPEND_FREEZE has l
11 matches
Mail list logo
