From: neil.armstrong@linaro.org
To: linux-amlogic@lists.infradead.org
Subject: Re: meson: Enabling full-range HDMI output
Date: Wed, 23 Oct 2024 10:22:37 +0200 [thread overview]
Message-ID: <40c07e23-0784-4bcd-8da6-485866e81425@linaro.org> (raw)
In-Reply-To: <CAN-StX2faaw60pUqRcDtHgrovWYFsM+PGDDAhU8wbT6aeDQKwg@mail.gmail.com>
Hi,
On 23/10/2024 10:00, Francisco Ayala Le Brun wrote:
> Hello,
>
> I am seeking some guidance regarding enabling full-range HDMI output.
> Specifically, I am wondering which component in the video pipeline
> could be clamping HDMI output values to 16-235? Further details
> follow:
>
> I have been trying to get full-range HDMI output from a Le Potato
> s905x SBC. At the moment, HDMI output seems to be hard-coded to color
> quantization limited range (16-235). This greatly diminishes the
> contrast in full range displays.
>
> So far setting the VIU_OSD1/2_FULL_RANGE bit in the
> VIU_OSD1/2_CTRL_STAT2 register does not seem to work. I have also
> looked at the color space conversion matrix in dw_hdmi in case that is
> the culprit, but the values seem fine and setting that to zero does
> produce a signal in the full range (0). The buffer from the VIU is
> using a YUV format so dw_hdmi is not using the full to limited range
> conversion matrix.
Indeed the internal VPU pipeline is in 10bit YUV444, so it requires enabling
the dw-hdmi CSC, so perhaps those are not designed to output full-range RGB ?
Could you revert:
d3d6b1bf85ae drm: bridge: dw_hdmi: fix preference of RGB modes over YUV420
This would give you direct YUV444 HDMI output without CSC involved, reverting
is not an options because of low-cost HDMI panels lying in their EDID
and not really supporting YUV HDMI...
So if the original YUV is in full range, the culprit is in the DW-HDMI CSC
table.
Neil
>
> Thank you in advance,
> Francisco
>
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2024-10-23 8:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 8:00 Francisco Ayala Le Brun
2024-10-23 8:22 ` neil.armstrong [this message]
2024-10-23 12:12 ` Francisco Ayala Le Brun
2024-10-23 12:55 ` neil.armstrong
2024-10-24 8:38 ` neil.armstrong
2024-10-24 8:51 ` Neil Armstrong
2024-10-25 8:57 ` Francisco Ayala Le Brun
2024-10-28 8:24 ` neil.armstrong
2024-10-28 13:09 ` Francisco Ayala Le Brun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40c07e23-0784-4bcd-8da6-485866e81425@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®