From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Gustavo Padovan <gustavo.padovan@collabora.com>
Cc: Daniel Stone <daniels@collabora.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>,
Tomeu Vizoso <tomeu.vizoso@gmail.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Liviu Dudau <liviu.dudau@arm.com>,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH] drm/atomic: Unconfuse the old_state mess in commmit_tail
Date: Mon, 21 Nov 2016 23:53:55 +0000 [thread overview]
Message-ID: <20161121235355.GR1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20161121235111.GJ32746@joana>
On Tue, Nov 22, 2016 at 08:51:11AM +0900, Gustavo Padovan wrote:
> 2016-11-21 Daniel Vetter <daniel.vetter@ffwll.ch>:
> > /**
> > * drm_atomic_helper_commit_tail - commit atomic update to hardware
> > - * @state: new modeset state to be committed
> > + * @old_state: atomic state object with old state structures
> > *
> > * This is the default implemenation for the ->atomic_commit_tail() hook of the
> > * &drm_mode_config_helper_funcs vtable.
> > @@ -1158,53 +1166,53 @@ EXPORT_SYMBOL(drm_atomic_helper_wait_for_vblanks);
> > *
> > * For drivers supporting runtime PM the recommended sequence is instead ::
> > *
> > - * drm_atomic_helper_commit_modeset_disables(dev, state);
> > + * drm_atomic_helper_commit_modeset_disables(dev, old_state);
> > *
> > - * drm_atomic_helper_commit_modeset_enables(dev, state);
> > + * drm_atomic_helper_commit_modeset_enables(dev, old_state);
> > *
> > - * drm_atomic_helper_commit_planes(dev, state,
> > + * drm_atomic_helper_commit_planes(dev, old_state,
> > * DRM_PLANE_COMMIT_ACTIVE_ONLY);
> > *
> > * for committing the atomic update to hardware. See the kerneldoc entries for
> > * these three functions for more details.
> > */
> > -void drm_atomic_helper_commit_tail(struct drm_atomic_state *state)
> > +void drm_atomic_helper_commit_tail(struct drm_atomic_state *old_state)
>
> I thought we would commit the new state. Why the rename to old_state?
Because the argument is the _old_ state, and the new state can be
found in the various plane, crtc, etc structures.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-11-21 23:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 16:35 [PATCH] drm/atomic: Unconfuse the old_state mess in commmit_tail Daniel Vetter
2016-11-21 16:39 ` Russell King - ARM Linux
2016-11-21 16:52 ` Daniel Vetter
2016-11-21 17:04 ` Liviu Dudau
2016-11-21 17:18 ` Daniel Vetter
2016-11-21 23:51 ` Gustavo Padovan
2016-11-21 23:53 ` Russell King - ARM Linux [this message]
2016-11-22 10:12 ` Daniel Vetter
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=20161121235355.GR1041@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=gustavo.padovan@collabora.com \
--cc=liviu.dudau@arm.com \
--cc=tomeu.vizoso@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 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.