<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/drivers/video, branch v2020.04</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<entry>
<title>video: rockchip: Support 4K resolution for rk3399, HDMI</title>
<updated>2020-04-02T13:52:01+00:00</updated>
<author>
<name>Jagan Teki</name>
<email>jagan@amarulasolutions.com</email>
</author>
<published>2020-04-02T11:41:25+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=05c65a82c3c1a1f5aced30babde51f934e066717'/>
<id>05c65a82c3c1a1f5aced30babde51f934e066717</id>
<content type='text'>
The default resolution for rockchip display is 1920x1080
which failed to work on 4K HDMI out displays on rk3399.

So, mark the default resolution as 3480x2160 for rk3399
HDMI out.

This would work all the hdmi display resolutions till
4K.

Signed-off-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
Tested-by: Peter Robinson &lt;pbrobinson@gmail.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The default resolution for rockchip display is 1920x1080
which failed to work on 4K HDMI out displays on rk3399.

So, mark the default resolution as 3480x2160 for rk3399
HDMI out.

This would work all the hdmi display resolutions till
4K.

Signed-off-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
Tested-by: Peter Robinson &lt;pbrobinson@gmail.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>video: rockchip: Fix vop modes for rk3399</title>
<updated>2020-04-02T13:47:35+00:00</updated>
<author>
<name>Jagan Teki</name>
<email>jagan@amarulasolutions.com</email>
</author>
<published>2020-04-02T11:41:22+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e67243f1a3afc1289f647c86642f067c1ab05498'/>
<id>e67243f1a3afc1289f647c86642f067c1ab05498</id>
<content type='text'>
VOP display endpoint pipeline configuration differs
between rk3288 vs rk3399.

These VOP pipeline configuration depends on how the
different display interfaces connected in sequence to
IN and OUT ports like for,

RK3288:

vopb_out: port {
	#address-cells = &lt;1&gt;;
	#size-cells = &lt;0&gt;;
	vopb_out_edp: endpoint@0 {
		reg = &lt;0&gt;;
		remote-endpoint = &lt;&amp;edp_in_vopb&gt;;
	};
	vopb_out_hdmi: endpoint@1 {
		reg = &lt;1&gt;;
                remote-endpoint = &lt;&amp;hdmi_in_vopb&gt;;
        };
        vopb_out_lvds: endpoint@2 {
                reg = &lt;2&gt;;
                remote-endpoint = &lt;&amp;lvds_in_vopb&gt;;
        };
        vopb_out_mipi: endpoint@3 {
                reg = &lt;3&gt;;
                remote-endpoint = &lt;&amp;mipi_in_vopb&gt;;
        };
};

RK3399:

vopb_out: port {
         #address-cells = &lt;1&gt;;
         #size-cells = &lt;0&gt;;
         vopb_out_edp: endpoint@0 {
                reg = &lt;0&gt;;
                remote-endpoint = &lt;&amp;edp_in_vopb&gt;;
         };
         vopb_out_mipi: endpoint@1 {
                reg = &lt;1&gt;;
                remote-endpoint = &lt;&amp;mipi_in_vopb&gt;;
         };
         vopb_out_hdmi: endpoint@2 {
                reg = &lt;2&gt;;
                remote-endpoint = &lt;&amp;hdmi_in_vopb&gt;;
         };
         vopb_out_mipi1: endpoint@3 {
                reg = &lt;3&gt;;
                remote-endpoint = &lt;&amp;mipi1_in_vopb&gt;;
         };
         vopb_out_dp: endpoint@4 {
                reg = &lt;4&gt;;
                remote-endpoint = &lt;&amp;dp_in_vopb&gt;;
         };
};

here, HDMI interface has endpoint 1 in rk3288 and 2 in rk3399.

The rockchip vop driver often depends on this determined endpoint
number and stored in vop_mode. So based on this vop_mode the bpp
and pin polarity would configure on detected display interface.

Since, the existing driver using rk3288 vop mode settings enabling
the same will result wrong display interface configuration for rk3399.

Add the patch for fixing these vop modes for rk3399.

Signed-off-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
Tested-by: Peter Robinson &lt;pbrobinson@gmail.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
VOP display endpoint pipeline configuration differs
between rk3288 vs rk3399.

These VOP pipeline configuration depends on how the
different display interfaces connected in sequence to
IN and OUT ports like for,

RK3288:

vopb_out: port {
	#address-cells = &lt;1&gt;;
	#size-cells = &lt;0&gt;;
	vopb_out_edp: endpoint@0 {
		reg = &lt;0&gt;;
		remote-endpoint = &lt;&amp;edp_in_vopb&gt;;
	};
	vopb_out_hdmi: endpoint@1 {
		reg = &lt;1&gt;;
                remote-endpoint = &lt;&amp;hdmi_in_vopb&gt;;
        };
        vopb_out_lvds: endpoint@2 {
                reg = &lt;2&gt;;
                remote-endpoint = &lt;&amp;lvds_in_vopb&gt;;
        };
        vopb_out_mipi: endpoint@3 {
                reg = &lt;3&gt;;
                remote-endpoint = &lt;&amp;mipi_in_vopb&gt;;
        };
};

RK3399:

vopb_out: port {
         #address-cells = &lt;1&gt;;
         #size-cells = &lt;0&gt;;
         vopb_out_edp: endpoint@0 {
                reg = &lt;0&gt;;
                remote-endpoint = &lt;&amp;edp_in_vopb&gt;;
         };
         vopb_out_mipi: endpoint@1 {
                reg = &lt;1&gt;;
                remote-endpoint = &lt;&amp;mipi_in_vopb&gt;;
         };
         vopb_out_hdmi: endpoint@2 {
                reg = &lt;2&gt;;
                remote-endpoint = &lt;&amp;hdmi_in_vopb&gt;;
         };
         vopb_out_mipi1: endpoint@3 {
                reg = &lt;3&gt;;
                remote-endpoint = &lt;&amp;mipi1_in_vopb&gt;;
         };
         vopb_out_dp: endpoint@4 {
                reg = &lt;4&gt;;
                remote-endpoint = &lt;&amp;dp_in_vopb&gt;;
         };
};

here, HDMI interface has endpoint 1 in rk3288 and 2 in rk3399.

The rockchip vop driver often depends on this determined endpoint
number and stored in vop_mode. So based on this vop_mode the bpp
and pin polarity would configure on detected display interface.

Since, the existing driver using rk3288 vop mode settings enabling
the same will result wrong display interface configuration for rk3399.

Add the patch for fixing these vop modes for rk3399.

Signed-off-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
Tested-by: Peter Robinson &lt;pbrobinson@gmail.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>video: meson: keep power domain up after booting</title>
<updated>2020-03-03T02:47:38+00:00</updated>
<author>
<name>Anatolij Gustschin</name>
<email>agust@denx.de</email>
</author>
<published>2020-02-17T11:36:44+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=9aa886cc0b4424b49b24486f804fd18aafad00b2'/>
<id>9aa886cc0b4424b49b24486f804fd18aafad00b2</id>
<content type='text'>
Add driver flag to skip power domain disabling on device removal.

Fixes: 52edfed65de9 ("dm: core: device: switch off power domain after device removal")
Signed-off-by: Anatolij Gustschin &lt;agust@denx.de&gt;
Acked-by: Neil Armstrong &lt;narmstrong@baylibre.com&gt;
Tested-by: Guillaume La Roque &lt;glaroque@baylibre.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add driver flag to skip power domain disabling on device removal.

Fixes: 52edfed65de9 ("dm: core: device: switch off power domain after device removal")
Signed-off-by: Anatolij Gustschin &lt;agust@denx.de&gt;
Acked-by: Neil Armstrong &lt;narmstrong@baylibre.com&gt;
Tested-by: Guillaume La Roque &lt;glaroque@baylibre.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'dm-pull-6feb20' of https://gitlab.denx.de/u-boot/custodians/u-boot-dm</title>
<updated>2020-02-11T15:58:41+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2020-02-11T15:58:41+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=9a8942b53d57149754e0dfc975e0d92d1afd4087'/>
<id>9a8942b53d57149754e0dfc975e0d92d1afd4087</id>
<content type='text'>
sandbox conversion to SDL2
TPM TEE driver
Various minor sandbox video enhancements
New driver model core utility functions
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
sandbox conversion to SDL2
TPM TEE driver
Various minor sandbox video enhancements
New driver model core utility functions
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'fixes-for-v2020.04' of https://gitlab.denx.de/u-boot/custodians/u-boot-video</title>
<updated>2020-02-10T17:08:51+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2020-02-10T17:08:51+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=5f2fe7d4617bbddc45b6a0cbf21cd468c57f4eba'/>
<id>5f2fe7d4617bbddc45b6a0cbf21cd468c57f4eba</id>
<content type='text'>
- fix Coverity CID 280902 issue in vid_console_color()
- fix vid_console_color() build warning
- fix for mxsfb to ensure correct Linux logo position
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
- fix Coverity CID 280902 issue in vid_console_color()
- fix vid_console_color() build warning
- fix for mxsfb to ensure correct Linux logo position
</pre>
</div>
</content>
</entry>
<entry>
<title>video: enable VIDEO_ANSI and all VIDEO_BBP options</title>
<updated>2020-02-06T21:11:47+00:00</updated>
<author>
<name>Anatolij Gustschin</name>
<email>agust@denx.de</email>
</author>
<published>2020-02-04T21:43:06+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8a6ffeda97dfda5263ef40e1a4efb25b032ce04c'/>
<id>8a6ffeda97dfda5263ef40e1a4efb25b032ce04c</id>
<content type='text'>
This partially reverts changes by commit 2cc393f32fd9
("video: make BPP and ANSI configs optional") since it
caused issues with other boards (missing LCD console
output on pinebook, x86 platform or sandbox). Enable
all disabled options again and opt out of not supported
color depth in board defconfigs.

Signed-off-by: Anatolij Gustschin &lt;agust@denx.de&gt;
Reported-by: Vagrant Cascadian &lt;vagrant@debian.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This partially reverts changes by commit 2cc393f32fd9
("video: make BPP and ANSI configs optional") since it
caused issues with other boards (missing LCD console
output on pinebook, x86 platform or sandbox). Enable
all disabled options again and opt out of not supported
color depth in board defconfigs.

Signed-off-by: Anatolij Gustschin &lt;agust@denx.de&gt;
Reported-by: Vagrant Cascadian &lt;vagrant@debian.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>dm: core: Create a new header file for 'compat' features</title>
<updated>2020-02-06T02:33:46+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-02-03T14:36:16+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=336d4615f8fa774557d14f9b3245daa9e5fe3dbc'/>
<id>336d4615f8fa774557d14f9b3245daa9e5fe3dbc</id>
<content type='text'>
At present dm/device.h includes the linux-compatible features. This
requires including linux/compat.h which in turn includes a lot of headers.
One of these is malloc.h which we thus end up including in every file in
U-Boot. Apart from the inefficiency of this, it is problematic for sandbox
which needs to use the system malloc() in some files.

Move the compatibility features into a separate header file.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
At present dm/device.h includes the linux-compatible features. This
requires including linux/compat.h which in turn includes a lot of headers.
One of these is malloc.h which we thus end up including in every file in
U-Boot. Apart from the inefficiency of this, it is problematic for sandbox
which needs to use the system malloc() in some files.

Move the compatibility features into a separate header file.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>dm: core: Require users of devres to include the header</title>
<updated>2020-02-06T02:33:46+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-02-03T14:36:15+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=61b29b82683863a970fd4609a7c58512872616bc'/>
<id>61b29b82683863a970fd4609a7c58512872616bc</id>
<content type='text'>
At present devres.h is included in all files that include dm.h but few
make use of it. Also this pulls in linux/compat which adds several more
headers. Drop the automatic inclusion and require files to include devres
themselves. This provides a good indication of which files use devres.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Anatolij Gustschin &lt;agust@denx.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
At present devres.h is included in all files that include dm.h but few
make use of it. Also this pulls in linux/compat which adds several more
headers. Drop the automatic inclusion and require files to include devres
themselves. This provides a good indication of which files use devres.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Anatolij Gustschin &lt;agust@denx.de&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>sandbox: Support changing the LCD colour depth</title>
<updated>2020-02-06T02:33:46+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-02-03T14:36:14+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a466db5adb58e486fbd8ae63536b03a70d69f68d'/>
<id>a466db5adb58e486fbd8ae63536b03a70d69f68d</id>
<content type='text'>
Add a new device-tree property to control the colour depth. At present we
support 16bpp and 32bpp.

While we are here, update the code to use livetree.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Anatolij Gustschin &lt;agust@denx.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add a new device-tree property to control the colour depth. At present we
support 16bpp and 32bpp.

While we are here, update the code to use livetree.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Anatolij Gustschin &lt;agust@denx.de&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>sandbox: sdl: Add an option to double the screen size</title>
<updated>2020-02-06T02:33:46+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-02-03T14:36:13+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=6be88c72828923f2df8c441ee12f5829e0d06f32'/>
<id>6be88c72828923f2df8c441ee12f5829e0d06f32</id>
<content type='text'>
On high-DPI displays U-Boot's LCD window can look very small. Add a
-K flag to expand it to make things easier to read, while still using
the existing resolution internally.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Anatolij Gustschin &lt;agust@denx.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
On high-DPI displays U-Boot's LCD window can look very small. Add a
-K flag to expand it to make things easier to read, while still using
the existing resolution internally.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Anatolij Gustschin &lt;agust@denx.de&gt;
</pre>
</div>
</content>
</entry>
</feed>
