All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>,
	laurent.pinchart@ideasonboard.com, daniel@ffwll.ch,
	airlied@linux.ie
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v4 0/6] drm: zpos normalization cleanup and omapdrm to use it
Date: Wed, 28 Mar 2018 12:30:52 +0300	[thread overview]
Message-ID: <ac34ebd8-4674-a2e7-a12e-64a8af2591ac@ti.com> (raw)
In-Reply-To: <20180206120556.30495-1-peter.ujfalusi@ti.com>

Hi,

On 06/02/18 14:05, Peter Ujfalusi wrote:
> Hi,
> 
> Changes since v3:
> - Moved the new normalize_zpos bool to be around another bools
> - Extended the commit message for sti that the drm_atomic_helper_check() is
>   going to ask for async_update due to the legacy cursor usage.
> 
> Changes since v2:
> - Fixed commit messages (s/drm_device/drm_mode_config)
> - Added ack from Benjamin Gaignard to drm/sti patch
> 
> Changes since v1:
> - normalize_zpos flag moved to drm_mode_config
> - Added comment to note the side effect of normalization and updated the comment
>   for normalized_zpos in the header file as well.
> - Added Acked-by from Daniel to patch 2-6 but not for patch 1 as I'm not sure if
>   the comments I have added matches with what is expected to be.
> 
> The first patch is adding a flag to drm_device that drivers can set if they want
> the zpos to be normalized.
> 
> Then convert exynos, tegra, sti and rcar-du to use this flag instead of
> re-implementing the drm_atomic_helper_check() locally just to add the call to
> drm_atomic_normalize_zpos().
> 
> The last patch is moving omapdrm to use the zpos normalization as well to comply
> with the UAPI documentation regarding to zpos.
> 
> Laurent's note in an earlier thread:
> https://marc.info/?l=dri-devel&m=151567355225029&w=2
> 
> "The problem is that zpos normalization requires accessing the state of all 
> enabled planes for a CRTC in order to compute (and store) the normalized zpos 
> values. This thus forces all planes to be added to the commit state, even when 
> the commit doesn't touch the zpos property. I assume this caused issues 
> (possibly performance issues) in drivers that then performed hardware setup of 
> all planes as a result."
> 
> can be addressed later in the core for all users of drm_atomic_normalize_zpos()

Thanks. I think this looks fine, I'll push via drm-misc.

 Tomi

-- 
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-03-28  9:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 12:05 [PATCH v4 0/6] drm: zpos normalization cleanup and omapdrm to use it Peter Ujfalusi
2018-02-06 12:05 ` [PATCH v4 1/6] drm: Add drm_mode_config->normalize_zpos boolean Peter Ujfalusi
2018-02-06 12:05 ` [PATCH v4 2/6] drm/exynos: Let core take care of normalizing the zpos Peter Ujfalusi
2018-02-06 12:05 ` [PATCH v4 3/6] drm/tegra: " Peter Ujfalusi
2018-02-06 12:05 ` [PATCH v4 4/6] drm/sti: " Peter Ujfalusi
2018-02-06 12:05 ` [PATCH v4 5/6] drm: rcar-du: " Peter Ujfalusi
2018-02-06 12:05 ` [PATCH v4 6/6] drm/omap: Use normalized zpos for plane placement Peter Ujfalusi
2018-03-01  7:31   ` Tomi Valkeinen
2018-03-07  9:18 ` [PATCH v4 0/6] drm: zpos normalization cleanup and omapdrm to use it Peter Ujfalusi
2018-03-28  9:30 ` Tomi Valkeinen [this message]
2018-03-28 12:10   ` Peter Ujfalusi
2018-03-28 12:13     ` Tomi Valkeinen

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=ac34ebd8-4674-a2e7-a12e-64a8af2591ac@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=peter.ujfalusi@ti.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 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.