<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/drivers/video/rockchip, branch v2016.05</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/drivers/video/rockchip?h=v2016.05</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/drivers/video/rockchip?h=v2016.05'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2016-03-14T21:24:10Z</updated>
<entry>
<title>rockchip: video: Add LVDS support in vop driver</title>
<updated>2016-03-14T21:24:10Z</updated>
<author>
<name>Jacob Chen</name>
<email>jacob-chen@iotwrt.com</email>
</author>
<published>2016-03-14T03:20:18Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8530783594f6de14ec6d4b7bf804437d6e1a4f5f'/>
<id>urn:sha1:8530783594f6de14ec6d4b7bf804437d6e1a4f5f</id>
<content type='text'>
LVDS have a different display out mode, add code to get right flag.

The vop_ip decide display device and the remote_vop_id decide which
vop was being used. So we should use the remote_vop_id to set DCLK_VOP.

Signed-off-by: Jacob Chen &lt;jacob-chen@iotwrt.com&gt;
Acked-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>rockchip: video: Add a display driver for rockchip LVDS</title>
<updated>2016-03-14T21:06:33Z</updated>
<author>
<name>Jacob Chen</name>
<email>jacob-chen@iotwrt.com</email>
</author>
<published>2016-03-14T03:20:16Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=35ac89dd8fe7e9373d8c4336e7fbe93ae3fd59d7'/>
<id>urn:sha1:35ac89dd8fe7e9373d8c4336e7fbe93ae3fd59d7</id>
<content type='text'>
Some Rockchip SoCs support LVDS output. Add a display driver for this so
that these displays can be used on supported boards.

Signed-off-by: Jacob Chen &lt;jacob-chen@iotwrt.com&gt;
Acked-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>rockchip: video: Add a video-output driver</title>
<updated>2016-01-22T03:42:36Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-01-22T02:45:05Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=7b7ad5c31c91f84ae12b9a7ec850b5d0f720e19b'/>
<id>urn:sha1:7b7ad5c31c91f84ae12b9a7ec850b5d0f720e19b</id>
<content type='text'>
Some rockchip SoCs include video output (VOP). Add a driver to support this.
It can output via a display driver (UCLASS_DISPLAY) and currently HDMI and
eDP are supported.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>rockchip: video: Add a display driver for rockchip eDP</title>
<updated>2016-01-22T03:42:36Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-01-22T02:45:04Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=5852d539eab0e0a7f7a600cb57459091773c6c4a'/>
<id>urn:sha1:5852d539eab0e0a7f7a600cb57459091773c6c4a</id>
<content type='text'>
Some Rockchip SoCs support embedded DisplayPort output. Add a display driver
for this so that these displays can be used on supported boards.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>rockchip: video: Add a display driver for rockchip HDMI</title>
<updated>2016-01-22T03:42:36Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-01-22T02:45:03Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c2539483416a3237ae6d7f2d15fe468c4e771223'/>
<id>urn:sha1:c2539483416a3237ae6d7f2d15fe468c4e771223</id>
<content type='text'>
Some Rockchip SoCs support HDMI output. Add a display driver for this so
that these displays can be used on supported boards.

Unfortunately this driver is not fully functional. It cannot reliably read
EDID information over HDMI. This seems to be due to the clocks being
incorrect - the I2C bus speed appears to be up to 100x slower than the
clock settings indicate. The root cause may be in the clock logic.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
