<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/include/video, branch v2.6.36</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v2.6.36</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v2.6.36'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2010-08-14T20:26:51Z</updated>
<entry>
<title>include: replace unifdef-y with header-y</title>
<updated>2010-08-14T20:26:51Z</updated>
<author>
<name>Sam Ravnborg</name>
<email>sam@ravnborg.org</email>
</author>
<published>2010-08-14T08:15:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=60641aa1f379820e99ac7f45a38b43795670c741'/>
<id>urn:sha1:60641aa1f379820e99ac7f45a38b43795670c741</id>
<content type='text'>
unifdef-y and header-y has same semantic.
So there is no need to have both.

Drop the unifdef-y variant and sort all lines again

Signed-off-by: Sam Ravnborg &lt;sam@ravnborg.org&gt;
</content>
</entry>
<entry>
<title>fbdev: sh-mobile: HDMI support for SH-Mobile SoCs</title>
<updated>2010-08-04T07:12:15Z</updated>
<author>
<name>Guennadi Liakhovetski</name>
<email>g.liakhovetski@gmx.de</email>
</author>
<published>2010-07-21T10:13:21Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=6011bdeaa6089d49c02de69f05980da7bad314ab'/>
<id>urn:sha1:6011bdeaa6089d49c02de69f05980da7bad314ab</id>
<content type='text'>
Some SH-Mobile SoCs have an HDMI controller and a PHY, attached to one of their
LCDC interfaces. This patch adds a preliminary static support for such
controllers, this means, that only the 720p mode is handled ATM. Support for
more modes and a dynamic switching between them will be added by a follow up
patch.

Signed-off-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
Acked-by: Magnus Damm &lt;damm@opensource.se&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh: add a parameter to LCDC driver's .display_on() callback</title>
<updated>2010-08-04T07:12:11Z</updated>
<author>
<name>Guennadi Liakhovetski</name>
<email>g.liakhovetski@gmx.de</email>
</author>
<published>2010-07-21T10:13:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=c2439398170be9d7af28eb3ab59593369cb303f3'/>
<id>urn:sha1:c2439398170be9d7af28eb3ab59593369cb303f3</id>
<content type='text'>
HDMI support for the sh_mobile_lcdc framebuffer driver will require a 'struct
fb_info *' pointer for its .display_on() callback. While at it fix kfr2r09
framebuffer modular build.

Signed-off-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
Acked-by: Magnus Damm &lt;damm@opensource.se&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6</title>
<updated>2010-05-31T04:14:26Z</updated>
<author>
<name>Paul Mundt</name>
<email>lethal@linux-sh.org</email>
</author>
<published>2010-05-31T04:14:26Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d5b732b17ca2fc74f370bdba5aae6c804fac8c35'/>
<id>urn:sha1:d5b732b17ca2fc74f370bdba5aae6c804fac8c35</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fbdev: move FBIO_WAITFORVSYNC to linux/fb.h</title>
<updated>2010-05-25T15:07:09Z</updated>
<author>
<name>Grazvydas Ignotas</name>
<email>notasas@gmail.com</email>
</author>
<published>2010-05-24T21:34:02Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=49c39b4953e545ce3b5957cce22e1ade01c6e642'/>
<id>urn:sha1:49c39b4953e545ce3b5957cce22e1ade01c6e642</id>
<content type='text'>
FBIO_WAITFORVSYNC is currently implemented by matroxfb, atyfb, intelfb and
more.  All of them keep redefining the same FBIO_WAITFORVSYNC macro over
and over again, so move it to linux/fb.h and clean up those duplicate
defines.

Signed-off-by: Grazvydas Ignotas &lt;notasas@gmail.com&gt;
Cc: Ville Syrjala &lt;syrjala@sci.fi&gt;
Cc: Grant Likely &lt;grant.likely@secretlab.ca&gt;
Cc: Maik Broemme &lt;mbroemme@plusserver.de&gt;
Cc: Petr Vandrovec &lt;vandrove@vc.cvut.cz&gt;
Cc: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Cc: Krzysztof Helt &lt;krzysztof.h1@poczta.fm&gt;
Cc: "Hiremath, Vaibhav" &lt;hvaibhav@ti.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>fbdev: da8xx/omap-l1xx: implement double buffering</title>
<updated>2010-05-25T15:07:09Z</updated>
<author>
<name>Martin Ambrose</name>
<email>martin@ti.com</email>
</author>
<published>2010-05-24T21:34:01Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1f9c3e1f07e39c8af3bf42236fc553b5bb0f83f1'/>
<id>urn:sha1:1f9c3e1f07e39c8af3bf42236fc553b5bb0f83f1</id>
<content type='text'>
This work includes the following:

- Implement handler for FBIO_WAITFORVSYNC ioctl.

- Allocate the data and palette buffers separately.  A consequence of
  this is that the palette and data loading is now done in different
  phases.  And that the LCD must be disabled temporarily after the palette
  is loaded but this will only happen once after init and each time the
  palette is changed.  I think this is OK.

- Allocate two (ping and pong) framebuffers from memory.

- Add pan_display handler which toggles the LCDC DMA registers between
  the ping and pong buffers.

Signed-off-by: Martin Ambrose &lt;martin@ti.com&gt;
Cc: Chaithrika U S &lt;chaithrika@ti.com&gt;
Cc: Sudhakar Rajashekhara &lt;sudhakar.raj@ti.com&gt;
Cc: Krzysztof Helt &lt;krzysztof.h1@poczta.fm&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>sh-mobile: add support for displays, connected over the MIPI bus</title>
<updated>2010-05-23T23:49:05Z</updated>
<author>
<name>Guennadi Liakhovetski</name>
<email>g.liakhovetski@gmx.de</email>
</author>
<published>2010-05-23T14:00:43Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=9fd04fe34af36344f61ebb24cc653726c231356e'/>
<id>urn:sha1:9fd04fe34af36344f61ebb24cc653726c231356e</id>
<content type='text'>
Some SH-mobile SoCs have a MIPI DSI controller, that can be used to connect
MIPI displays to LCDC. This patch adds a platform driver for SH-mobile MIPI DSI
unit. It uses existing hooks in the sh_mobile_lcdcfb.c driver for display
activation and deactivation.

Signed-off-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
Tested-by: Damian Hobson-Garcia &lt;dhobsong@igel.co.jp&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh: add a YUV422 output data format, that is also supported by LCDC</title>
<updated>2010-05-23T23:49:01Z</updated>
<author>
<name>Guennadi Liakhovetski</name>
<email>g.liakhovetski@gmx.de</email>
</author>
<published>2010-05-21T15:15:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1430e006a36da5401ad4420711b5a702ba17afa8'/>
<id>urn:sha1:1430e006a36da5401ad4420711b5a702ba17afa8</id>
<content type='text'>
The LCDC block is allowed to use one of the two output data formats, when used
with MIPI DSI: RGB24 and YUV422. YUV422 is not currently handled by the LCDC
driver, but we have to add a define for it for MIPI.

Signed-off-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>fbdev: add a MIPI DSI header</title>
<updated>2010-05-23T23:47:38Z</updated>
<author>
<name>Guennadi Liakhovetski</name>
<email>g.liakhovetski@gmx.de</email>
</author>
<published>2010-05-20T16:31:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=ea95450eede38ca695db8c2202b1f5c7a0f9ebbb'/>
<id>urn:sha1:ea95450eede38ca695db8c2202b1f5c7a0f9ebbb</id>
<content type='text'>
This header adds defines for MIPI DSI and DCS commands and data formats. See
http://www.mipi.org/ for details.

Signed-off-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
Acked-by: Tomi Valkeinen &lt;tomi.valkeinen@nokia.com&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>broadsheetfb: support storing waveform</title>
<updated>2010-03-12T23:52:34Z</updated>
<author>
<name>Jaya Kumar</name>
<email>jayakumar.lkml@gmail.com</email>
</author>
<published>2010-03-10T23:21:43Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=b32bfc3843f7fd090d30853d98866d923cfb8fff'/>
<id>urn:sha1:b32bfc3843f7fd090d30853d98866d923cfb8fff</id>
<content type='text'>
This patch adds waveform storing capability to broadsheetfb. It uses the
firmware class to retrieve the waveform, and the request to initiate the
waveform storing is done via a driver sysfs entry, loadstore_waveform.

Broadsheet is a framebuffer device.  It is slightly different from a
typical framebuffer controller that drives a normal TFT-LCD display.  Most
E-Ink display panels require a waveform in order to function.  That is, in
order to drive the state of a pixel to black, gray, or white, a specific
waveform is utilized.  Basically, that waveform represents the specific
E-field wiggling needed to get the pixel to its optimal state given
current temperature, and its previous state.  TN/IPS-LCDs use a similar
concept but the driving waveform is sufficiently simple that it is
internalized in the TFT source/gate driver.

These E-Ink waveforms are specific to a production batch.  That is, a
batch of display films are produced, then they get characterized and a
waveform is generated for that batch.  Broadsheet, typically, is attached
to its private SPI flash which is then flashed with this waveform.

Users won't be able to see the waveform and typically won't ever need to
know about it.  If however, the display panel attached to broadsheet is
changed out, then they will need to update their waveform.  That would
typically be done at a factory or repair facility rather than by a user.

[akpm@linux-foundation.org: fix printk warning]
Signed-off-by: Jaya Kumar &lt;jayakumar.lkml@gmail.com&gt;
Cc: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;
Cc: Krzysztof Helt &lt;krzysztof.h1@wp.pl&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
</feed>
