From: "Souza, Jose" <jose.souza@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>
Subject: Re: [PATCH 2/5] drm/i915: add wrappers to get intel connector state
Date: Fri, 1 Nov 2019 00:26:11 +0000 [thread overview]
Message-ID: <de5cf843eaff41e18b6c4e655ae3a77034dbcf6d.camel@intel.com> (raw)
In-Reply-To: <20191030012448.14937-3-lucas.demarchi@intel.com>
On Tue, 2019-10-29 at 18:24 -0700, Lucas De Marchi wrote:
> Wrap drm_atomic_get_old_connector_state so we can get the
> intel_digital_connector_state and make it easier to migrate to intel
> types.
Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> .../gpu/drm/i915/display/intel_display_types.h | 18
> ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h
> b/drivers/gpu/drm/i915/display/intel_display_types.h
> index 40184e823c84..a550abb48b3c 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_types.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_types.h
> @@ -1527,6 +1527,24 @@ intel_atomic_get_new_crtc_state(struct
> intel_atomic_state *state,
> &crtc-
> >base));
> }
>
> +static inline struct intel_digital_connector_state *
> +intel_atomic_get_new_connector_state(struct intel_atomic_state
> *state,
> + struct intel_connector *connector)
> +{
> + return to_intel_digital_connector_state(
> + drm_atomic_get_new_connector_state(&state-
> >base,
> + &connector->base));
> +}
> +
> +static inline struct intel_digital_connector_state *
> +intel_atomic_get_old_connector_state(struct intel_atomic_state
> *state,
> + struct intel_connector *connector)
> +{
> + return to_intel_digital_connector_state(
> + drm_atomic_get_old_connector_state(&state-
> >base,
> + &connector->base));
> +}
> +
> /* intel_display.c */
> static inline bool
> intel_crtc_has_type(const struct intel_crtc_state *crtc_state,
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: "Souza, Jose" <jose.souza@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>
Subject: Re: [Intel-gfx] [PATCH 2/5] drm/i915: add wrappers to get intel connector state
Date: Fri, 1 Nov 2019 00:26:11 +0000 [thread overview]
Message-ID: <de5cf843eaff41e18b6c4e655ae3a77034dbcf6d.camel@intel.com> (raw)
Message-ID: <20191101002611.uRfB8BMCuBc3yAPO9hksOlOrWFbDYNwjAO060HacmiM@z> (raw)
In-Reply-To: <20191030012448.14937-3-lucas.demarchi@intel.com>
On Tue, 2019-10-29 at 18:24 -0700, Lucas De Marchi wrote:
> Wrap drm_atomic_get_old_connector_state so we can get the
> intel_digital_connector_state and make it easier to migrate to intel
> types.
Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> .../gpu/drm/i915/display/intel_display_types.h | 18
> ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h
> b/drivers/gpu/drm/i915/display/intel_display_types.h
> index 40184e823c84..a550abb48b3c 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_types.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_types.h
> @@ -1527,6 +1527,24 @@ intel_atomic_get_new_crtc_state(struct
> intel_atomic_state *state,
> &crtc-
> >base));
> }
>
> +static inline struct intel_digital_connector_state *
> +intel_atomic_get_new_connector_state(struct intel_atomic_state
> *state,
> + struct intel_connector *connector)
> +{
> + return to_intel_digital_connector_state(
> + drm_atomic_get_new_connector_state(&state-
> >base,
> + &connector->base));
> +}
> +
> +static inline struct intel_digital_connector_state *
> +intel_atomic_get_old_connector_state(struct intel_atomic_state
> *state,
> + struct intel_connector *connector)
> +{
> + return to_intel_digital_connector_state(
> + drm_atomic_get_old_connector_state(&state-
> >base,
> + &connector->base));
> +}
> +
> /* intel_display.c */
> static inline bool
> intel_crtc_has_type(const struct intel_crtc_state *crtc_state,
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-01 0:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 1:24 [PATCH 0/5] tgl: MST support Lucas De Marchi
2019-10-30 1:24 ` [Intel-gfx] " Lucas De Marchi
2019-10-30 1:24 ` [PATCH 1/5] drm/i915: Add for_each_new_intel_connector_in_state() Lucas De Marchi
2019-10-30 1:24 ` [Intel-gfx] " Lucas De Marchi
2019-10-30 1:24 ` [PATCH 2/5] drm/i915: add wrappers to get intel connector state Lucas De Marchi
2019-10-30 1:24 ` [Intel-gfx] " Lucas De Marchi
2019-11-01 0:26 ` Souza, Jose [this message]
2019-11-01 0:26 ` Souza, Jose
2019-10-30 1:24 ` [PATCH 3/5] drm/i915/tgl: do not enable transcoder clock twice on MST Lucas De Marchi
2019-10-30 1:24 ` [Intel-gfx] " Lucas De Marchi
2019-11-01 0:37 ` Souza, Jose
2019-11-01 0:37 ` [Intel-gfx] " Souza, Jose
2019-10-30 1:24 ` [PATCH 4/5] drm/i915: avoid reading DP_TP_CTL twice Lucas De Marchi
2019-10-30 1:24 ` [Intel-gfx] " Lucas De Marchi
2019-11-01 0:39 ` Souza, Jose
2019-11-01 0:39 ` [Intel-gfx] " Souza, Jose
2019-10-30 1:24 ` [PATCH 5/5] drm/i915/tgl: Select master transcoder in DP MST Lucas De Marchi
2019-10-30 1:24 ` [Intel-gfx] " Lucas De Marchi
2019-10-30 3:24 ` ✗ Fi.CI.CHECKPATCH: warning for tgl: MST support Patchwork
2019-10-30 3:24 ` [Intel-gfx] " Patchwork
2019-10-30 3:27 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-10-30 3:27 ` [Intel-gfx] " Patchwork
2019-10-30 3:51 ` ✓ Fi.CI.BAT: success " Patchwork
2019-10-30 3:51 ` [Intel-gfx] " Patchwork
2019-10-31 8:00 ` ✓ Fi.CI.IGT: " Patchwork
2019-10-31 8:00 ` [Intel-gfx] " Patchwork
2019-11-01 0:43 ` [PATCH 0/5] " Souza, Jose
2019-11-01 0:43 ` [Intel-gfx] " Souza, Jose
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=de5cf843eaff41e18b6c4e655ae3a77034dbcf6d.camel@intel.com \
--to=jose.souza@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@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