From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Brian Starkey <Brian.Starkey@arm.com>
Cc: "Lowry Li (Arm Technology China)" <Lowry.Li@arm.com>,
nd <nd@arm.com>, Ayan Halder <Ayan.Halder@arm.com>,
"airlied@linux.ie" <airlied@linux.ie>,
Liviu Dudau <Liviu.Dudau@arm.com>,
"Jonathan Chai (Arm Technology China)" <Jonathan.Chai@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Julien Yin (Arm Technology China)" <Julien.Yin@arm.com>,
"james qian wang (Arm Technology China)"
<james.qian.wang@arm.com>,
"seanpaul@chromium.org" <seanpaul@chromium.org>,
Mihail Atanassov <Mihail.Atanassov@arm.com>
Subject: Re: [PATCH] drm/komeda: Adds output-color format/depth support
Date: Mon, 23 Sep 2019 15:50:59 +0300 [thread overview]
Message-ID: <20190923125059.GI1208@intel.com> (raw)
In-Reply-To: <20190923121604.jqi6ewln27yvdajw@DESKTOP-E1NTVVP.localdomain>
On Mon, Sep 23, 2019 at 12:16:12PM +0000, Brian Starkey wrote:
> Hi Lowry,
>
> On Fri, Sep 20, 2019 at 09:43:47AM +0000, Lowry Li (Arm Technology China) wrote:
> > From: "Lowry Li (Arm Technology China)" <Lowry.Li@arm.com>
> >
> > Sets color_depth according to connector->bpc.
> > Adds a new optional DT attribute "color-format" to represent a
> > preferred color formats for a specific pipeline, and the select order
> > is:
> > YCRCB420 > YCRCB422 > YCRCB444 > RGB444
> > The color-format can be anyone of these 4 format, one color-format not
> > only represent one format, but also include the lower formats, like
> >
> > color-format preferred_color_formats
> > YCRCB420 YCRCB420 > YCRCB422 > YCRCB444 > RGB444
> > YCRCB422 YCRCB422 > YCRCB444 > RGB444
> > YCRCB444 YCRCB444 > RGB444
> > RGB444 RGB444
> >
> > Then the final color_format is calculated by 3 steps:
> > 1. calculate HW available formats.
> > avail_formats = connector_color_formats & improc->color_formats;
> > 2. filter out un-preferred format.
> > avail_formats &= preferred_color_formats;
> > 3. select the final format according to the preferred order.
> > color_format = BIT(__fls(aval_formats));
>
> Is there a specific use-case for the DT property for selecting color
> format?
>
> I think in general the color format should be determined according to
> the rules in the CEA spec. There's also the drm_mode_is_420_only()
> helper we can use to determine if YCBCR420 must be used. For the cases
> where it's optional, I think we can default to RGB444.
That is the policy we have in i915. We have a vague plan to add
a new property for the user to select the encoding explicitly
(which would also allow things like YCbCr 4:4:4), but IIRC no
one has actually sent a patch for that.
CTA-861 sort of seems to say that one should favor YCbCr over
RGB iff both sides support it, but I think RGB is probably the
better default because it means straight passthrough (minus the
annoying full->limit quantization range trickery).
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2019-09-23 12:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 9:43 [PATCH] drm/komeda: Adds output-color format/depth support Lowry Li (Arm Technology China)
2019-09-20 9:43 ` Lowry Li (Arm Technology China)
2019-09-20 10:03 ` Mihail Atanassov
2019-09-20 10:03 ` Mihail Atanassov
2019-09-23 1:49 ` Lowry Li (Arm Technology China)
2019-09-23 1:49 ` Lowry Li (Arm Technology China)
2019-09-23 12:16 ` Brian Starkey
2019-09-23 12:16 ` Brian Starkey
2019-09-23 12:50 ` Ville Syrjälä [this message]
2019-09-24 2:13 ` james qian wang (Arm Technology China)
2019-09-24 2:13 ` james qian wang (Arm Technology China)
2019-09-25 9:48 ` Brian Starkey
2019-09-25 9:48 ` Brian Starkey
2019-09-27 2:22 ` james qian wang (Arm Technology China)
2019-09-30 10:36 ` Brian Starkey
2019-09-30 10:36 ` Brian Starkey
2019-10-08 9:25 ` Lowry Li (Arm Technology China)
2019-10-08 9:25 ` Lowry Li (Arm Technology China)
2019-10-15 10:06 ` Lowry Li (Arm Technology China)
2019-10-15 10:06 ` Lowry Li (Arm Technology China)
-- strict thread matches above, loose matches on Subject: below --
2019-06-19 9:26 Lowry Li (Arm Technology China)
2019-06-19 9:26 ` Lowry Li (Arm Technology China)
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=20190923125059.GI1208@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=Ayan.Halder@arm.com \
--cc=Brian.Starkey@arm.com \
--cc=Jonathan.Chai@arm.com \
--cc=Julien.Yin@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=Lowry.Li@arm.com \
--cc=Mihail.Atanassov@arm.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=james.qian.wang@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nd@arm.com \
--cc=seanpaul@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.