From: Jose.Abreu@synopsys.com (Jose Abreu)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v3 4/6] drm: bridge: dw-hdmi: Switch to V4L bus format and encodings
Date: Mon, 13 Mar 2017 11:43:44 +0000 [thread overview]
Message-ID: <dfc1e19f-8b83-fc1a-3653-7e95bcc3c7f0@synopsys.com> (raw)
In-Reply-To: <f73a3cee-3336-2562-696d-dd4e0e7ac680@synopsys.com>
Hi Neil,
On 09-03-2017 14:27, Jose Abreu wrote:
> Hi Neil,
>
>
> On 08-03-2017 12:12, Neil Armstrong wrote:
>> Hi Jose,
>>
>> It seems here that we only have the RGB444<->YUV444 8bit tables, from the Amlogic
>> source I have the following for 10bit, 12bit and 16bit for itu601 :
>>
>> static const u16 csc_coeff_rgb_out_eitu601_10b[3][4] = {
>> { 0x2000, 0x6926, 0x74fd, 0x043b },
>> { 0x2000, 0x2cdd, 0x0000, 0x7a65 },
>> { 0x2000, 0x0000, 0x38b4, 0x78ea }
>> };
>>
>> static const u16 csc_coeff_rgb_out_eitu601_12b_16b[3][4] = {
>> { 0x2000, 0x6926, 0x74fd, 0x10ee },
>> { 0x2000, 0x2cdd, 0x0000, 0x6992 },
>> { 0x2000, 0x0000, 0x38b4, 0x63a6 }
>> };
> These two do not match anything I have here.
>
>> static const u16 csc_coeff_rgb_in_eitu601_10b[3][4] = {
>> { 0x2591, 0x1322, 0x074b, 0x0000 },
>> { 0x6535, 0x2000, 0x7acc, 0x0800 },
>> { 0x6acd, 0x7534, 0x2000, 0x0800 }
>> };
> This is more or less correct, I have small offsets. Note that I
> even have offsets with the values that are in dw-hdmi driver,
> which can be caused because I'm seeing the latest document that
> contain these values. I guess they were updated.
>
>> static const u16 csc_coeff_rgb_in_eitu601_12b_16b[3][4] = {
>> { 0x2591, 0x1322, 0x074b, 0x0000 },
>> { 0x6535, 0x2000, 0x7acc, 0x2000 },
>> { 0x6acd, 0x7534, 0x2000, 0x2000 }
>> };
> The same for this.
>
>> But I miss the itu709 values.
>>
>> Could you confirm these values and maybe provide the itu709 values ?
> I will have to check if I can provide you the values. I will get
> back to you.
Sorry but looks like I won't be able to provide you the correct
values :/ If you are working for a Synopsys customer you can
contact our CAE (If so I can guide you to the correct CAE).
Anyway, unless you can test the values you have I suggest you
don't use them, they do not match what I have here and I can't
test them because right now I don't have a setup (I'm assuming
that your CSC block within the controller was not modified).
Best regards,
Jose Miguel Abreu
next prev parent reply other threads:[~2017-03-13 11:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 16:42 [PATCH v3 0/6] drm: bridge: dw-hdmi: Add support for Custom PHYs Neil Armstrong
2017-03-07 16:42 ` [PATCH v3 1/6] drm: bridge: dw-hdmi: Extract PHY interrupt setup to a function Neil Armstrong
2017-03-07 17:12 ` Jose Abreu
2017-03-08 10:25 ` Neil Armstrong
2017-03-07 16:42 ` [PATCH v3 2/6] media: uapi: Add RGB and YUV bus formats for Synopsys HDMI TX Controller Neil Armstrong
2017-03-16 17:06 ` Archit Taneja
2017-03-17 16:10 ` Neil Armstrong
2017-03-20 15:35 ` Hans Verkuil
2017-03-07 16:42 ` [PATCH v3 3/6] documentation: media: Add documentation for new RGB and YUV bus formats Neil Armstrong
2017-03-16 17:01 ` Archit Taneja
2017-03-17 16:11 ` Neil Armstrong
2017-03-20 15:04 ` Hans Verkuil
2017-03-20 14:33 ` Hans Verkuil
2017-03-07 16:42 ` [PATCH v3 4/6] drm: bridge: dw-hdmi: Switch to V4L bus format and encodings Neil Armstrong
2017-03-07 17:35 ` Jose Abreu
2017-03-08 9:35 ` Neil Armstrong
2017-03-08 12:12 ` Neil Armstrong
2017-03-09 14:27 ` Jose Abreu
2017-03-13 11:43 ` Jose Abreu [this message]
2017-03-14 8:14 ` Neil Armstrong
2017-03-07 16:42 ` [PATCH v3 5/6] drm: bridge: dw-hdmi: Add Documentation on supported input formats Neil Armstrong
2017-03-16 16:43 ` Archit Taneja
2017-03-07 16:42 ` [PATCH v3 6/6] drm: bridge: dw-hdmi: Move HPD handling to PHY operations Neil Armstrong
2017-03-07 17:19 ` Jose Abreu
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=dfc1e19f-8b83-fc1a-3653-7e95bcc3c7f0@synopsys.com \
--to=jose.abreu@synopsys.com \
--cc=linus-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;
as well as URLs for NNTP newsgroup(s).