<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/gpu/drm/tilcdc, branch v3.11</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/gpu/drm/tilcdc?h=v3.11</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/gpu/drm/tilcdc?h=v3.11'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2013-06-27T23:13:00Z</updated>
<entry>
<title>drm/tilcdc: Clear bits of register we're going to set.</title>
<updated>2013-06-27T23:13:00Z</updated>
<author>
<name>Pantelis Antoniou</name>
<email>panto@antoniou-consulting.com</email>
</author>
<published>2013-06-21T18:52:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c19b3e238d7573cbe0bb60f4578b7d1de4a13746'/>
<id>urn:sha1:c19b3e238d7573cbe0bb60f4578b7d1de4a13746</id>
<content type='text'>
Bits weren't cleared so resolution changes didn't work.

Signed-off-by: Pantelis Antoniou &lt;panto@antoniou-consulting.com&gt;
Signed-off-by: Darren Etheridge &lt;detheridge@ti.com&gt;
Acked-by: Rob Clark &lt;robdclark@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/tilcdc fixing i2c/slave initialization race</title>
<updated>2013-06-27T23:12:54Z</updated>
<author>
<name>Darren Etheridge</name>
<email>detheridge@ti.com</email>
</author>
<published>2013-06-21T18:52:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=39de6194131c155901f96686a063212656d80c2e'/>
<id>urn:sha1:39de6194131c155901f96686a063212656d80c2e</id>
<content type='text'>
In certain senarios drm will initialize before i2c this means that i2c
slave devices like the nxp tda998x will fail to be probed.  This patch
detects this condition then defers the probe of the slave device and
the tilcdc main driver.

Signed-off-by: Darren Etheridge &lt;detheridge@ti.com&gt;
Acked-by: Rob Clark &lt;robdclark@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/tilcdc: whitespace fixes and tidyup</title>
<updated>2013-06-27T23:12:46Z</updated>
<author>
<name>Darren Etheridge</name>
<email>detheridge@ti.com</email>
</author>
<published>2013-06-21T18:52:26Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f7b4575601dafb3cf3c568465ec6980de6d09b94'/>
<id>urn:sha1:f7b4575601dafb3cf3c568465ec6980de6d09b94</id>
<content type='text'>
keeping checkpatch happy.

Signed-off-by: Darren Etheridge &lt;detheridge@ti.com&gt;
Acked-by: Rob Clark &lt;robdclark@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/tilcdc: adding more guards to prevent selection of invalid modes</title>
<updated>2013-06-27T23:12:39Z</updated>
<author>
<name>Darren Etheridge</name>
<email>detheridge@ti.com</email>
</author>
<published>2013-06-21T18:52:25Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e1c5d0a819e495a79cf76a8c63c5a30c327a89a5'/>
<id>urn:sha1:e1c5d0a819e495a79cf76a8c63c5a30c327a89a5</id>
<content type='text'>
The tilcdc has a number of limitations for the allowed sizes of
the various adjustable timing parameter.  Some modes are outside
of these timings.  This commit will prune modes that report timings
that will overflow the allowed sizes in the tilcdc.

Signed-off-by: Darren Etheridge &lt;detheridge@ti.com&gt;
Acked-by: Rob Clark &lt;robdclark@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/tilcdc: fixing off by one errors found on analyzer</title>
<updated>2013-06-27T23:12:32Z</updated>
<author>
<name>Darren Etheridge</name>
<email>detheridge@ti.com</email>
</author>
<published>2013-06-21T18:52:24Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=db2b4bd09b43fc27ecd097e193f1135f5e40d347'/>
<id>urn:sha1:db2b4bd09b43fc27ecd097e193f1135f5e40d347</id>
<content type='text'>
When hooking up to an HDMI analyzer noticed some timings were
off by one.  Referring to the hardware technical reference manual
for the lcd controller some of the timing registers use 0 to
represent 1.  This patch addresses that issue.

Signed-off-by: Darren Etheridge &lt;detheridge@ti.com&gt;
Acked-by: Rob Clark &lt;robdclark@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/tilcdc: adding some more devicetree config</title>
<updated>2013-06-27T23:12:23Z</updated>
<author>
<name>Darren Etheridge</name>
<email>detheridge@ti.com</email>
</author>
<published>2013-06-21T18:52:23Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4e5643468715260209e42b715e8cd9643456d2bd'/>
<id>urn:sha1:4e5643468715260209e42b715e8cd9643456d2bd</id>
<content type='text'>
Adding support for max-pixelclock and max-width device tree
entries. As some devices that use the tilcdc hardware module
have restrictions on the allowed/tested values.  Also update DT
bindings document to reflect new parameters.

Signed-off-by: Darren Etheridge &lt;detheridge@ti.com&gt;
Acked-by: Rob Clark &lt;robdclark@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/tilcdc: support pixel widths greater than 1024</title>
<updated>2013-06-27T23:12:13Z</updated>
<author>
<name>Darren Etheridge</name>
<email>detheridge@ti.com</email>
</author>
<published>2013-06-21T18:52:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6bf02c66b97379609a05bc715b96f874f2cefb33'/>
<id>urn:sha1:6bf02c66b97379609a05bc715b96f874f2cefb33</id>
<content type='text'>
TI LCD controller version 2 has an extended eleventh
bit that enables horizontal resolutions greater than
1024 pixels to be specified (upto 2048).  This patch
adds support for setting this bit on LCDC V2.

Signed-off-by: Darren Etheridge &lt;detheridge@ti.com&gt;
Acked-by: Rob Clark &lt;robdclark@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'v3.10-rc7' into drm-next</title>
<updated>2013-06-27T10:40:44Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2013-06-27T10:40:44Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4300a0f8bdcce5a03b88bfa16fc9827e15c52dc4'/>
<id>urn:sha1:4300a0f8bdcce5a03b88bfa16fc9827e15c52dc4</id>
<content type='text'>
Linux 3.10-rc7

The sdvo lvds fix in this -fixes pull

commit c3456fb3e4712d0448592af3c5d644c9472cd3c1
Author: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Date:   Mon Jun 10 09:47:58 2013 +0200

    drm/i915: prefer VBT modes for SVDO-LVDS over EDID

has a silent functional conflict with

commit 990256aec2f10800595dddf4d1c3441fcd6b2616
Author: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Date:   Fri May 31 12:17:07 2013 +0000

    drm: Add probed modes in probe order

in drm-next. W simply need to add the vbt modes before edid modes, i.e. the
other way round than now.

Conflicts:
	drivers/gpu/drm/drm_prime.c
	drivers/gpu/drm/i915/intel_sdvo.c
</content>
</entry>
<entry>
<title>gpu:drm:tilcdc: get preferred_bpp value from DT</title>
<updated>2013-06-20T04:08:01Z</updated>
<author>
<name>Benoit Parrot</name>
<email>bparrot@ti.com</email>
</author>
<published>2013-06-18T22:18:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dc28aa072f502433b6adc5c9ae8f56955c07580a'/>
<id>urn:sha1:dc28aa072f502433b6adc5c9ae8f56955c07580a</id>
<content type='text'>
The preferred_bpp value in currently hard-coded to 16.
This causes color corruption on the am335x-evm lcd panel which
requires 32 bpp instead. This changes attempts to use the configured
bpp value from the DT or built-in panel-info struct.

Signed-off-by: Benoit Parrot &lt;bparrot@ti.com&gt;
Acked-by: Rob Clark &lt;robdclark@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm: Drop all the stub gamma_get, gamma_set, load_lut functions from drivers</title>
<updated>2013-06-17T09:42:47Z</updated>
<author>
<name>Ville Syrjälä</name>
<email>ville.syrjala@linux.intel.com</email>
</author>
<published>2013-05-27T17:19:58Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=fb85ac4da8d202f89e0635e4ac2ac680d662be98'/>
<id>urn:sha1:fb85ac4da8d202f89e0635e4ac2ac680d662be98</id>
<content type='text'>
Many of the drivers didn't implement palette/gamma handling, but were forced
to provide stubs for the hooks to avoid drm_fb_helper from oopsing. Now that
the hooks are optional, we can eliminate all the stubs.

Signed-off-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Reviewed-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Dave Airlie &lt;airlied@gmail.com&gt;
</content>
</entry>
</feed>
