From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 1/7] drm/i915/display: support struct intel_atomic_state in to_intel_display()
Date: Thu, 15 Aug 2024 15:03:26 -0400 [thread overview]
Message-ID: <Zr5Q_jEQbpwUwGSk@intel.com> (raw)
In-Reply-To: <20240813164123.2674462-1-jani.nikula@intel.com>
On Tue, Aug 13, 2024 at 07:41:17PM +0300, Jani Nikula wrote:
> Add support for converting struct intel_atomic_state pointers to struct
> intel_display pointers.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_display_types.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h b/drivers/gpu/drm/i915/display/intel_display_types.h
> index ea6548ceab2f..bd290536a1b7 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_types.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_types.h
> @@ -2206,6 +2206,8 @@ to_intel_frontbuffer(struct drm_framebuffer *fb)
> */
> #define __drm_device_to_intel_display(p) \
> (&to_i915(p)->display)
> +#define __intel_atomic_state_to_intel_display(p) \
> + __drm_device_to_intel_display((p)->base.dev)
> #define __intel_connector_to_intel_display(p) \
> __drm_device_to_intel_display((p)->base.dev)
> #define __intel_crtc_to_intel_display(p) \
> @@ -2229,6 +2231,7 @@ to_intel_frontbuffer(struct drm_framebuffer *fb)
> #define to_intel_display(p) \
> _Generic(*p, \
> __assoc(drm_device, p), \
> + __assoc(intel_atomic_state, p), \
> __assoc(intel_connector, p), \
> __assoc(intel_crtc, p), \
> __assoc(intel_crtc_state, p), \
> --
> 2.39.2
>
next prev parent reply other threads:[~2024-08-15 19:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 16:41 [PATCH 1/7] drm/i915/display: support struct intel_atomic_state in to_intel_display() Jani Nikula
2024-08-13 16:41 ` [PATCH 2/7] drm/i915/display: convert intel_link_bw.c to struct intel_display Jani Nikula
2024-08-15 19:03 ` Rodrigo Vivi
2024-08-13 16:41 ` [PATCH 3/7] drm/i915/display: convert intel_load_detect.c " Jani Nikula
2024-08-15 19:04 ` Rodrigo Vivi
2024-08-15 19:06 ` Rodrigo Vivi
2024-08-15 19:06 ` Rodrigo Vivi
2024-08-13 16:41 ` [PATCH 4/7] drm/i915/alpm: convert " Jani Nikula
2024-08-15 19:14 ` Rodrigo Vivi
2024-08-13 16:41 ` [PATCH 5/7] drm/i915/lspcon: " Jani Nikula
2024-08-15 19:15 ` Rodrigo Vivi
2024-08-13 16:41 ` [PATCH 6/7] drm/i915/display: convert dp aux backlight " Jani Nikula
2024-08-15 19:16 ` Rodrigo Vivi
2024-08-13 16:41 ` [PATCH 7/7] drm/i915/hti: convert " Jani Nikula
2024-08-15 19:16 ` Rodrigo Vivi
2024-08-13 16:46 ` ✓ CI.Patch_applied: success for series starting with [1/7] drm/i915/display: support struct intel_atomic_state in to_intel_display() Patchwork
2024-08-13 16:47 ` ✓ CI.checkpatch: " Patchwork
2024-08-13 16:48 ` ✓ CI.KUnit: " Patchwork
2024-08-13 17:00 ` ✓ CI.Build: " Patchwork
2024-08-13 17:02 ` ✓ CI.Hooks: " Patchwork
2024-08-13 17:03 ` ✗ CI.checksparse: warning " Patchwork
2024-08-13 17:27 ` ✓ CI.BAT: success " Patchwork
2024-08-13 20:41 ` ✗ CI.FULL: failure " Patchwork
2024-08-15 19:03 ` Rodrigo Vivi [this message]
2024-08-16 8:22 ` [PATCH 1/7] " Jani Nikula
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=Zr5Q_jEQbpwUwGSk@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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