From: Simon Ser <contact@emersion.fr>
To: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@linux.ie>,
Yannick FERTRE - foss <yannick.fertre@foss.st.com>,
Philippe CORNU - foss <philippe.cornu@foss.st.com>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE - foss <alexandre.torgue@foss.st.com>,
Matt Roper <matthew.d.roper@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Yannick FERTRE <yannick.fertre@st.com>,
Raphael GALLAIS-POU <raphael.gallais-pou@st.com>,
Philippe CORNU <philippe.cornu@st.com>
Subject: Re: [PATCH 0/2] Add "BACKGROUND_COLOR" drm property
Date: Fri, 09 Jul 2021 09:23:10 +0000 [thread overview]
Message-ID: <OMOzHvru0iqQzq7rTSqJtI0P9wKSBLATuflwj10xgHvSgJ49V522CaDkIiZ0wWHJw-F5GPQxeO8cKO5ACMXggtDNlfx5TAa0zRObj7wsHHg=@emersion.fr> (raw)
In-Reply-To: <a8f02b4c-b1ea-320e-a6b2-952f4e641794@foss.st.com>
On Friday, July 9th, 2021 at 11:09, Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com> wrote:
> We don't usually test with piglit and igt-gpu-tools. Instead, modetest
> utility of the libdrm is used quite often (as is it the case in order to
> test this property).
Just to make it extra clear: regardless of how you bring up your driver
implementation, without an IGT test and real-world open-source user-space
patches that make use of the new prop, your patches *cannot* be merged.
If you're planning to add support for the new prop to an open-source KMS
client, please add a link to the patches in your kernel submission. If
you don't have plans to use the new prop in an open-source KMS client,
let us know and we can discuss what the best candidate would be.
> I was also thinking about implementing an option into modetest to ease
> the use of this drm property (support of hexadecimal values for properties).
(For the record, modeset doesn't count as a real-world user-space usage: it's
just a toy implementation, just a test tool.)
Simon
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-09 9:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 8:48 [PATCH 0/2] Add "BACKGROUND_COLOR" drm property Raphael GALLAIS-POU - foss
2021-07-07 8:48 ` [PATCH 1/2] drm: add crtc background color property Raphael GALLAIS-POU - foss
2021-07-09 8:04 ` Pekka Paalanen
2021-07-09 16:23 ` Raphael Gallais-Pou
2021-07-12 8:03 ` Pekka Paalanen
2021-07-12 16:15 ` Harry Wentland
2021-07-13 7:52 ` Pekka Paalanen
2021-07-13 13:54 ` Harry Wentland
2021-07-14 7:35 ` Pekka Paalanen
2021-07-14 16:13 ` Harry Wentland
2021-07-15 9:34 ` Pekka Paalanen
2021-07-15 18:10 ` Harry Wentland
2021-07-07 8:48 ` [PATCH 2/2] drm/stm: ltdc: add crtc background color property support Raphael GALLAIS-POU - foss
2021-07-09 7:36 ` Pekka Paalanen
2021-07-07 9:03 ` [PATCH 0/2] Add "BACKGROUND_COLOR" drm property Simon Ser
2021-07-07 11:42 ` Daniel Vetter
2021-07-09 9:09 ` Raphael Gallais-Pou
2021-07-09 9:23 ` Simon Ser [this message]
2021-07-12 15:50 ` Raphael Gallais-Pou
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='OMOzHvru0iqQzq7rTSqJtI0P9wKSBLATuflwj10xgHvSgJ49V522CaDkIiZ0wWHJw-F5GPQxeO8cKO5ACMXggtDNlfx5TAa0zRObj7wsHHg=@emersion.fr' \
--to=contact@emersion.fr \
--cc=airlied@linux.ie \
--cc=alexandre.torgue@foss.st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.d.roper@intel.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mripard@kernel.org \
--cc=philippe.cornu@foss.st.com \
--cc=philippe.cornu@st.com \
--cc=raphael.gallais-pou@foss.st.com \
--cc=raphael.gallais-pou@st.com \
--cc=tzimmermann@suse.de \
--cc=yannick.fertre@foss.st.com \
--cc=yannick.fertre@st.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;
as well as URLs for NNTP newsgroup(s).