From: Daniel Vetter <daniel@ffwll.ch>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/todo: Add item about modeset properties
Date: Thu, 4 Jun 2020 09:30:49 +0200 [thread overview]
Message-ID: <20200604073049.GS20149@phenom.ffwll.local> (raw)
In-Reply-To: <20200603170434.2363446-1-emil.l.velikov@gmail.com>
On Wed, Jun 03, 2020 at 06:04:34PM +0100, Emil Velikov wrote:
> Add some information about pre-atomic modeset properties alongside a
> list of suggestions how to handle the different instances.
>
> Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
> ---
> Documentation/gpu/todo.rst | 32 ++++++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
> diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
> index 658b52f7ffc6..6648fd13cc1e 100644
> --- a/Documentation/gpu/todo.rst
> +++ b/Documentation/gpu/todo.rst
> @@ -392,6 +392,38 @@ Contact: Laurent Pinchart, respective driver maintainers
>
> Level: Intermediate
>
> +Consolidate custom driver modeset properties
> +--------------------------------------------
> +
> +Before atomic modeset took place, many drivers where creating their own
> +properties. Among other things, atomic brought the requirement that custom,
> +driver specific properties should not be used.
> +
> +In for this task, we aim to introduce core helper or reuse the existing ones
s/In for/For/ I think ...
> +if available:
> +
> +A quick, unconfirmed, examples list.
> +
> +Introduce core helpers:
> +- audio (amdgpu, intel, gma500, radeon)
> +- brightness, contrast, etc (armada, nouveau) - overlay only (?)
> +- broadcast rgb (gma500, intel)
> +- colorkey (armada, nouveau, rcar) - overlay only (?)
> +- dither (amdgpu, nouveau, radeon) - varies across drivers
> +- underscan family (amdgpu, radeon, nouveau)
> +
> +Already in core:
> +- colorspace (sti)
> +- tv format names, enhancements (gma500, intel)
> +- tv overscan, margins, etc. (gma500, intel)
> +- zorder (omapdrm) - same as zpos (?)
> +
> +
> +Contact: Emil Velikov, respective driver maintainers
> +
> +Level: Intermediate
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> +
> +
> Core refactorings
> =================
>
> --
> 2.25.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-06-04 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 17:04 [PATCH] drm/todo: Add item about modeset properties Emil Velikov
2020-06-04 7:30 ` Daniel Vetter [this message]
2020-06-15 19:23 ` Emil Velikov
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=20200604073049.GS20149@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.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).