dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Daniel Stone <daniels@collabora.com>,
	Liviu Dudau <liviu.dudau@arm.com>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Tomeu Vizoso <tomeu.vizoso@gmail.com>,
	Daniel Vetter <daniel.vetter@intel.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 16:39:13 +0000	[thread overview]
Message-ID: <20161121163913.GL1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20161121163520.20900-1-daniel.vetter@ffwll.ch>

On Mon, Nov 21, 2016 at 05:35:20PM +0100, Daniel Vetter wrote:
> I totally butcherd the job on typing the kernel-doc for these, and no
> one realized. Noticed by Russell. Maarten has a more complete approach
> to this confusion, by making it more explicit what the new/old state
> is, instead of this magic switching behaviour.

Thanks for fixing this.  I noticed a couple of mistakes while reading
through the patch:

> diff --git a/include/drm/drm_modeset_helper_vtables.h b/include/drm/drm_modeset_helper_vtables.h
> index 72478cf82147..e96d662ea572 100644
> --- a/include/drm/drm_modeset_helper_vtables.h
> +++ b/include/drm/drm_modeset_helper_vtables.h
> @@ -999,10 +999,14 @@ struct drm_mode_config_helper_funcs {
>  	 * to implement blocking and nonblocking commits easily. It is not used
>  	 * by the atomic helpers
>  	 *
> -	 * This hook should first commit the given atomic state to the hardware.
> -	 * But drivers can add more waiting calls at the start of their
> -	 * implementation, e.g. to wait for driver-internal request for implicit
> -	 * syncing, before starting to commit the update to the hardware.
> +	 * This function is called when the new atomic state has already been
> +	 * swapped into the various state pointers. The the passed in state therefore contains

"The the".  It also goes way over 80 columns.

> +	 * copies of the old/previous state. This hook should commit the new
> +	 * state into hardware. Note that the helpers have already waited for
> +	 * preceedning atomic commits and fences, but drivers can add more

"preceeding"

> +	 * waiting calls at the start of their implementation, e.g. to wait for
> +	 * driver-internal request for implicit syncing, before starting to
> +	 * commit the update to the hardware.
>  	 *
>  	 * After the atomic update is committed to the hardware this hook needs
>  	 * to call drm_atomic_helper_commit_hw_done(). Then wait for the upate
> -- 
> 2.10.2
> 

-- 
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

  reply	other threads:[~2016-11-21 16:39 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 [this message]
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
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=20161121163913.GL1041@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox