Hi Tomi, On Tue, Feb 14, 2012 at 5:52 PM, Tomi Valkeinen <[email protected]> wrote: > Hi, >
> The color range is something that desktops have to handle also, so > there's probably ways to handle it in DRM. DisplayPort also has the same > range setting, so it's not specific to HDMI. > > So I propose to add a kernel API for this in the omap_dss_driver, so > that the users of omapdss may handle setting the range as they see best. > I see , it is fine i shall make it generic dss API. > Btw, the displayport spec speaks of VESA and CEA ranges. Does HDMI spec > only speak about limited/full range? > Yes so is the case with HDMI it is full range for VGA and limited range for rest. > 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. Thanks and regards, Mythri. > Tomi > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
