I do not currently have a VLV to test this on, but hopefully it only
removes information from debugfs, sysfs, and prevents enabling an
unsupported mode.
CC: Jesse Barnes
Signed-off-by: Ben Widawsky
---
drivers/gpu/drm/i915/i915_debugfs.c | 5 +
drivers/gpu/drm/i915/i915_sysfs.c | 3 +++
d
On Thu, Sep 13, 2012 at 04:18:41PM +0200, Daniel Vetter wrote:
> Hi Dave,
>
> The big ticket item here is the new i915 modeset infrastructure.
> Shockingly it didn't not blow up all over the place (i.e. I've managed to
> fix the ugly issues before merging). 1-2 smaller corner cases broke, but
> we
Dave Airlie recently discovered a locking bug in the fbcon layer,
where a timer_del_sync (for the blinking cursor) deadlocks with the
timer itself, since both (want to) hold the console_lock:
https://lkml.org/lkml/2012/8/21/36
Unfortunately the console_lock isn't a plain mutex and hence has no
lo
Instead of BUG_ON(in_interrupt()), since that doesn't check for all
the newfangled stuff like preempt.
Note that this is valid since the console_sem is essentially used like
a real mutex with only two twists:
- we allow trylock from hardirq context
- across suspend/resume we lock the logical conso
On Mon, Sep 17, 2012 at 02:38:14PM -0700, Jesse Barnes wrote:
> On Mon, 17 Sep 2012 22:27:21 +0200
> Daniel Vetter wrote:
>
> > This goes back to
> >
> > commit c1c7af60892070e4b82ad63bbfb95ae745056de0
> > Author: Jesse Barnes
> > Date: Thu Sep 10 15:28:03 2009 -0700
> >
> > drm/i915: fo
On Mon, 17 Sep 2012 22:27:21 +0200
Daniel Vetter wrote:
> This goes back to
>
> commit c1c7af60892070e4b82ad63bbfb95ae745056de0
> Author: Jesse Barnes
> Date: Thu Sep 10 15:28:03 2009 -0700
>
> drm/i915: force mode set at lid open time
>
> It was used to fix an issue on a i915GM based T
This goes back to
commit c1c7af60892070e4b82ad63bbfb95ae745056de0
Author: Jesse Barnes
Date: Thu Sep 10 15:28:03 2009 -0700
drm/i915: force mode set at lid open time
It was used to fix an issue on a i915GM based Thinkpad X41, which
somehow clobbered the modeset state at lid close time. Si
Hi Dave,
Essentially just flush my -fixes queue before I head off to xdc.
- gen2 regression fixer, we've enabled the lvds stuff too late. Not
causing any known issues, but this restores the sequence before a
refactor that landed in 3.5, and lvds is a fickle beast. And seriously,
who runs gen
Signed-off-by: Adam Jackson
---
drivers/gpu/drm/i915/intel_dp.c | 28 +++-
1 files changed, 27 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index 92939bd..9809c53 100644
--- a/drivers/gpu/drm/i915/intel_dp.
Signed-off-by: Adam Jackson
---
drivers/gpu/drm/i915/intel_dp.c | 25 -
1 files changed, 20 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index ace757a..92939bd 100644
--- a/drivers/gpu/drm/i915/intel_dp.c
+
Sources: DP, eDP, and DP interop specs, and a VESA slideshow about DP
1.2 for the MST bits.
Signed-off-by: Adam Jackson
---
include/drm/drm_dp_helper.h | 60 ---
1 files changed, 56 insertions(+), 4 deletions(-)
diff --git a/include/drm/drm_dp_helper.h
Signed-off-by: Adam Jackson
---
drivers/gpu/drm/drm_edid.c |3 ++-
include/drm/drm_crtc.h |1 +
2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index b7ee230..a1895ba 100644
--- a/drivers/gpu/drm/drm_edid.c
+++ b/d
Connection sense for DP bridge devices (like DP->VGA) currently only looks
at DPCD presence. This is wrong. However we would still like to avoid
DDC reads if possible, since they're much slower than AUXCH.
This series enhances i915 DP detection to know about branch devices, and
attempts to disco
On Sun, 16 Sep 2012 08:12:46 +0100
Chris Wilson wrote:
> On Sat, 15 Sep 2012 18:06:03 -0400, Dave Airlie wrote:
> > On Sat, Sep 15, 2012 at 10:41 AM, hank peng wrote:
> > > I noticed that drm_clflush_pages function will first choose clfush
> > > instead of wbinvd, its code like this:
> > >
> >
On Mon, 2012-09-17 at 11:32 +0200, Takashi Iwai wrote:
> At Mon, 17 Sep 2012 19:11:34 +1000,
> Dave Airlie wrote:
> > On Mon, Sep 17, 2012 at 6:28 PM, Takashi Iwai wrote:
> > > At Mon, 17 Sep 2012 18:21:47 +1000,
> > > Dave Airlie wrote:
> > >> On Mon, Sep 17, 2012 at 6:16 PM, Takashi Iwai wrote:
At Mon, 17 Sep 2012 19:11:34 +1000,
Dave Airlie wrote:
>
> On Mon, Sep 17, 2012 at 6:28 PM, Takashi Iwai wrote:
> > At Mon, 17 Sep 2012 18:21:47 +1000,
> > Dave Airlie wrote:
> >>
> >> On Mon, Sep 17, 2012 at 6:16 PM, Takashi Iwai wrote:
> >> > Hi Adam,
> >> >
> >> > At Fri, 14 Sep 2012 11:25:03
On Mon, Sep 17, 2012 at 6:28 PM, Takashi Iwai wrote:
> At Mon, 17 Sep 2012 18:21:47 +1000,
> Dave Airlie wrote:
>>
>> On Mon, Sep 17, 2012 at 6:16 PM, Takashi Iwai wrote:
>> > Hi Adam,
>> >
>> > At Fri, 14 Sep 2012 11:25:03 -0400,
>> > Adam Jackson wrote:
>> >>
>> >> On 9/14/12 10:19 AM, Takashi
At Mon, 17 Sep 2012 18:21:47 +1000,
Dave Airlie wrote:
>
> On Mon, Sep 17, 2012 at 6:16 PM, Takashi Iwai wrote:
> > Hi Adam,
> >
> > At Fri, 14 Sep 2012 11:25:03 -0400,
> > Adam Jackson wrote:
> >>
> >> On 9/14/12 10:19 AM, Takashi Iwai wrote:
> >> > Hi,
> >> >
> >> > we've got a machine showing
On Mon, Sep 17, 2012 at 6:16 PM, Takashi Iwai wrote:
> Hi Adam,
>
> At Fri, 14 Sep 2012 11:25:03 -0400,
> Adam Jackson wrote:
>>
>> On 9/14/12 10:19 AM, Takashi Iwai wrote:
>> > Hi,
>> >
>> > we've got a machine showing a ghost DP2 output on a docking station.
>> > The docking station has only one
Hi Adam,
At Fri, 14 Sep 2012 11:25:03 -0400,
Adam Jackson wrote:
>
> On 9/14/12 10:19 AM, Takashi Iwai wrote:
> > Hi,
> >
> > we've got a machine showing a ghost DP2 output on a docking station.
> > The docking station has only one DP port and it's connected to DP1.
> > As a result, we get an DP2
On Mon, 17 Sep 2012 09:48:24 +0200, Daniel Vetter wrote:
> On Sat, Sep 15, 2012 at 09:41:57AM +0100, Chris Wilson wrote:
> > Pin-leaks persist and we get the perennial bug reports of machine
> > lockups to the BUG_ON(pin_count==MAX). If we instead loudly report that
> > the object cannot be pinned
On Thu, Sep 13, 2012 at 08:51:22AM +0200, Takashi Iwai wrote:
> At Thu, 13 Sep 2012 11:19:00 +0800,
> Wang Xingchao wrote:
> >
> > Clear Audio Enable bit to trigger unsolicated event to notify Audio
> > Driver part the HDMI hot plug change. The patch fixed the bug when
> > remove HDMI cable the bi
On Sat, Sep 15, 2012 at 09:41:57AM +0100, Chris Wilson wrote:
> Pin-leaks persist and we get the perennial bug reports of machine
> lockups to the BUG_ON(pin_count==MAX). If we instead loudly report that
> the object cannot be pinned at that time it should prevent the driver from
> locking up, and
23 matches
Mail list logo
