<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/gpu, branch v2.6.32.8</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/gpu?h=v2.6.32.8</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/gpu?h=v2.6.32.8'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2010-02-09T12:50:52Z</updated>
<entry>
<title>drm/i915: only enable hotplug for detected outputs</title>
<updated>2010-02-09T12:50:52Z</updated>
<author>
<name>Jesse Barnes</name>
<email>jbarnes@virtuousgeek.org</email>
</author>
<published>2009-12-11T19:07:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=612e99b2d1ba8839896c6ea78d4329782d4e16b8'/>
<id>urn:sha1:612e99b2d1ba8839896c6ea78d4329782d4e16b8</id>
<content type='text'>
commit b01f2c3a4a37d09a47ad73ccbb46d554d21cfeb0 upstream.

This patch changes around our hotplug enable code a bit to only enable
it for ports we actually detect and initialize.  This prevents problems
with stuck or spurious interrupts on outputs that aren't actually wired
up, and is generally more correct.

Fixes FDO bug #23183.

Signed-off-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>drm/i915: Reload hangcheck timer too for Ironlake</title>
<updated>2010-02-09T12:50:46Z</updated>
<author>
<name>Zhenyu Wang</name>
<email>zhenyuw@linux.intel.com</email>
</author>
<published>2009-12-17T08:12:56Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=61d4374b51386dd40c03fd15df5a7f97347de688'/>
<id>urn:sha1:61d4374b51386dd40c03fd15df5a7f97347de688</id>
<content type='text'>
commit c566ec49159b806db95a90fd8f37448376cd0ad2 upstream.

Make sure hangcheck timer won't beat us unexpectedly on Ironlake.

Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;
Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>drm/i915: Selectively enable self-reclaim</title>
<updated>2010-02-09T12:50:42Z</updated>
<author>
<name>Chris Wilson</name>
<email>chris@chris-wilson.co.uk</email>
</author>
<published>2010-01-27T13:36:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d8e0902806c0bd2ccc4f6a267ff52565a3ec933b'/>
<id>urn:sha1:d8e0902806c0bd2ccc4f6a267ff52565a3ec933b</id>
<content type='text'>
commit 4bdadb9785696439c6e2b3efe34aa76df1149c83 upstream.

Having missed the ENOMEM return via i915_gem_fault(), there are probably
other paths that I also missed. By not enabling NORETRY by default these
paths can run the shrinker and take memory from the system (but not from
our own inactive lists because our shrinker can not run whilst we hold
the struct mutex) and this may allow the system to survive a little longer
whilst our drivers consume all available memory.

References:
  OOM killer unexpectedly called with kernel 2.6.32
  http://bugzilla.kernel.org/show_bug.cgi?id=14933

v2: Pass gfp into page mapping.
v3: Use new read_cache_page_gfp() instead of open-coding.

Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Cc: KOSAKI Motohiro &lt;kosaki.motohiro@jp.fujitsu.com&gt;
Cc: Hugh Dickins &lt;hugh.dickins@tiscali.co.uk&gt;
Cc: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Cc: Eric Anholt &lt;eric@anholt.net&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>drm/i915: try another possible DDC bus for the SDVO device with multiple outputs</title>
<updated>2010-01-25T18:49:39Z</updated>
<author>
<name>Zhao Yakui</name>
<email>yakui.zhao@intel.com</email>
</author>
<published>2010-01-08T02:58:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ed0cd89c7333b17d50812201602f436b57ef1482'/>
<id>urn:sha1:ed0cd89c7333b17d50812201602f436b57ef1482</id>
<content type='text'>
commit 7c3f0a2726fed78e0e0afe3b6fc3c1f5b298e447 upstream.

There exist multiple DDC buses for the SDVO cards with multiple outputs.
When we can't get the EDID by using the select DDC bus, we can try the other
possible DDC bus to see whether the EDID can be obtained.

https://bugs.freedesktop.org/show_bug.cgi?id=23842

Signed-off-by: Zhao Yakui &lt;yakui.zhao@intel.com&gt;
Tested-by: Sebastien Caty &lt;sebastien.caty@mrnf.gouv.qc.ca&gt;
Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>drm/i915: Read the response after issuing DDC bus switch command</title>
<updated>2010-01-25T18:49:38Z</updated>
<author>
<name>Zhao Yakui</name>
<email>yakui.zhao@intel.com</email>
</author>
<published>2010-01-08T02:58:19Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4fb77a3f85d3e4633e6ef3a8b319f882caf7c623'/>
<id>urn:sha1:4fb77a3f85d3e4633e6ef3a8b319f882caf7c623</id>
<content type='text'>
commit 6a304caf0bf9c429fc261f260b86cabf5bde2cbb upstream.

For some SDVO cards based on conexant chip, we can't read the EDID if
we don't read the response after issuing SDVO DDC bus switch
command.

From the SDVO spec once when another I2C transaction is finished after
completing the I2C transaction of issuing the bus switch command, it
will be switched back to the SDVO internal state again. So we can't
initiate a new I2C transaction to read the response after issuing the
DDC bus switch command. Instead we should issue DDC bus switch command
and read the response in the same I2C transaction.

https://bugs.freedesktop.org/show_bug.cgi?id=23842
https://bugs.freedesktop.org/show_bug.cgi?id=24458
https://bugs.freedesktop.org/show_bug.cgi?id=24522
https://bugs.freedesktop.org/show_bug.cgi?id=24282

Signed-off-by: Zhao Yakui &lt;yakui.zhao@intel.com&gt;
Tested-by: Sebastien Caty &lt;sebastien.caty@mrnf.gouv.qc.ca&gt;
Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>drm/i915: remove loop in Ironlake interrupt handler</title>
<updated>2010-01-22T23:18:03Z</updated>
<author>
<name>Zou Nan hai</name>
<email>Nanhai.zou@intel.com</email>
</author>
<published>2010-01-15T02:29:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8a9c3f5c34a93fd4635aa739810280c4752eaa6e'/>
<id>urn:sha1:8a9c3f5c34a93fd4635aa739810280c4752eaa6e</id>
<content type='text'>
commit c7c85101afd0cb8ce497456d12ee1cad4aad152f upstream.

On Ironlake, there is an interrupt master control bit. With the bit
disabled before clearing IIR, we do not need to handle extra interrupt
in a loop. This patch removes the loop in Ironlake interrupt handler.
It fixed irq lost issue on some Ironlake platforms.

Signed-off-by: Zou Nan hai &lt;Nanhai.zou@intel.com&gt;
Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;
Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;


</content>
</entry>
<entry>
<title>drm/i915: remove render reclock support</title>
<updated>2010-01-18T18:19:48Z</updated>
<author>
<name>Jesse Barnes</name>
<email>jbarnes@virtuousgeek.org</email>
</author>
<published>2009-12-17T19:11:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b9945e752afed38518d7041ae00dea25f6272a34'/>
<id>urn:sha1:b9945e752afed38518d7041ae00dea25f6272a34</id>
<content type='text'>
commit cda9d05c499093c67b4a376a15009923acc2127a upstream.

This code generally fails to adjust the render clock, and when it does,
it conflicts with some other register settings and can cause problems.

So remove this code altogether.  I'm reworking it now to do the right
thing, but the only bit it will share is the VBT check for whether
reclocking is supported, so I'm leaving that bit.

Reverts most of 652c393a3368af84359da37c45afc35a91144960 ("add dynamic
clock frequency control"), though for many the regressions showed up
in the later 181a5336d6cc836f05507410d66988c483ad0154 ("Fix render
reclock availability detection").

Signed-off-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>drm/i915: fix unused var</title>
<updated>2010-01-18T18:19:28Z</updated>
<author>
<name>Andrew Morton</name>
<email>akpm@linux-foundation.org</email>
</author>
<published>2009-11-17T22:08:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0c51b5c49b554e7da4c929e1ee877d9e47ba1eec'/>
<id>urn:sha1:0c51b5c49b554e7da4c929e1ee877d9e47ba1eec</id>
<content type='text'>
commit 29bd0ae25f8cb96b63560c2cbccec77b425e1603 upstream.

drivers/gpu/drm/i915/i915_dma.c: In function 'i915_driver_load':
drivers/gpu/drm/i915/i915_dma.c:1114: warning: 'll_base' may be used uninitialized in this function

Partly this is because gcc isn't smart enough.  But `ll_base' does get used
uninitialised in the DRM_DEBUG() call.

Cc: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Cc: Eric Anholt &lt;eric@anholt.net&gt;
Cc: Dave Airlie &lt;airlied@linux.ie&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>drm/i915: Select the correct BPC for LVDS on Ironlake</title>
<updated>2010-01-18T18:19:27Z</updated>
<author>
<name>Zhao Yakui</name>
<email>yakui.zhao@intel.com</email>
</author>
<published>2010-01-04T08:29:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c7e8c269f5d886064af13e7d3eff1324cd78248c'/>
<id>urn:sha1:c7e8c269f5d886064af13e7d3eff1324cd78248c</id>
<content type='text'>
commit e5a95eb778690bc864eb330202d2c1b974caaeb4 upstream.

Select the correct BPC for LVDS on Ironlake. If it is 18-bit LVDS panel,
the BPC will be 6. When it is 24-bit LVDS panel, the BPC will 8.
At the same time the BPC will be 8 when the output device is CRT/HDMI/DP.

Signed-off-by: Zhao Yakui &lt;yakui.zhao@intel.com&gt;
Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>drm/i915: Make the BPC in FDI rx/transcoder be consistent with that in pipeconf on Ironlake</title>
<updated>2010-01-18T18:19:25Z</updated>
<author>
<name>Zhao Yakui</name>
<email>yakui.zhao@intel.com</email>
</author>
<published>2010-01-04T08:29:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c04fd308e3d6148c3c8bcba688c668569759b29c'/>
<id>urn:sha1:c04fd308e3d6148c3c8bcba688c668569759b29c</id>
<content type='text'>
commit 8faf3b317471179c02db339aa80955a2e88c036d upstream.

Make the BPC in FDI rx/transcoder be consistent with that in pipeconf on Ironlake.

Signed-off-by: Zhao Yakui &lt;yakui.zhao@intel.com&gt;
Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
