From: Brian Starkey <Brian.Starkey@arm.com>
To: "james qian wang (Arm Technology China)" <james.qian.wang@arm.com>
Cc: nd <nd@arm.com>, Mihail Atanassov <Mihail.Atanassov@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>,
Ayan Halder <Ayan.Halder@arm.com>,
"seanpaul@chromium.org" <seanpaul@chromium.org>,
"Lowry Li (Arm Technology China)" <Lowry.Li@arm.com>
Subject: Re: [PATCH] drm/komeda: Adds output-color format/depth support
Date: Wed, 25 Sep 2019 09:48:11 +0000 [thread overview]
Message-ID: <20190925094810.fbeyt7fxvyhaip33@DESKTOP-E1NTVVP.localdomain> (raw)
In-Reply-To: <20190924021313.GA15776@jamwan02-TSP300>
Hi James,
On Tue, Sep 24, 2019 at 02:13:27AM +0000, james qian wang (Arm Technology China) wrote:
>
> Hi Brian:
>
> Since one monitor can support mutiple color-formats, this DT property
> supply a way for user to select a specific one from this supported
> color-formats.
Modifying DT is a _really_ user-unfriendly way of specifying
preferences. If we want a user to be able to pick a preferred format,
then it should probably be via the atomic API as Ville mentioned.
Cheers,
-Brian
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-09-25 9:48 UTC|newest]
Thread overview: 12+ 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 10:03 ` Mihail Atanassov
2019-09-23 1:49 ` Lowry Li (Arm Technology China)
2019-09-23 12:16 ` Brian Starkey
2019-09-23 12:50 ` Ville Syrjälä
2019-09-24 2:13 ` james qian wang (Arm Technology China)
2019-09-25 9:48 ` Brian Starkey [this message]
2019-09-27 2:22 ` james qian wang (Arm Technology China)
2019-09-30 10:36 ` Brian Starkey
2019-10-08 9:25 ` 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)
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=20190925094810.fbeyt7fxvyhaip33@DESKTOP-E1NTVVP.localdomain \
--to=brian.starkey@arm.com \
--cc=Ayan.Halder@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 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).