From: Jani Nikula <jani.nikula@linux.intel.com>
To: Damien Lespiau <damien.lespiau@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/4] drm/i915: Introduce a for_each_crtc() macro
Date: Wed, 14 May 2014 11:56:12 +0300 [thread overview]
Message-ID: <874n0s3fir.fsf@intel.com> (raw)
In-Reply-To: <1400020344-17248-4-git-send-email-damien.lespiau@intel.com>
On Wed, 14 May 2014, Damien Lespiau <damien.lespiau@intel.com> wrote:
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
> ---
> drivers/gpu/drm/i915/i915_drv.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index edf7299..4006dfe 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -163,6 +163,9 @@ enum hpd_pin {
> #define for_each_pipe(p) for ((p) = 0; (p) < INTEL_INFO(dev)->num_pipes; (p)++)
> #define for_each_sprite(p, s) for ((s) = 0; (s) < INTEL_INFO(dev)->num_sprites[(p)]; (s)++)
>
> +#define for_each_crtc(dev, crtc) \
> + list_for_each_entry(crtc, &dev->mode_config.crtc_list, head)
> +
Would this be useful in some drm header as drm_for_each_crtc()?
BR,
Jani.
> #define for_each_intel_crtc(dev, intel_crtc) \
> list_for_each_entry(intel_crtc, &dev->mode_config.crtc_list, base.head)
>
> --
> 1.8.3.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-05-14 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 22:32 [PATCH 0/4] for_each_{intel_,}crtc v2 Damien Lespiau
2014-05-13 22:32 ` [PATCH 1/4] drm/i915: Introduce a for_each_intel_crtc() macro Damien Lespiau
2014-05-13 22:32 ` [PATCH 2/4] drm/i915: Use for_each_intel_crtc() when iterating through intel_crtcs Damien Lespiau
2014-05-13 22:32 ` [PATCH 3/4] drm/i915: Introduce a for_each_crtc() macro Damien Lespiau
2014-05-14 8:56 ` Jani Nikula [this message]
2014-05-13 22:32 ` [PATCH 4/4] drm/i915: Use for_each_crtc() when iterating through the CRTCs Damien Lespiau
2014-05-13 22:40 ` [PATCH 0/4] for_each_{intel_,}crtc v2 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=874n0s3fir.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=damien.lespiau@intel.com \
--cc=intel-gfx@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 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.