Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Jessica Zhang <quic_jesszhan@quicinc.com>,
	freedreno@lists.freedesktop.org
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	robdclark@gmail.com, seanpaul@chromium.org, swboyd@chromium.org,
	quic_abhinavk@quicinc.com, contact@emersion.fr,
	daniel.vetter@ffwll.ch, laurent.pinchart@ideasonboard.com,
	ppaalanen@gmail.com, sebastian.wick@redhat.com,
	wayland-devel@lists.freedesktop.org,
	ville.syrjala@linux.intel.com
Subject: Re: [RFC PATCH v3 1/3] drm: Introduce solid fill property for drm plane
Date: Thu, 5 Jan 2023 04:12:21 +0200	[thread overview]
Message-ID: <34880c9e-6150-5a90-ed0e-5dcdc862f2b8@linaro.org> (raw)
In-Reply-To: <20230104234036.636-2-quic_jesszhan@quicinc.com>

On 05/01/2023 01:40, Jessica Zhang wrote:
> Add support for solid_fill property to drm_plane. In addition, add
> support for setting and getting the values for solid_fill.
> 
> solid_fill holds data for supporting solid fill planes. The property
> accepts an RGB323232 value and the driver data is formatted as such:
> 
> struct drm_solid_fill {
> 	u32 r;
> 	u32 g;
> 	u32 b;
> };
> 
> To enable solid fill planes, userspace must assigned solid_fill to a
> property blob containing the following information:
> 
> struct drm_solid_fill_info {
> 	u8 version;
> 	u32 r, g, b;

BTW: should we add support for alpha too? DPU hardware supports using 
RGBA as a fill colour format, doesn't it?

But then we face the obvious question, how do we communicate to 
userspace if the hardware support RGB or RGBA?

> };
> 
> Changes in V2:
> - Changed solid_fill property to a property blob (Simon, Dmitry)
> - Added drm_solid_fill struct (Simon)
> - Added drm_solid_fill_info struct (Simon)
> 
> Changes in V3:
> - Corrected typo in drm_solid_fill struct documentation
> 
> Signed-off-by: Jessica Zhang <quic_jesszhan@quicinc.com>
> ---
>   drivers/gpu/drm/drm_atomic_state_helper.c |  9 ++++
>   drivers/gpu/drm/drm_atomic_uapi.c         | 59 +++++++++++++++++++++++
>   drivers/gpu/drm/drm_blend.c               | 17 +++++++
>   include/drm/drm_blend.h                   |  1 +
>   include/drm/drm_plane.h                   | 43 +++++++++++++++++
>   5 files changed, 129 insertions(+)

-- 
With best wishes
Dmitry


  parent reply	other threads:[~2023-01-05  2:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 23:40 [RFC PATCH v3 0/3] Support for Solid Fill Planes Jessica Zhang
2023-01-04 23:40 ` [RFC PATCH v3 1/3] drm: Introduce solid fill property for drm plane Jessica Zhang
2023-01-05  1:50   ` Dmitry Baryshkov
2023-01-05  2:12   ` Dmitry Baryshkov [this message]
2023-01-18 18:57   ` Harry Wentland
2023-01-18 22:53     ` Jessica Zhang
2023-01-19 15:57       ` Harry Wentland
2023-01-19 16:24         ` Jessica Zhang
2023-01-19 16:27           ` Harry Wentland
2023-01-04 23:40 ` [RFC PATCH v3 2/3] drm: Adjust atomic checks for solid fill color Jessica Zhang
2023-01-05  1:57   ` Dmitry Baryshkov
2023-01-06 20:51     ` Jessica Zhang
2023-01-04 23:40 ` [RFC PATCH v3 3/3] drm/msm/dpu: Use color_fill property for DPU planes Jessica Zhang
2023-01-05  2:16   ` Dmitry Baryshkov
2023-01-06 20:57     ` [Freedreno] " Jessica Zhang
2023-01-06 21:56       ` Dmitry Baryshkov
2023-01-05 11:33 ` [RFC PATCH v3 0/3] Support for Solid Fill Planes Daniel Vetter
2023-01-06  0:37   ` Jessica Zhang
2023-01-06  3:43     ` Dmitry Baryshkov
2023-01-06 18:41       ` Daniel Vetter
2023-01-06 21:49         ` Dmitry Baryshkov
2023-01-07  0:33           ` Abhinav Kumar
2023-01-11 22:29             ` Daniel Vetter
2023-01-24 10:42               ` Simon Ser
2023-01-31  9:25           ` Pekka Paalanen
2023-01-31 10:06             ` Simon Ser
2023-01-31 11:13               ` Pekka Paalanen
2023-01-31 11:21                 ` Simon Ser
2023-01-31 12:49                   ` Pekka Paalanen
2023-02-02  2:06                     ` Jessica Zhang
2023-02-02  8:55                       ` Pekka Paalanen
2023-01-06 19:44       ` Jessica Zhang

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=34880c9e-6150-5a90-ed0e-5dcdc862f2b8@linaro.org \
    --to=dmitry.baryshkov@linaro.org \
    --cc=contact@emersion.fr \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=ppaalanen@gmail.com \
    --cc=quic_abhinavk@quicinc.com \
    --cc=quic_jesszhan@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=seanpaul@chromium.org \
    --cc=sebastian.wick@redhat.com \
    --cc=swboyd@chromium.org \
    --cc=ville.syrjala@linux.intel.com \
    --cc=wayland-devel@lists.freedesktop.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