hdmitx: uboot modify default hdr_priority value [1/1]
PD#SWPL-191567
Problem:
The Google HDR strategy used by Android U is incompatible with
the private HDR strategy of Android R. When the default value
of hdr_priority is given as the Google HDR strategy value, it
will affect the private HDR strategy.
Solution:
For uboot 2023 currently used with androidu, a default value
of dv priority is given to hdr_priority. In other cases,
special modifications will be made for the project
Verify:
s7
Change-Id: Ic3055d8149dded322a4b5272ae5a9456707e7d6d
Signed-off-by: xiang.wu1 <xiang.wu1@amlogic.com>
diff --git a/cmd/amlogic/cmd_hdmitx21.c b/cmd/amlogic/cmd_hdmitx21.c
index f41d16c..a67544a 100644
--- a/cmd/amlogic/cmd_hdmitx21.c
+++ b/cmd/amlogic/cmd_hdmitx21.c
@@ -1378,20 +1378,16 @@
* the inconsistency between the value of the hdr_priority environment
* variable and the result of the Google hdr policy during the boot
* process, causing the TV to flash black.
- * Android use strategy2:
- * 268435456 = 0x10000000, DV priority
- * 268435472 = 0x10000010, HDR priority
- * Linux Yocto not set
+ * AndroidU use strategy2: default DV priority
+ * 268435456 = 0x10000000, DV priority.
+ * If the DV library is not burned, the computer may flash black when
+ * it is turned on for the first time after burning.
+ * Linux Yocto not set.
*/
if (hdr_priority == -1) {
#ifndef CONFIG_YOCTO
- if (is_amdolby_enabled()) {
- hdr_priority = 268435456;
- env_set("hdr_priority", "268435456");
- } else {
- hdr_priority = 268435472;
- env_set("hdr_priority", "268435472");
- }
+ hdr_priority = 268435456;
+ env_set("hdr_priority", "268435456");
#endif
}