Jani, all,
On a Lenovo X1 Carbon if the display is off when suspend is entered
it will be off when it is resumed. A key must be pressed to restore
normal brightness.
xset dpms force off
sleep 1
sudo systemctl suspend
(resume)
(screen off, press any key)
The behavior I am accustomed to
Implements a required workaround whose implications aren't entirely clear to me
from the description. In particular I do not know if this effects legacy
contexts, execlists, or both.
I couldn't find a real workaround name, so I made up:
WaHdcCtxNonCoherent
Signed-off-by: Ben Widawsky
---
driver
We know certain future platforms need things. Don't let them go unnoticed as
they did for SKL by adding an error message and falling back to the possibly
more conservative SKL values.
Signed-off-by: Ben Widawsky
---
drivers/gpu/drm/i915/intel_ringbuffer.c | 4
1 file changed, 4 insertions(+
Cc: Kristian Høgsberg
Signed-off-by: Ben Widawsky
---
drivers/gpu/drm/i915/intel_ringbuffer.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c
b/drivers/gpu/drm/i915/intel_ringbuffer.c
index 62318a4..b8a445b 100644
--- a/drivers/gpu/drm
Cc: Kristian Høgsberg
Signed-off-by: Ben Widawsky
---
drivers/gpu/drm/i915/intel_ringbuffer.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c
b/drivers/gpu/drm/i915/intel_ringbuffer.c
index b8a445b..e14748d 100644
--- a/drivers/gpu/drm/i915/intel_
Hi Maintainers,
Any comments?
Regards,
Libin
> -Original Message-
> From: Yang, Libin
> Sent: Wednesday, January 07, 2015 12:56 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Yang, Libin; Lin, Mengdong
> Subject: [PATCH] intel_audio_dump: add support for Cherryview
>
> From: Libin Yang
On 2014.12.18 12:12:33 -0600, jeff.mc...@intel.com wrote:
> diff --git a/include/drm/i915_drm.h b/include/drm/i915_drm.h
> index 15dd01d..be38adf 100644
> --- a/include/drm/i915_drm.h
> +++ b/include/drm/i915_drm.h
> @@ -340,6 +340,10 @@ typedef struct drm_i915_irq_wait {
> #define I915_PARAM_HAS_
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/intel_runtime_pm.c between commit 7f1241ed1a06
("drm/i915: Kill check_power_well() calls") from the drm-intel-fixes
tree and commit e2c719b75c8c ("drm/i915: tame the chattermouth (v2)")
from the drm-intel
Tested-By: PRC QA PRTS (Patch Regression Test System Contact:
shuang...@intel.com)
-Summary-
Platform Delta drm-intel-nightly Series Applied
PNV -32 363/364
This is v4 of [1] addressing the review comments from Takashi and Jani.
[1]
http://lists.freedesktop.org/archives/intel-gfx/2014-December/056992.html
Imre Deak (6):
drm/i915: add dev_to_i915 helper
drm/i915: add component support
ALSA: hda: export struct hda_intel
ALSA: hda: pass intel_hd
This struct will be needed by the component code added in an upcoming
patch, so export it into a new hda_intel.h file. At the same time also
merge hda_i915.h into this new header, there is no reason to keep two
separate intel specific header file.
Suggested-by: Takashi Iwai
Signed-off-by: Imre De
This will be needed by later patches, so factor it out.
No functional change.
v2:
- s/dev_to_i915_priv/dev_to_i915/ (Jani)
- don't use the helper in i915_pm_suspend (Chris)
- simplify the helper (Chris)
v3:
- remove redundant upcasting in the helper (Daniel)
Signed-off-by: Imre Deak
Reviewed-by
After switching to using the component interface this API isn't needed
any more.
v2-3: unchanged
v4:
- move the removal of i915_powerwell.h to this patch (Takashi)
Signed-off-by: Imre Deak
Reviewed-by: Takashi Iwai
---
drivers/gpu/drm/i915/intel_runtime_pm.c | 56 --
chip is already passed to most of the i915 interface functions. Unify
the interface by passing intel_hda instead of chip and passing it to all
functions. Passing intel_hda instead of chip makes more sense since this
is an intel specific interface. Also in an upcoming patch we will use
intel_hda in
Register a component master to be used to interface with the i915
driver. This is meant to replace the current interface which is based on
module symbol lookups.
Note that currently we keep the existing behavior and pin the i915
module while the hda driver is loaded. Using the component interface
Register a component to be used to interface with the snd_hda_intel
driver. This is meant to replace the same interface that is currently
based on module symbol lookup.
v2:
- change roles between the hda and i915 components (Daniel)
- add the implementation to a new file (Jani)
- use better namesp
At Wed, 07 Jan 2015 21:49:46 +0200,
Imre Deak wrote:
>
> On Tue, 2015-01-06 at 11:25 +0100, Takashi Iwai wrote:
> > At Mon, 05 Jan 2015 19:25:09 +0200,
> > Imre Deak wrote:
> > >
> > > On Mon, 2015-01-05 at 16:35 +0100, Takashi Iwai wrote:
> > > > At Mon, 05 Jan 2015 17:29:34 +0200,
> > > > Imre
From: Tim Gore
A recent change to igt_kms.c reqires HAVE_LINUX_KD_H to be set
in order to pick up the kd.h header file.
Signed-off-by: Tim Gore
---
lib/Android.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/Android.mk b/lib/Android.mk
index 548bca4..2251c15 100644
-
i915_gem_validate_context() will check the engine->state to see if it can
submit into a ringbuffer. But when we are releasing the context we leave the
engine state to a non null value. Thus after a successful hang recovery
we might mistakenly submit to a non initialized ringbuffer resulting in:
[
Hello Daniel and the other maintainers,
I'm having some weird trouble while working on my small project.
For some reason, there is a chance that forcewake is not properly set, when
I'm reading some registers.
In that case, when values from registers (e.g., ring head, xxIMRs, .) are
sometimes 0 (
On Wed, Jan 07, 2015 at 05:32:39PM +, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> If not pinned VMA can become an eviction target just before it needs to be
> executed which breaks the internal object lifetime rules.
>
> Signed-off-by: Tvrtko Ursulin
> Bugzilla: https://bugs.freedeskto
On Wed, Jan 07, 2015 at 04:09:30PM +, Thomas Daniel wrote:
> During a suspend/resume cycle the hardware Context Status Buffer write pointer
> is reset. However since recent changes to the init sequence the software CSB
> read pointer is no longer reset. This means that context status events a
22 matches
Mail list logo