2011/9/27 Keith Packard kei...@keithp.com:
Here's a patch sequence which cleans up a bunch of PCH refclk related
bits.
For the series: Tested-by: Paulo Zanoni paulo.r.zan...@intel.com
Tested all the patches on Ironlake (LVDS + VGA). Fixes fd.o bug #38750 for me.
I also tested the patch you
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
the screen is
rotated. More information:
http://en.wikipedia.org/wiki/Intel_Active_Management_Technology#VNC-based_KVM_remote_control
Cheers,
Paulo
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org
From: Paulo Zanoni paulo.r.zan...@intel.com
Move code from drm_mode_connector_property_set_ioctl to a new
function, so we can reuse this code when we add crtc properties.
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu/drm/drm_crtc.c | 41
From: Paulo Zanoni paulo.r.zan...@intel.com
Code based on the connector properties code.
Two new ioctls:
- DRM_IOCTL_MODE_CRTC_GETPROPERTIES
- DRM_IOCTL_MODE_CRTC_SETPROPERTY
The i915 driver needs this (for the rotation property). Other drivers
might need this too.
Signed-off-by: Paulo Zanoni
From: Paulo Zanoni paulo.r.zan...@intel.com
This property is needed by to inform the KVMr feature about our
current rotation: whenever we change the rotation, we should change
that property so that the KVMr knows that the screen is rotated.
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
),
+ DRM_IOCTL_DEF(DRM_IOCTL_MODE_CRTC_SETPROPERTY,
drm_mode_crtc_set_property_ioctl, DRM_MASTER|DRM_CONTROL_ALLOW|DRM_UNLOCKED)
I'm not sure about how we want these flags. I just copied from
connector properties ioctls.
--
Paulo Zanoni
___
dri-devel mailing list
@)
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
From: Paulo Zanoni paulo.r.zan...@intel.com
Move code from drm_mode_connector_property_set_ioctl to a new
function, so we can reuse this code when we add crtc properties.
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu/drm/drm_crtc.c | 41
From: Paulo Zanoni paulo.r.zan...@intel.com
Also return void instead of int. We have more than 100 callers and
no one checks for the return value.
If this function fails the property won't be exposed by the get/set
ioctls, but we should probably survive. If this starts happening,
the solution
From: Paulo Zanoni paulo.r.zan...@intel.com
Code based on the connector properties code.
Two new ioctls:
- DRM_IOCTL_MODE_CRTC_GETPROPERTIES
- DRM_IOCTL_MODE_CRTC_SETPROPERTY
The i915 driver needs this for the rotation and overscan compensation
properties. Other drivers might need this too.
v2
From: Paulo Zanoni paulo.r.zan...@intel.com
This property is needed so we can inform the KVMr feature about our
current rotation: whenever we change the rotation, we should change
that property so that the KVMr knows that the screen is rotated.
How to reproduce the problem:
- on an AMT machine
From: Paulo Zanoni paulo.r.zan...@intel.com
They're named underscan x and underscan y. The properties accept
values from 0 to 100, where 0 is don't compensate and 100 is shrink
the screen as much as possible.
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu/drm/i915
From: Paulo Zanoni paulo.r.zan...@intel.com
Use unsigned int instead of int:
- modetest.c:89:1: warning: comparison between signed and unsigned integer
expressions [-Wsign-compare]
- modetest.c:97:1: warning: comparison between signed and unsigned integer
expressions [-Wsign-compare
From: Paulo Zanoni paulo.r.zan...@intel.com
Don't continue without freeing the connector.
192 bytes in 6 blocks are indirectly lost in loss record 6 of 12
at 0x4C2779D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
by 0x4E30DD8: drmMalloc (xf86drm.c:147)
by 0x4E35024
From: Paulo Zanoni paulo.r.zan...@intel.com
In the future we'll have more than just connector properties, so create
a dump_prop function that can handle any property (instead of the
current dump_props function that only handles connector properties).
Also, make this function print a lot more
From: Paulo Zanoni paulo.r.zan...@intel.com
New library calls:
- drmModeCrtcGetProperties
- drmModeFreeCrtcProperties
- drmModeCrtcSetProperties
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
include/drm/drm.h |2 +
include/drm/drm_mode.h | 13
xf86drmMode.c
From: Paulo Zanoni paulo.r.zan...@intel.com
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
tests/modetest/modetest.c | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/tests/modetest/modetest.c b/tests/modetest/modetest.c
index 52c81a9..58bb39e 100644
From: Paulo Zanoni paulo.r.zan...@intel.com
Same change for intel_display.c and sna_display.c.
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
src/intel_display.c | 104 +
src/sna/sna_display.c | 104
From: Paulo Zanoni paulo.r.zan...@intel.com
Don't worry if that fails: only the KVMr feature will be affected.
We still need to change the sna/ code.
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
src/intel.h |3 ++
src/intel_display.c | 79
From: Paulo Zanoni paulo.r.zan...@intel.com
In the Kernel side, these are crtc properties (since in the hardware,
underscan use the panel fitters, which are attached to the pipes).
Ideally we should make these as crtc properties too, but since xrandr
doesn't have support for them, we expose
the
new functions.
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
dependency and the sna/ code, so for now these are
just for review.
0001: Update the rotation property whenever we change the rotation.
0002: Add underscan properties
Cheers,
Paulo
2012/3/20 Paulo Zanoni przan...@gmail.com:
Hi
Some time ago I posted a patch series to implement Kernel CRTC
From: Paulo Zanoni paulo.r.zan...@intel.com
Move code from drm_mode_connector_property_set_ioctl to a new
function, so we can reuse this code when we add crtc properties.
v2: use bool instead of int
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu/drm/drm_crtc.c | 41
From: Paulo Zanoni paulo.r.zan...@intel.com
For now, only connectors have it. In the future, all objects that need
properties should use it. Since the strucutre is referenced inside
struct drm_mode_object, we will be able to deal with object properties
without knowing the real type of the object
From: Paulo Zanoni paulo.r.zan...@intel.com
Useless for connector properties (since they already have their own
ioctls), but useful when we add properties to CRTCs, planes and other
objects.
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu/drm/drm_crtc.c | 180
From: Paulo Zanoni paulo.r.zan...@intel.com
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu/drm/drm_crtc.c | 96 +--
1 files changed, 12 insertions(+), 84 deletions(-)
diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm
From: Paulo Zanoni paulo.r.zan...@intel.com
The i915 driver needs this for the rotation and overscan compensation
properties. Other drivers might need this too.
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu/drm/drm_crtc.c | 20
include/drm
From: Paulo Zanoni paulo.r.zan...@intel.com
This property is needed so we can inform the KVMr feature about our
current rotation: whenever we change the rotation, we should change
that property so that the KVMr knows that the screen is rotated.
How to reproduce the problem:
- on an AMT machine
From: Paulo Zanoni paulo.r.zan...@intel.com
They're named underscan hborder and underscan vborder. The
properties accept values from 0 to 100, where 0 is don't compensate
and 100 is shrink the screen as much as possible (not necessarily
100 pixels).
V2: Rename to underscan hborder and underscan
From: Paulo Zanoni paulo.r.zan...@intel.com
Use unsigned int instead of int:
- modetest.c:89:1: warning: comparison between signed and unsigned integer
expressions [-Wsign-compare]
- modetest.c:97:1: warning: comparison between signed and unsigned integer
expressions [-Wsign-compare
From: Paulo Zanoni paulo.r.zan...@intel.com
Don't continue without freeing the connector.
192 bytes in 6 blocks are indirectly lost in loss record 6 of 12
at 0x4C2779D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
by 0x4E30DD8: drmMalloc (xf86drm.c:147)
by 0x4E35024
From: Paulo Zanoni paulo.r.zan...@intel.com
New library calls:
- drmModeObjectGetProperties
- drmModeFreeObjectProperties
- drmModeObjectSetProperties
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
include/drm/drm.h |2 +
include/drm/drm_mode.h | 24
From: Paulo Zanoni paulo.r.zan...@intel.com
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
tests/modetest/modetest.c | 15 +++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/tests/modetest/modetest.c b/tests/modetest/modetest.c
index 02ea579..a6a2a8c
From: Paulo Zanoni paulo.r.zan...@intel.com
Don't worry if that fails: only the KVMr feature will be affected.
We still need to change the sna/ code.
We also need to add the dependency on libdrm.
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
src/intel.h |3 ++
src
From: Paulo Zanoni paulo.r.zan...@intel.com
In the Kernel side, these are crtc properties (since in the hardware,
underscan use the panel fitters, which are attached to the pipes).
Ideally we should make these as crtc properties too, but since xrandr
doesn't have support for them, we expose
mode
underscan
underscan hborder
underscan vborder
vibrant hue
- radeon:
coherent
load detection
tmds_pll
tv standard
underscan
underscan hborder
underscan vborder
Cheers,
Paulo
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
2012/3/30 Paulo Zanoni przan...@gmail.com:
Can't we try to add some document
(or header file) defining the standard properties and add a way to
distinguish between? Documentation/drm/properties.txt?
After looking at the list names, maybe we should define that standard
properties should
From: Paulo Zanoni paulo.r.zan...@intel.com
The specification defines a VIC (Video Identification Code) for each
mode. When we're browsing drm_edid_modes.h, it really helps to have the
number available (otherwise we have to count...). These numbers are also
used in the EDID data (by the CEA-EXT
From: Paulo Zanoni paulo.r.zan...@intel.com
CEA modes 6, 7, 8, 9, 21, 22, 23, 24, 44, 45, 50, 51, 54, 55, 58 and 59
require sending pixel data 2 times. This doesn't mean the modes will
work yet, but now the drivers know they're different.
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
From: Paulo Zanoni paulo.r.zan...@intel.com
To keep the consistency with the other fields.
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu/drm/i915/intel_drv.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_drv.h b
From: Paulo Zanoni paulo.r.zan...@intel.com
They require an AVI InfoFrame with a proper Pixel Repetition field.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=45729
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
I'm still waiting for confirmation on bugzilla, but I have access
this,
it should
be done in a separate patch.
I'm resending this patch with more warning fixes and a rebase.
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
2012/3/29 Eugeni Dodonov eug...@dodonov.net:
On Thu, Mar 29, 2012 at 18:28, Paulo Zanoni przan...@gmail.com wrote:
really-small-bikeshedding
I don't know if it should go into a separate patch though. But it is aligned
to the other formatting patterns you do, and it certainly looks nicer
From: Paulo Zanoni paulo.r.zan...@intel.com
Use unsigned int instead of int:
- modetest.c:90:1: warning: comparison between signed and unsigned integer
expressions [-Wsign-compare]
- modetest.c:98:1: warning: comparison between signed and unsigned integer
expressions [-Wsign-compare
From: Paulo Zanoni paulo.r.zan...@intel.com
Don't continue without freeing the connector.
192 bytes in 6 blocks are indirectly lost in loss record 6 of 12
at 0x4C2779D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
by 0x4E30DD8: drmMalloc (xf86drm.c:147)
by 0x4E35024
From: Paulo Zanoni paulo.r.zan...@intel.com
24 (16 direct, 8 indirect) bytes in 1 blocks are definitely lost in loss record
2 of 7
at 0x402994D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
by 0x4A25950: drmMalloc (xf86drm.c:147)
by 0x4A2E26D: drmModeGetPlaneResources
From: Paulo Zanoni paulo.r.zan...@intel.com
In the future we'll have more than just connector properties, so create
a dump_prop function that can handle any property (instead of the
current dump_props function that only handles connector properties).
Also, make this function print a lot more
in which struct to add this kind of
information to pass to the drivers...
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
2012/5/14 Paulo Zanoni przan...@gmail.com:
I haven't bothered to even try to fix them since I couldn't find any
TV/Monitor that supports them.
Also, I think flag DRM_MODE_FLAG_DBLCLK does not sound correct for
them, so we would need to create flags:
- DRM_MODE_FLAG_PR_1_to_10
From: Paulo Zanoni paulo.r.zan...@intel.com
Move code from drm_mode_connector_property_set_ioctl to a new
function, so we can reuse this code when we add crtc properties.
Reviewed-by: Eugeni Dodonov eugeni.dodo...@intel.com
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu
From: Paulo Zanoni paulo.r.zan...@intel.com
Also return void instead of int. We have more than 100 callers and
no one checks for the return value.
If this function fails the property won't be exposed by the get/set
ioctls, but we should probably survive. If this starts happening,
the solution
From: Paulo Zanoni paulo.r.zan...@intel.com
For now, only connectors have it. In the future, all objects that need
properties should use it. Since the structure is referenced inside
struct drm_mode_object, we will be able to deal with object properties
without knowing the real type of the object
From: Paulo Zanoni paulo.r.zan...@intel.com
Useless for connector properties (since they already have their own
ioctls), but useful when we add properties to CRTCs, planes and other
objects.
Reviewed-by: Eugeni Dodonov eugeni.dodo...@intel.com
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
From: Paulo Zanoni paulo.r.zan...@intel.com
In the future, we may want to kill the internal functions:
- drm_connector_attach_property
- drm_connector_property_set_value
- drm_connector_property_get_value
It seems the IOCTL drm_mode_connector_property_set_ioctl will have to live, but
we may
From: Paulo Zanoni paulo.r.zan...@intel.com
This way, we don't need to count every time, so we're a little bit
faster and code is a little bit smaller.
Change suggested by Ville Syrjälä.
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu/drm/drm_crtc.c | 64
From: Paulo Zanoni paulo.r.zan...@intel.com
The i915 driver needs this for the rotation and overscan compensation
properties. Other drivers might need this too.
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu/drm/drm_crtc.c | 20
include/drm
2012/5/15 Paulo Zanoni przan...@gmail.com:
Patches 0 to 6 are not completely useless: they change the code that's
executed
when someone changes the Connector properties, and they allow the
implementation
of other object properties. This patch (0007) is an example of how to add
properties
From: Paulo Zanoni paulo.r.zan...@intel.com
New library calls:
- drmModeObjectGetProperties
- drmModeFreeObjectProperties
- drmModeObjectSetProperties
Reviewed-by: Eugeni Dodonov eugeni.dodo...@intel.com
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
include/drm/drm.h |2
From: Paulo Zanoni paulo.r.zan...@intel.com
Reviewed-by: Eugeni Dodonov eugeni.dodo...@intel.com
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
tests/modetest/modetest.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/tests/modetest/modetest.c b/tests/modetest
From: Paulo Zanoni paulo.r.zan...@intel.com
A small program that allows us to see and modify properties.
Signed-off-by: Paulo Zanoni paulo.r.zan...@intel.com
---
configure.ac |1 +
tests/Makefile.am |2 +-
tests/proptest/Makefile.am | 11 ++
tests/proptest
/drm_crtc.h documenting the new
added fields of drm_plane_funcs and drm_funcs (we already have
descriptions of all the other fields).
With that:
Reviewed-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu/drm/drm_crtc.c | 19 +++
include/drm/drm_crtc.h | 5
num_values appears after column 80 in 2 places
/Bikeshedding
Reviewed-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu/drm/drm_crtc.c | 46
+---
include/drm/drm_crtc.h | 3 +++
include/drm/drm_mode.h | 1 +
3 files changed, 47
for bitmask properties
modetest: support bitmask properties
modetest: support plane properties
For the 3 patches:
Reviewed-by: Paulo Zanoni paulo.r.zan...@intel.com
You might want to create patch 0004 adding support for the proptest
tool... It might help you test stuff.
include/drm/drm_mode.h
+#define DRM_OBJECT_MAX_PROPERTY 24
struct drm_object_properties {
int count;
uint32_t ids[DRM_OBJECT_MAX_PROPERTY];
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo
connector in
the new kernel (and maybe this is also not a bug/regression...).
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
From: Paulo Zanoni paulo.r.zan...@intel.com
Before Kernel 3.5, no one was checking for the return value of
drm_connector_attach_property, so we never noticed that we were unable
to create some properties. Commit drm: WARN() when
drm_connector_attach_property fails added a WARN when we fail
-intel-next
drm/fb helper: don't call drm_helper_connector_dpms directly
Jani Nikula (2):
drm/i915: only enable sdvo hotplug irq if needed
drm/i915: fix sdvo hotplug support check and activation
Paulo Zanoni (3):
drm/i915: add gen7_render_ring_flush
drm
that this will affect patch 4 of this
series.
Idea for a follow-up patch: maybe we should try to add some comments
explaining which bits appeared only in some specific DPCD x.y
revision?
With the bit 7 problem fixed somehow:
Reviewed-by: Paulo Zanoni paulo.r.zan...@intel.com
+# define
2012/9/20 Adam Jackson a...@redhat.com:
Signed-off-by: Adam Jackson a...@redhat.com
Reviewed-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu/drm/i915/intel_dp.c |9 -
include/drm/drm_dp_helper.h |3 ++-
2 files changed, 6 insertions(+), 6 deletions(-)
diff
could check it
still does what it says on the box!
I have nothing to add or remove. Tested on HSW eDP, used xrandr to
alternate the property values. Works fine.
Being consistent on the default value between LVDS and eDP is
certainly a nice thing.
For the 3 patches:
Reviewed-by: Paulo Zanoni
From: Paulo Zanoni paulo.r.zan...@intel.com
We currently set 0 as the VIC value of the AVI InfoFrames. According
to the specs this should be fine and work for every mode, so to my
point of view we can't consider the current behavior as a bug. The
problem is that we recently received a bug report
Hi
2012/11/22 Thierry Reding thierry.red...@avionic-design.de:
On Wed, Nov 21, 2012 at 01:39:48PM -0200, Paulo Zanoni wrote:
From: Paulo Zanoni paulo.r.zan...@intel.com
We currently set 0 as the VIC value of the AVI InfoFrames. According
to the specs this should be fine and work for every
From: Paulo Zanoni paulo.r.zan...@intel.com
This function returns the VIC of the mode. This value can be used when
creating AVI InfoFrames.
Cc: Thierry Reding thierry.red...@avionic-design.de
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=50371
Signed-off-by: Paulo Zanoni paulo.r.zan
From: Paulo Zanoni paulo.r.zan...@intel.com
We currently set 0 as the VIC value of the AVI InfoFrames. According
to the specs this should be fine and work for every mode, so to my
point of view we can't consider the current behavior as a bug. The
problem is that we recently received a bug report
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
Hi
2012/12/6 Paulo Zanoni przan...@gmail.com:
Hi
2012/12/5 Thierry Reding thierry.red...@avionic-design.de:
Use the generic HDMI infoframe helpers to get rid of the duplicate
implementation in the i915 driver.
A few comments:
- I've compiled your patches and now intel_infoframes -d tells
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
From: Paulo Zanoni paulo.r.zan...@intel.com
Use the generic HDMI infoframe helpers to get rid of the duplicate
implementation in the i915 driver.
This patch is based on the initial patch by Thierry Reding, but with a
different approach.
TODO:
- The SDVO part is totally untested. I am not sure
correct (checked against the spec, did not really test).
Reviewed-by: Paulo Zanoni paulo.r.zan...@intel.com
See below for optional bikeshedding:
Signed-off-by: Ville Syrjälä ville.syrj...@linux.intel.com
---
drivers/gpu/drm/drm_edid.c | 33 +
include/drm
DIP_AVI_QUANTIZATION_LIMITED (1 2)
#define DIP_AVI_QUANTIZATION_FULL (2 2)
bikeshedding optional=true
Everything else looks fine.
With or without that:
Reviewed-by: Paulo Zanoni paulo.r.zan...@intel.com
Also, these things kinda conflict with Thierry's patches, but I know
you're aware because you've
patches
Things look correct. As you mention, the only problem seems to be the
Haswell. I could not find anything on the specs, so I think we should
send some emails and maybe consider removing the property on Haswell?
If-you-promise-to-find-a-solution-for-the-Haswell-case:
Reviewed-by: Paulo Zanoni
has weird colors bugs.
Reviewed-by: Paulo Zanoni paulo.r.zan...@intel.com
Signed-off-by: Ville Syrjälä ville.syrj...@linux.intel.com
---
drivers/gpu/drm/i915/i915_drv.h|4 +++
drivers/gpu/drm/i915/intel_dp.c| 28 ++---
drivers/gpu/drm/i915/intel_drv.h
about this patch (besides the sentence above) would
be due to using more than 80 columns, both on the commit message and
coding :)
Reviewed-by: Paulo Zanoni paulo.r.zan...@intel.com
Signed-off-by: Rodrigo Vivi rodrigo.v...@gmail.com
---
drivers/gpu/drm/i915/i915_reg.h | 16
intel_connector *attached_connector;
};
--
1.7.11.7
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Paulo Zanoni
___
dri-devel mailing list
*/
--
1.7.11.7
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http
From: Paulo Zanoni paulo.r.zan...@intel.com
If bit 0 of the features byte (0x18) is set to 0, then, according to
the EDID spec, the display is non-continuous frequency (multi-mode)
and is only specified to accept the video timing formats that are
listed in Base EDID and certain Extension Blocks
for TRANSCODER_EDP.
v2: Adding HSW_TVIDEO_DIP_VSC_DATA to transmit vsc to eDP.
Signed-off-by: Rodrigo Vivi rodrigo.v...@gmail.com
Reviewed-by: Paulo Zanoni paulo.r.zan...@intel.com
---
drivers/gpu/drm/i915/i915_reg.h | 18 ++
drivers/gpu/drm/i915/intel_hdmi.c | 13
://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
-devel
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
___
Intel-gfx mailing list
intel-...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http
Hi
2013/2/28 Sedat Dilek sedat.di...@gmail.com:
On Thu, Feb 28, 2013 at 6:12 PM, Sedat Dilek sedat.di...@gmail.com wrote:
On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni przan...@gmail.com wrote:
Hi
2013/2/28 Chris Wilson ch...@chris-wilson.co.uk:
On Thu, Feb 28, 2013 at 12:06:28AM +0100
EDP_PSR_DEBUG_MASK_MEMUP (126)
--
1.8.1.2
___
Intel-gfx mailing list
intel-...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Paulo Zanoni
___
dri-devel mailing list
dri
/listinfo/intel-gfx
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
RGB quantization range in automatic mode
Everything looks correct, but I really didn't test anything. If you
apply my comments from patch 2, then you have Reviewed-by: Paulo
Zanoni paulo.r.zan...@intel.com for all the 4 patches.
Optional bikeshedding: you could add a follow-up patch fixing
whenever panel is disabled/enabled.
v5: make it last patch to avoid breaking whenever bisecting. So calling for
update and force exit came to this patch along with enable/disable calls.
CC: Paulo Zanoni paulo.r.zan...@intel.com
Signed-off-by: Rodrigo Vivi rodrigo.v...@gmail.com
://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Paulo Zanoni
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
1 - 100 of 267 matches
Mail list logo
