From: Daniel Vetter <daniel@ffwll.ch>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: atomic: fix legacy gamma set helper
Date: Tue, 12 Apr 2016 13:57:57 +0200 [thread overview]
Message-ID: <20160412115757.GF2510@phenom.ffwll.local> (raw)
In-Reply-To: <1460382219-29428-1-git-send-email-lionel.g.landwerlin@intel.com>
On Mon, Apr 11, 2016 at 02:43:39PM +0100, Lionel Landwerlin wrote:
> Color management properties are a bit of an odd use case because
> they're not marked as atomic properties. Currently we're not updating
> the non atomic values so the drm_crtc_state is out of sync with the
> values stored in the crtc object.
tbh sounds like this is the bug here - why does the lookup of the correct
values stored in the crtc_state drm_atomic_crtc_get_property() not work?
Duct-taping over this bug in every place we update these properties
(you're just patching one of many) won't scale.
Also: Where's the igt for this failure?
-Daniel
>
> v2: Update non atomic values only if commit succeeds (Bob Paauwe)
>
> v3: Do not access crtc_state after commit, use crtc->state (Maarten
> Lankhorst)
>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Bob Paauwe <bob.j.paauwe@intel.com>
> Cc: <dri-devel@lists.freedesktop.org>
> Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> ---
> drivers/gpu/drm/drm_atomic_helper.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_atomic_helper.c b/drivers/gpu/drm/drm_atomic_helper.c
> index 7bf678e..13b86cf 100644
> --- a/drivers/gpu/drm/drm_atomic_helper.c
> +++ b/drivers/gpu/drm/drm_atomic_helper.c
> @@ -2979,6 +2979,14 @@ retry:
> if (ret)
> goto fail;
>
> + drm_object_property_set_value(&crtc->base,
> + config->degamma_lut_property, 0);
> + drm_object_property_set_value(&crtc->base,
> + config->ctm_property, 0);
> + drm_object_property_set_value(&crtc->base,
> + config->gamma_lut_property,
> + crtc->state->gamma_lut->base.id);
> +
> /* Driver takes ownership of state on successful commit. */
>
> drm_property_unreference_blob(blob);
> --
> 2.8.0.rc3
>
> _______________________________________________
> 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:[~2016-04-12 11:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 17:17 [PATCH] drm: atomic: fix legacy gamma set helper Lionel Landwerlin
2016-04-08 18:15 ` Bob Paauwe
2016-04-11 10:37 ` Lionel Landwerlin
2016-04-11 10:47 ` Maarten Lankhorst
2016-04-11 13:43 ` Lionel Landwerlin
2016-04-11 17:28 ` Bob Paauwe
2016-04-12 11:57 ` Daniel Vetter [this message]
2016-04-12 12:51 ` Lionel Landwerlin
2016-04-12 16:07 ` Daniel Vetter
2016-04-18 10:07 ` Lionel Landwerlin
2016-04-18 12:39 ` Daniel Vetter
2016-04-09 6:56 ` ✗ Fi.CI.BAT: warning for " Patchwork
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=20160412115757.GF2510@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lionel.g.landwerlin@intel.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