Searched hist:b692eb6fea93db41292f80654d3f6a73176b15d6 (Results 1 – 4 of 4) sorted by relevance
| /rk3399_rockchip-uboot/include/linux/ |
| H A D | hdmi.h | b692eb6fea93db41292f80654d3f6a73176b15d6 Mon May 13 08:20:45 UTC 2024 Algea Cao <algea.cao@rock-chips.com> edid: Don't send non-zero YQ in AVI infoframe for HDMI 1.x sinks
Apparently some sinks look at the YQ bits even when receiving RGB,
and they get somehow confused when they see a non-zero YQ value.
So we can't just blindly follow CEA-861-F and set YQ to match the
RGB range.
Unfortunately there is no good way to tell whether the sink
designer claims to have read CEA-861-F. The CEA extension block
revision number has generally been stuck at 3 since forever,
and even a very recently manufactured sink might be based on
an old design so the manufacturing date doesn't seem like
something we can use. In lieu of better information let's
follow CEA-861-F only for HDMI 2.0 sinks, since HDMI 2.0 is
based on CEA-861-F. For HDMI 1.x sinks we'll always set YQ=0.
Change-Id: If477d06e6dbbf1ef0f84ef35abb075a37ff17be1
Signed-off-by: Algea Cao <algea.cao@rock-chips.com>
|
| /rk3399_rockchip-uboot/drivers/video/drm/ |
| H A D | dw_hdmi_qp.c | b692eb6fea93db41292f80654d3f6a73176b15d6 Mon May 13 08:20:45 UTC 2024 Algea Cao <algea.cao@rock-chips.com> edid: Don't send non-zero YQ in AVI infoframe for HDMI 1.x sinks
Apparently some sinks look at the YQ bits even when receiving RGB,
and they get somehow confused when they see a non-zero YQ value.
So we can't just blindly follow CEA-861-F and set YQ to match the
RGB range.
Unfortunately there is no good way to tell whether the sink
designer claims to have read CEA-861-F. The CEA extension block
revision number has generally been stuck at 3 since forever,
and even a very recently manufactured sink might be based on
an old design so the manufacturing date doesn't seem like
something we can use. In lieu of better information let's
follow CEA-861-F only for HDMI 2.0 sinks, since HDMI 2.0 is
based on CEA-861-F. For HDMI 1.x sinks we'll always set YQ=0.
Change-Id: If477d06e6dbbf1ef0f84ef35abb075a37ff17be1
Signed-off-by: Algea Cao <algea.cao@rock-chips.com>
|
| H A D | dw_hdmi.c | b692eb6fea93db41292f80654d3f6a73176b15d6 Mon May 13 08:20:45 UTC 2024 Algea Cao <algea.cao@rock-chips.com> edid: Don't send non-zero YQ in AVI infoframe for HDMI 1.x sinks
Apparently some sinks look at the YQ bits even when receiving RGB,
and they get somehow confused when they see a non-zero YQ value.
So we can't just blindly follow CEA-861-F and set YQ to match the
RGB range.
Unfortunately there is no good way to tell whether the sink
designer claims to have read CEA-861-F. The CEA extension block
revision number has generally been stuck at 3 since forever,
and even a very recently manufactured sink might be based on
an old design so the manufacturing date doesn't seem like
something we can use. In lieu of better information let's
follow CEA-861-F only for HDMI 2.0 sinks, since HDMI 2.0 is
based on CEA-861-F. For HDMI 1.x sinks we'll always set YQ=0.
Change-Id: If477d06e6dbbf1ef0f84ef35abb075a37ff17be1
Signed-off-by: Algea Cao <algea.cao@rock-chips.com>
|
| /rk3399_rockchip-uboot/common/ |
| H A D | edid.c | b692eb6fea93db41292f80654d3f6a73176b15d6 Mon May 13 08:20:45 UTC 2024 Algea Cao <algea.cao@rock-chips.com> edid: Don't send non-zero YQ in AVI infoframe for HDMI 1.x sinks
Apparently some sinks look at the YQ bits even when receiving RGB,
and they get somehow confused when they see a non-zero YQ value.
So we can't just blindly follow CEA-861-F and set YQ to match the
RGB range.
Unfortunately there is no good way to tell whether the sink
designer claims to have read CEA-861-F. The CEA extension block
revision number has generally been stuck at 3 since forever,
and even a very recently manufactured sink might be based on
an old design so the manufacturing date doesn't seem like
something we can use. In lieu of better information let's
follow CEA-861-F only for HDMI 2.0 sinks, since HDMI 2.0 is
based on CEA-861-F. For HDMI 1.x sinks we'll always set YQ=0.
Change-Id: If477d06e6dbbf1ef0f84ef35abb075a37ff17be1
Signed-off-by: Algea Cao <algea.cao@rock-chips.com>
|