From: "james qian wang (Arm Technology China)" <james.qian.wang@arm.com>
To: Brian Starkey <Brian.Starkey@arm.com>
Cc: "Lowry Li (Arm Technology China)" <Lowry.Li@arm.com>,
Liviu Dudau <Liviu.Dudau@arm.com>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"seanpaul@chromium.org" <seanpaul@chromium.org>,
"airlied@linux.ie" <airlied@linux.ie>,
Mihail Atanassov <Mihail.Atanassov@arm.com>,
"Julien Yin (Arm Technology China)" <Julien.Yin@arm.com>,
"Jonathan Chai (Arm Technology China)" <Jonathan.Chai@arm.com>,
Ayan Halder <Ayan.Halder@arm.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
nd <nd@arm.com>
Subject: Re: [PATCH] drm/komeda: Adds output-color format/depth support
Date: Fri, 27 Sep 2019 02:22:24 +0000 [thread overview]
Message-ID: <20190927022218.GA11732@jamwan02-TSP300> (raw)
In-Reply-To: <20190925094810.fbeyt7fxvyhaip33@DESKTOP-E1NTVVP.localdomain>
On Wed, Sep 25, 2019 at 09:48:11AM +0000, Brian Starkey wrote:
> 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.
>
Hi Brian:
Agree, a drm UPAI might be the best & right way for this.
I can raise a new thread/topic to discuss the "HOW TO", maybe after the
Chinese national day.
LAST:
what do you think about this patch:
- Just drop it, waiting for the new uapi
- or keep it, and replace it once new uapi is ready.
Thanks
James
> Cheers,
> -Brian
next prev parent reply other threads:[~2019-09-27 2:22 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ä
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) [this message]
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=20190927022218.GA11732@jamwan02-TSP300 \
--to=james.qian.wang@arm.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=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--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.