From: Daniel Vetter <daniel@ffwll.ch>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
daniel.vetter@ffwll.ch, Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: HDCP state handling in ddi_update_pipe
Date: Thu, 7 Feb 2019 08:01:36 +0100 [thread overview]
Message-ID: <20190207070136.GN3271@phenom.ffwll.local> (raw)
In-Reply-To: <1549295080-18353-1-git-send-email-ramalingam.c@intel.com>
On Mon, Feb 04, 2019 at 09:14:40PM +0530, Ramalingam C wrote:
> The downgrade of the fullmodeset into fastset
> intel_encoder->update_pipe, in possible scenario, skips the En/Dis-able
> DDI. Hence breaks the HDCP state change handling.
>
> We also don't have any hdcp tests in CI, because the shard runs don't
> have hdcp capable outputs :-/
>
> So this change fixs it by handling the HDCP state change request at
> intel_encoder->update_pipe too along with enable and disable of the DDI.
>
> Fixes: d19f958db23c ("drm/i915: Enable fastset for non-boot modesets.")
>
> v2:
> Added commit id that broke the HDCP [Daniel]
>
> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> cc: Hans de Goede <hdegoede@redhat.com>
> cc: Daniel Vetter <daniel.vetter@intel.com>
Applied because regression fix, but we still need the igt side to make
sure CI exercises both paths consistently.
-Daniel
> ---
> drivers/gpu/drm/i915/intel_ddi.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
> index ca705546a0ab..2323b7cb1d38 100644
> --- a/drivers/gpu/drm/i915/intel_ddi.c
> +++ b/drivers/gpu/drm/i915/intel_ddi.c
> @@ -3568,6 +3568,13 @@ static void intel_ddi_update_pipe(struct intel_encoder *encoder,
> {
> if (!intel_crtc_has_type(crtc_state, INTEL_OUTPUT_HDMI))
> intel_ddi_update_pipe_dp(encoder, crtc_state, conn_state);
> +
> + if (conn_state->content_protection ==
> + DRM_MODE_CONTENT_PROTECTION_DESIRED)
> + intel_hdcp_enable(to_intel_connector(conn_state->connector));
> + else if (conn_state->content_protection ==
> + DRM_MODE_CONTENT_PROTECTION_UNDESIRED)
> + intel_hdcp_disable(to_intel_connector(conn_state->connector));
> }
>
> static void intel_ddi_set_fia_lane_count(struct intel_encoder *encoder,
> --
> 2.7.4
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-02-07 7:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 13:15 [PATCH] drm/i915: HDCP state handling in ddi_update_pipe Ramalingam C
2019-02-04 14:41 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-02-04 15:44 ` [PATCH] " Ramalingam C
2019-02-04 16:43 ` Maarten Lankhorst
2019-02-04 16:51 ` C, Ramalingam
2019-02-04 17:04 ` Maarten Lankhorst
2019-02-04 17:22 ` C, Ramalingam
2019-02-06 21:24 ` C, Ramalingam
2019-02-07 7:01 ` Daniel Vetter [this message]
2019-02-04 16:26 ` ✓ Fi.CI.BAT: success for drm/i915: HDCP state handling in ddi_update_pipe (rev2) Patchwork
2019-02-04 17:45 ` ✓ Fi.CI.IGT: success for drm/i915: HDCP state handling in ddi_update_pipe Patchwork
2019-02-04 17:57 ` ✓ Fi.CI.IGT: success for drm/i915: HDCP state handling in ddi_update_pipe (rev2) Patchwork
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=20190207070136.GN3271@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=ramalingam.c@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 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.