From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "K, Mythri P" <mythripk@ti.com>
Cc: linux-omap@vger.kernel.org, Archit Taneja <archit@ti.com>
Subject: Re: [PATCH v4 3/3] OMAPDSS: HDMI: Sysfs support to configure quantization
Date: Fri, 09 Mar 2012 14:26:52 +0200 [thread overview]
Message-ID: <1331296012.1927.60.camel@deskari> (raw)
In-Reply-To: <CAP5A+B8J_y4GOMJ1pX1koYSDzGNA15i6ebY2i5ZZ5ZMZsvPE3A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 819 bytes --]
On Fri, 2012-03-09 at 16:17 +0530, K, Mythri P wrote:
> > I also only now realized that we have full/limited range setting in
> > video overlay's ATTRIBUTEs also. And it seems that we currently set it
> > always to 0, i.e. limited range. I wonder if this causes color
> > degradation in case the HDMI/DP output also sets limited range, and thus
> > the color range gets scaled down twice...
> >
> yes there is a limited/full range bit in dispc for color conversion,
> did a quick check using analyzer it doesn't impact the HDMI color
> range, so can confirm there is no degradation.
Did you try what happens if you set the range to full in DISPC? Because
it should affect HDMI also, so I don't quite understand how there could
be no degradation if both DISPC and HDMI do the range limiting.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-09 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 6:24 [PATCH v4 1/3] OMAPDSS: HDMI: Move Avi-infoframe struct to hdmi_ip_data mythripk
2012-02-08 6:24 ` [PATCH v4 2/3] OMAPDSS: HDMI: Add quantization range support in IP lib mythripk
2012-02-08 6:24 ` [PATCH v4 3/3] OMAPDSS: HDMI: Sysfs support to configure quantization mythripk
2012-02-14 12:22 ` Tomi Valkeinen
2012-03-09 10:47 ` K, Mythri P
2012-03-09 12:26 ` Tomi Valkeinen [this message]
2012-02-14 12:30 ` [PATCH v4 1/3] OMAPDSS: HDMI: Move Avi-infoframe struct to hdmi_ip_data Tomi Valkeinen
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=1331296012.1927.60.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=archit@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mythripk@ti.com \
/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