Some Poulsbo cards seem to incorrectly report
SDVO_CMD_STATUS_TARGET_NOT_SPECIFIED instead of SDVO_CMD_STATUS_PENDING, which
causes the display to be turned off.
Signed-off-by: Guillaume Clement
---
drivers/gpu/drm/gma500/psb_intel_sdvo.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
On Fri, Aug 09, 2013 at 10:12:15PM -0700, Ben Widawsky wrote:
> The conditional is usually a recoverable driver bug, and so WARNing, and
> preventing the drm_mm code from doing potential damage (BUG) is
> desirable.
>
> This issue was hit and fixed twice while developing the i915 multiple
> addres
https://bugs.freedesktop.org/show_bug.cgi?id=67888
--- Comment #2 from fossphr...@gmail.com ---
Yes, I do.
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists
On Sat, Aug 10, 2013 at 9:06 AM, Guillaume Clement wrote:
> Some Poulsbo cards seem to incorrectly report
> SDVO_CMD_STATUS_TARGET_NOT_SPECIFIED instead of SDVO_CMD_STATUS_PENDING,
> which causes the display to be turned off.
>
> Signed-off-by: Guillaume Clement
Can you please submit the exac
On Sat, Aug 10, 2013 at 10:55:08AM +0200, Daniel Vetter wrote:
> On Sat, Aug 10, 2013 at 9:06 AM, Guillaume Clement
> wrote:
> > Some Poulsbo cards seem to incorrectly report
> > SDVO_CMD_STATUS_TARGET_NOT_SPECIFIED instead of SDVO_CMD_STATUS_PENDING,
> > which causes the display to be turned o
On Sat, Aug 10, 2013 at 11:19 AM, Chris Wilson wrote:
> On Sat, Aug 10, 2013 at 10:55:08AM +0200, Daniel Vetter wrote:
>> On Sat, Aug 10, 2013 at 9:06 AM, Guillaume Clement
>> wrote:
>> > Some Poulsbo cards seem to incorrectly report
>> > SDVO_CMD_STATUS_TARGET_NOT_SPECIFIED instead of SDVO_CMD
On Fri, Aug 9, 2013 at 1:31 PM, Tom Cooksey wrote:
>> > > So in the above, after X receives the second DRI2SwapBuffers, it
>> > > doesn't need to get scheduled again for the next frame to be both
>> > > rendered by the GPU and issued to the display for scanout.
>> >
>> > well, this is really only
https://bugs.freedesktop.org/show_bug.cgi?id=67982
Priority: medium
Bug ID: 67982
Assignee: dri-devel@lists.freedesktop.org
Summary: After boot, the APU is powered with its maximum
voltage (trinity/ARUBA)
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=67982
--- Comment #1 from Kertesz Laszlo ---
Created attachment 83927
--> https://bugs.freedesktop.org/attachment.cgi?id=83927&action=edit
lspci
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #90 from Sergey ---
> Does disabling clockgating avoid the hangs?
No. Behaves the same. Today it was ~40% of hangs after shutdown.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #91 from Hrvoje Senjan ---
(In reply to comment #87)
> (In reply to comment #86)
> > Ingoring suspend/hibernate, is anyone getting hangs or gpu resets with dpm
> > enabled under normal operation? If so, can you try disabling clockgat
Hi Sachin,
> -Original Message-
> From: Sachin Kamat [mailto:sachin.ka...@linaro.org]
> Sent: Friday, August 09, 2013 6:40 PM
> To: Chanho Park
> Cc: inki@samsung.com; kgene@samsung.com; dri-
> de...@lists.freedesktop.org; kyungmin.p...@samsung.com;
> mark.rutl...@arm.com; l.st...@
This patchset includes device tree support for rotator of exynos4210/4x12/5250.
Unfortunately, each of them has slightly different limitations of image size.
The rotator can support several image formats(RGB888/555, YCbCr422/420_2/3p).
For convinience, however, exynos drm rotator driver only suppor
Hi Sachin,
> -Original Message-
> From: Sachin Kamat [mailto:sachin.ka...@linaro.org]
> Sent: Friday, August 09, 2013 6:49 PM
> To: Chanho Park
> Cc: inki@samsung.com; kgene@samsung.com; dri-
> de...@lists.freedesktop.org; kyungmin.p...@samsung.com;
> mark.rutl...@arm.com; l.st...@
The exynos4 platform is only dt-based since 3.10, we should convert driver data
and ids to dt-based parsing methods. The rotator driver has a limit table to get
size limit of input picture. Each SoCs has slightly different limit value
compared with any others.
For example, exynos4210's max_size of
This patch adds a rotator node for exynos4210. The exynos4210 has different
limitation of image size compared with later chips.
Signed-off-by: Chanho Park
Cc: Thomas Abraham
Cc: Kukjin Kim
Cc: Inki Dae
Signed-off-by: Kyungmin Park
---
arch/arm/boot/dts/exynos4.dtsi |9 +
1 file c
This patch adds a rotator node for exynos4212 and 4412. These have different
limitation of image size compared with the exynos4210. So, we should define
new compatible to distinguish it from the exynos4210.
Signed-off-by: Chanho Park
Cc: Thomas Abraham
Cc: Kukjin Kim
Cc: Inki Dae
Signed-off-by
This patch adds a rotator node for exynos5250. It has different align value of
image size compared with any other chips. So, we should define new compatible
for the exynos5250.
Signed-off-by: Chanho Park
Cc: Thomas Abraham
Cc: Kukjin Kim
Cc: Inki Dae
Signed-off-by: Kyungmin Park
---
arch/arm
Hi Chanho,
On 9 August 2013 13:10, Chanho Park wrote:
> This patch describes each nodes of rotator and specifies a example how to bind
> it.
>
> Signed-off-by: Chanho Park
> Cc: Thomas Abraham
> Cc: Kukjin Kim
> Cc: Inki Dae
> Signed-off-by: Kyungmin Park
> ---
> .../devicetree/bindings/gpu
This patch describes each nodes of rotator and specifies a example how to bind
it.
Signed-off-by: Chanho Park
Cc: Thomas Abraham
Cc: Kukjin Kim
Cc: Inki Dae
Signed-off-by: Kyungmin Park
---
.../devicetree/bindings/gpu/samsung-rotator.txt| 26
1 file changed, 26 ins
Hi Chanho,
On 9 August 2013 13:10, Chanho Park wrote:
> The exynos4 platform is only dt-based since 3.10, we should convert driver
> data
> and ids to dt-based parsing methods. The rotator driver has a limit table to
> get
> size limit of input picture. Each SoCs has slightly different limit va
And sorry for off-topic email, but I can't resist.
Can't we finally kill block_all_signals() and ->notifier ? This
is very, very wrong and doesn't work anyway.
I tried to ask many, many times. Starting from 2007 at least.
And every time the discussion "hangs". I am quoting the last
email I sent b
The DISPLAY_ prefix will clash with the Common Display Framework, rename
it.
Signed-off-by: Laurent Pinchart
---
drivers/video/omap2/displays-new/Kconfig | 24
drivers/video/omap2/displays-new/Makefile | 24
2 files changed, 24 insertions(+), 24
Hi everybody,
Here's the third RFC of the Common Display Framework.
I won't repeat all the background information from the versions one and two
here, you can read it at http://lwn.net/Articles/512363/ and
http://lwn.net/Articles/526965/.
This RFC isn't final. Given the high interest in CDF and t
The Common Display Framework (CDF) splits display devices in entities
that interact through an abstract API. Each entity is managed by its own
driver independently of the other entities, with the framework
orchestrating interactions.
This commit introduces the CDF core with entity (un)registration
The video and stream control operations handle video stream management,
both from the control point of view (called in response to userspace
requests) and the video stream point of view (called by entities to
control the video stream they receive on their input(s)).
Signed-off-by: Laurent Pinchart
Display entities are initialized by they respective drivers
asynchronously with the master display driver. The notifier
infrastructure allows display drivers to create a list of entities they
need (based on platform data) and be notified when those entities are
added to or removed from the system.
Add two graph helper functions. display_entity_build_notifier() builds
an entity notifier from an entities graph represented as a flat array,
typically passed from platform data. display_entity_link_graph() can
then be used to create media controller links between all entities in
the graph.
Signed
Extend the notifier with DT node matching support, and add helper functions to
build the notifier and link entities based on a graph representation in
DT.
Signed-off-by: Laurent Pinchart
---
drivers/video/display/display-core.c | 334 +++
drivers/video/display/dis
Pixel codings describe how pixels are transmitted on a physical bus. The
information can be communicated between drivers to configure devices.
Signed-off-by: Laurent Pinchart
---
include/video/display.h | 120
1 file changed, 120 insertions(+)
di
MIPI DBI is a configurable-width parallel display bus that transmits
commands and data.
Add a new DBI Linux bus type that implements the usual bus
infrastructure (including devices and drivers (un)registration and
matching, and bus configuration and access functions).
Signed-off-by: Laurent Pinch
The Display Pixel Interface is a configurable-width video-only
unidirectional parallel bus standard that defines video formats and
signaling for panel devices.
This driver implements support for simple DPI panels with no runtime
configuration capabilities (GPIOs- and/or regulators-based control ca
The R61505 is a SYS-80 bus panel controller from Renesas.
Signed-off-by: Laurent Pinchart
---
drivers/video/display/Kconfig| 10 +
drivers/video/display/Makefile | 1 +
drivers/video/display/panel-r61505.c | 567 +++
include/video/panel-r61505.h
The R61517 is a MIPI DBI panel controller from Renesas.
Signed-off-by: Laurent Pinchart
---
drivers/video/display/Kconfig| 10 +
drivers/video/display/Makefile | 1 +
drivers/video/display/panel-r61517.c | 460 +++
include/video/panel-r61517.h
This driver implements support for VGA Digital to Analog Converters
(DACs) that receive pixel data through a DPI interface and have no
control interface (GPIOs- and/or regulators-based control can be
implemented later when needed). It exposes the devices a display
entities.
Signed-off-by: Laurent
Signed-off-by: Laurent Pinchart
---
arch/arm/mach-shmobile/clock-r8a7790.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/mach-shmobile/clock-r8a7790.c
b/arch/arm/mach-shmobile/clock-r8a7790.c
index d99b87b..7229f96 100644
--- a/arch/arm/mach-shmobile/clock-r8a7790.c
+++ b/arc
This driver exposes VGA connectors as display entity devices. The
connectors are passive devices that pass analog VGA signals though. They
optionally cary DDC signals for bidirectional control communications
with the devices connected to the connectors.
EDID retrieval isn't supported yet.
Signed-
Signed-off-by: Laurent Pinchart
---
arch/arm/boot/dts/r8a7790.dtsi | 33 +
1 file changed, 33 insertions(+)
diff --git a/arch/arm/boot/dts/r8a7790.dtsi b/arch/arm/boot/dts/r8a7790.dtsi
index ab0582c..b63f1a6 100644
--- a/arch/arm/boot/dts/r8a7790.dtsi
+++ b/arch/a
Signed-off-by: Laurent Pinchart
---
arch/arm/mach-shmobile/board-marzen.c | 77 ---
1 file changed, 53 insertions(+), 24 deletions(-)
diff --git a/arch/arm/mach-shmobile/board-marzen.c
b/arch/arm/mach-shmobile/board-marzen.c
index 6499f1a..be1b7cb 100644
--- a/ar
Signed-off-by: Laurent Pinchart
---
arch/arm/mach-shmobile/board-lager.c | 76 +---
1 file changed, 53 insertions(+), 23 deletions(-)
diff --git a/arch/arm/mach-shmobile/board-lager.c
b/arch/arm/mach-shmobile/board-lager.c
index 75a01bc..d61b892 100644
--- a/arch
Signed-off-by: Laurent Pinchart
---
arch/arm/boot/dts/r8a7790-lager-reference.dts | 92 +++
1 file changed, 92 insertions(+)
diff --git a/arch/arm/boot/dts/r8a7790-lager-reference.dts
b/arch/arm/boot/dts/r8a7790-lager-reference.dts
index d9a25d5..ba2469b 100644
--- a/arc
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/rcar-du/Kconfig | 3 +-
drivers/gpu/drm/rcar-du/Makefile| 7 +-
drivers/gpu/drm/rcar-du/rcar_du_connector.c | 164
drivers/gpu/drm/rcar-du/rcar_du_connector.h | 36
drivers/gpu/drm/rcar-du/rcar_
On Fri, Aug 9, 2013 at 11:36 AM, Daniel Vetter wrote:
> On Fri, Aug 9, 2013 at 8:12 PM, Andy Lutomirski wrote:
>> On Thu, Aug 8, 2013 at 6:41 AM, Daniel Vetter wrote:
>>> The new arch_phys_wc_add/del functions do the right thing both with
>>> and without MTRR support in the kernel. So we can dro
On Thu, Aug 8, 2013 at 6:41 AM, Daniel Vetter wrote:
> The new arch_phys_wc_add/del functions do the right thing both with
> and without MTRR support in the kernel. So we can drop these
> additional checks.
If any of the new arch_phys_wc_add calls are reachable and if the
driver calls arch_phys_w
On Fri, Aug 9, 2013 at 11:47 AM, Daniel Vetter wrote:
> On Fri, Aug 9, 2013 at 8:39 PM, Andy Lutomirski wrote:
>> On Fri, Aug 9, 2013 at 11:36 AM, Daniel Vetter
>> wrote:
>>> On Fri, Aug 9, 2013 at 8:12 PM, Andy Lutomirski wrote:
On Thu, Aug 8, 2013 at 6:41 AM, Daniel Vetter
wrote:
9107e9d227e3b0893829baee4ac59feb874d4c23 introduced "score", and while
it's actually not possible for it to be uninitialized (given the
return values of ring_stuck()), the warning should be suppressed. It
probably just needs a "default:" added to the switch statement.
drivers/gpu/drm/i915/i915_irq
The conditional is usually a recoverable driver bug, and so WARNing, and
preventing the drm_mm code from doing potential damage (BUG) is
desirable.
This issue was hit and fixed twice while developing the i915 multiple
address space code. The first fix is the patch just before this, and is
hit on a
> >> Can you please submit the exact same change for drm/i915/intel_sdvoc.c
> >> too? The sdvo encoders can be the same ones for psb and i915 so having
> >> the same code would be great. Separate patch for drm/i915 ofc.
> >
> > Are you absolutely sure that is a hardware error and not a software SDV
Some Poulsbo cards seem to incorrectly report
SDVO_CMD_STATUS_TARGET_NOT_SPECIFIED instead of SDVO_CMD_STATUS_PENDING, which
causes the display to be turned off.
This could also happen to i915.
Signed-off-by: Guillaume Clement
---
drivers/gpu/drm/i915/intel_sdvo.c | 3 ++-
1 file changed, 2 i
On Sat, Aug 10, 2013 at 9:40 PM, Guillaume CLÉMENT wrote:
>> >> Can you please submit the exact same change for drm/i915/intel_sdvoc.c
>> >> too? The sdvo encoders can be the same ones for psb and i915 so having
>> >> the same code would be great. Separate patch for drm/i915 ofc.
>> >
>> > Are you
https://bugs.freedesktop.org/show_bug.cgi?id=67927
--- Comment #5 from Dieter Nützel ---
Excellent Vadim!
It fix it and apparently ./objview GreatLakesBiplaneHP.obj, too.
Should we close it, now?
Thank you very much.
-Dieter
--
You are receiving this mail because:
You are the assignee for th
Hi folks !
So I've been trying to figure out what it would take to make
nouveau work properly on architectures where PAGE_SIZE isn't
4k such as most ppc64's. An initial patch from Dave fixed a
bogon in nv41.c nv41_vm_map_sg() which was trying to handle
the case at that low level, but this isn't en
On Sun, 2013-08-11 at 10:41 +1000, Benjamin Herrenschmidt wrote:
> Now, to do that, I need a better understanding of the various things
> in there since I'm not familiar with nouveau at all. What I think I've
> figured out is with a few questions, it would be awesome if you could
> answer them so I
Op 11-08-13 07:36, Benjamin Herrenschmidt schreef:
> On Sun, 2013-08-11 at 10:41 +1000, Benjamin Herrenschmidt wrote:
>> Now, to do that, I need a better understanding of the various things
>> in there since I'm not familiar with nouveau at all. What I think I've
>> figured out is with a few questi
https://bugs.freedesktop.org/show_bug.cgi?id=67888
--- Comment #3 from fossphr...@gmail.com ---
It doesn't seem to be clear in the dmesg output - I am using the vanilla Linux
3.11-rc2 kernel. I can recompile the kernel with extra debugging options turned
on if required.
Do you need any other info
On Thu, Aug 8, 2013 at 11:39 AM, Simon Horman wrote:
> On Thu, Aug 08, 2013 at 03:34:17AM +0200, Laurent Pinchart wrote:
>> Hi Dave,
>>
>> (CC'ing Simon Horman, the shmobile tree maintainer)
>>
>> On Thursday 08 August 2013 10:57:33 Dave Airlie wrote:
>> > On Thu, Aug 8, 2013 at 10:43 AM, Laurent
On Sat, Aug 10, 2013 at 7:25 AM, Laurent Pinchart
wrote:
> Hi Dave,
>
> On Saturday 10 August 2013 06:45:05 Dave Airlie wrote:
>> On Thu, Aug 8, 2013 at 11:39 AM, Simon Horman wrote:
>> > On Thu, Aug 08, 2013 at 03:34:17AM +0200, Laurent Pinchart wrote:
>> >> Hi Dave,
>> >>
>> >> (CC'ing Simon Ho
Hi everybody,
Here's the third RFC of the Common Display Framework. This is a resent, the
series I've sent earlier seems not to have made it to the vger mailing lists,
possibly due to a too long list of CCs (the other explanation being that CDF
has been delayed for so long that vger considers it a
The DISPLAY_ prefix will clash with the Common Display Framework, rename
it.
Signed-off-by: Laurent Pinchart
---
drivers/video/omap2/displays-new/Kconfig | 24
drivers/video/omap2/displays-new/Makefile | 24
2 files changed, 24 insertions(+), 24
The video and stream control operations handle video stream management,
both from the control point of view (called in response to userspace
requests) and the video stream point of view (called by entities to
control the video stream they receive on their input(s)).
Signed-off-by: Laurent Pinchart
The Common Display Framework (CDF) splits display devices in entities
that interact through an abstract API. Each entity is managed by its own
driver independently of the other entities, with the framework
orchestrating interactions.
This commit introduces the CDF core with entity (un)registration
Display entities are initialized by they respective drivers
asynchronously with the master display driver. The notifier
infrastructure allows display drivers to create a list of entities they
need (based on platform data) and be notified when those entities are
added to or removed from the system.
Add two graph helper functions. display_entity_build_notifier() builds
an entity notifier from an entities graph represented as a flat array,
typically passed from platform data. display_entity_link_graph() can
then be used to create media controller links between all entities in
the graph.
Signed
Pixel codings describe how pixels are transmitted on a physical bus. The
information can be communicated between drivers to configure devices.
Signed-off-by: Laurent Pinchart
---
include/video/display.h | 120
1 file changed, 120 insertions(+)
di
Extend the notifier with DT node matching support, and add helper functions to
build the notifier and link entities based on a graph representation in
DT.
Signed-off-by: Laurent Pinchart
---
drivers/video/display/display-core.c | 334 +++
drivers/video/display/dis
MIPI DBI is a configurable-width parallel display bus that transmits
commands and data.
Add a new DBI Linux bus type that implements the usual bus
infrastructure (including devices and drivers (un)registration and
matching, and bus configuration and access functions).
Signed-off-by: Laurent Pinch
The R61505 is a SYS-80 bus panel controller from Renesas.
Signed-off-by: Laurent Pinchart
---
drivers/video/display/Kconfig| 10 +
drivers/video/display/Makefile | 1 +
drivers/video/display/panel-r61505.c | 567 +++
include/video/panel-r61505.h
The Display Pixel Interface is a configurable-width video-only
unidirectional parallel bus standard that defines video formats and
signaling for panel devices.
This driver implements support for simple DPI panels with no runtime
configuration capabilities (GPIOs- and/or regulators-based control ca
The R61517 is a MIPI DBI panel controller from Renesas.
Signed-off-by: Laurent Pinchart
---
drivers/video/display/Kconfig| 10 +
drivers/video/display/Makefile | 1 +
drivers/video/display/panel-r61517.c | 460 +++
include/video/panel-r61517.h
This driver implements support for VGA Digital to Analog Converters
(DACs) that receive pixel data through a DPI interface and have no
control interface (GPIOs- and/or regulators-based control can be
implemented later when needed). It exposes the devices a display
entities.
Signed-off-by: Laurent
This driver exposes VGA connectors as display entity devices. The
connectors are passive devices that pass analog VGA signals though. They
optionally cary DDC signals for bidirectional control communications
with the devices connected to the connectors.
EDID retrieval isn't supported yet.
Signed-
Signed-off-by: Laurent Pinchart
---
arch/arm/mach-shmobile/clock-r8a7790.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/mach-shmobile/clock-r8a7790.c
b/arch/arm/mach-shmobile/clock-r8a7790.c
index d99b87b..7229f96 100644
--- a/arch/arm/mach-shmobile/clock-r8a7790.c
+++ b/arc
Signed-off-by: Laurent Pinchart
---
arch/arm/boot/dts/r8a7790.dtsi | 33 +
1 file changed, 33 insertions(+)
diff --git a/arch/arm/boot/dts/r8a7790.dtsi b/arch/arm/boot/dts/r8a7790.dtsi
index ab0582c..b63f1a6 100644
--- a/arch/arm/boot/dts/r8a7790.dtsi
+++ b/arch/a
Signed-off-by: Laurent Pinchart
---
arch/arm/mach-shmobile/board-marzen.c | 77 ---
1 file changed, 53 insertions(+), 24 deletions(-)
diff --git a/arch/arm/mach-shmobile/board-marzen.c
b/arch/arm/mach-shmobile/board-marzen.c
index 6499f1a..be1b7cb 100644
--- a/ar
Signed-off-by: Laurent Pinchart
---
arch/arm/mach-shmobile/board-lager.c | 76 +---
1 file changed, 53 insertions(+), 23 deletions(-)
diff --git a/arch/arm/mach-shmobile/board-lager.c
b/arch/arm/mach-shmobile/board-lager.c
index 75a01bc..d61b892 100644
--- a/arch
Signed-off-by: Laurent Pinchart
---
arch/arm/boot/dts/r8a7790-lager-reference.dts | 92 +++
1 file changed, 92 insertions(+)
diff --git a/arch/arm/boot/dts/r8a7790-lager-reference.dts
b/arch/arm/boot/dts/r8a7790-lager-reference.dts
index d9a25d5..ba2469b 100644
--- a/arc
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/rcar-du/Kconfig | 3 +-
drivers/gpu/drm/rcar-du/Makefile| 7 +-
drivers/gpu/drm/rcar-du/rcar_du_connector.c | 164
drivers/gpu/drm/rcar-du/rcar_du_connector.h | 36
drivers/gpu/drm/rcar-du/rcar_
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130810/6d0f1801/attachment.html>
DE, and lately with
3.4.55 LTS in ubuntu 12.04.2.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130810/5eb8/attachment.html>
pl111_fb = NULL;
> > > + struct drm_framebuffer *fb = NULL;
> > > + struct drm_gem_object *gem_obj;
> > > + struct pl111_gem_bo *bo;
> > > +
> > > + pr_info("DRM %s\n", __func__);
> > > + gem_obj = drm_gem_object_
Some Poulsbo cards seem to incorrectly report
SDVO_CMD_STATUS_TARGET_NOT_SPECIFIED instead of SDVO_CMD_STATUS_PENDING, which
causes the display to be turned off.
Signed-off-by: Guillaume Clement
---
drivers/gpu/drm/gma500/psb_intel_sdvo.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
On Fri, Aug 09, 2013 at 10:12:15PM -0700, Ben Widawsky wrote:
> The conditional is usually a recoverable driver bug, and so WARNing, and
> preventing the drm_mm code from doing potential damage (BUG) is
> desirable.
>
> This issue was hit and fixed twice while developing the i915 multiple
> addres
org/archives/dri-devel/attachments/20130810/0c5a768c/attachment.html>
On Sat, Aug 10, 2013 at 9:06 AM, Guillaume Clement
wrote:
> Some Poulsbo cards seem to incorrectly report
> SDVO_CMD_STATUS_TARGET_NOT_SPECIFIED instead of SDVO_CMD_STATUS_PENDING,
> which causes the display to be turned off.
>
> Signed-off-by: Guillaume Clement
Can you please submit the exa
On Sat, Aug 10, 2013 at 10:55:08AM +0200, Daniel Vetter wrote:
> On Sat, Aug 10, 2013 at 9:06 AM, Guillaume Clement
> wrote:
> > Some Poulsbo cards seem to incorrectly report
> > SDVO_CMD_STATUS_TARGET_NOT_SPECIFIED instead of SDVO_CMD_STATUS_PENDING,
> > which causes the display to be turned o
On Sat, Aug 10, 2013 at 11:19 AM, Chris Wilson
wrote:
> On Sat, Aug 10, 2013 at 10:55:08AM +0200, Daniel Vetter wrote:
>> On Sat, Aug 10, 2013 at 9:06 AM, Guillaume Clement
>> wrote:
>> > Some Poulsbo cards seem to incorrectly report
>> > SDVO_CMD_STATUS_TARGET_NOT_SPECIFIED instead of SDVO_CM
On Fri, Aug 9, 2013 at 1:31 PM, Tom Cooksey wrote:
>> > > So in the above, after X receives the second DRI2SwapBuffers, it
>> > > doesn't need to get scheduled again for the next frame to be both
>> > > rendered by the GPU and issued to the display for scanout.
>> >
>> > well, this is really only
/dri-devel/attachments/20130810/1e55cc09/attachment-0001.html>
xt part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130810/b4d7057d/attachment.html>
art --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130810/a98dbc6b/attachment.html>
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130810/51fe32fe/attachment.html>
> >> Can you please submit the exact same change for drm/i915/intel_sdvoc.c
> >> too? The sdvo encoders can be the same ones for psb and i915 so having
> >> the same code would be great. Separate patch for drm/i915 ofc.
> >
> > Are you absolutely sure that is a hardware error and not a software SDV
Some Poulsbo cards seem to incorrectly report
SDVO_CMD_STATUS_TARGET_NOT_SPECIFIED instead of SDVO_CMD_STATUS_PENDING, which
causes the display to be turned off.
This could also happen to i915.
Signed-off-by: Guillaume Clement
---
drivers/gpu/drm/i915/intel_sdvo.c | 3 ++-
1 file changed, 2 i
On Sat, Aug 10, 2013 at 9:40 PM, Guillaume CL?MENT
wrote:
>> >> Can you please submit the exact same change for drm/i915/intel_sdvoc.c
>> >> too? The sdvo encoders can be the same ones for psb and i915 so having
>> >> the same code would be great. Separate patch for drm/i915 ofc.
>> >
>> > Are yo
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130810/64eaaa50/attachment.html>
95 matches
Mail list logo
