From: "Ser, Simon" <simon.ser@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"C, Ramalingam" <ramalingam.c@intel.com>
Cc: "Latvala, Petri" <petri.latvala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] lib/display_require: reset hdcp on all connectors
Date: Tue, 13 Aug 2019 14:22:11 +0000 [thread overview]
Message-ID: <819ea7c50585114a55ae76fdcacc76798f845ec9.camel@intel.com> (raw)
In-Reply-To: <20190813070421.17633-1-ramalingam.c@intel.com>
On Tue, 2019-08-13 at 12:34 +0530, Ramalingam C wrote:
> At the start of every test, reset HDCP state to UNDESIRED on all
> connectors, so that we will not have any hdcp related noises in
> the subsequent tests.
>
> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111390
> ---
> lib/igt_kms.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/lib/igt_kms.c b/lib/igt_kms.c
> index b0169f73b752..68650ae3d7e9 100644
> --- a/lib/igt_kms.c
> +++ b/lib/igt_kms.c
> @@ -1859,6 +1859,10 @@ static void igt_output_reset(igt_output_t *output)
> if (igt_output_has_prop(output, IGT_CONNECTOR_BROADCAST_RGB))
> igt_output_set_prop_value(output, IGT_CONNECTOR_BROADCAST_RGB,
> BROADCAST_RGB_FULL);
> +
> + if (igt_output_has_prop(output, IGT_CONNECTOR_CONTENT_PROTECTION))
> + igt_output_set_prop_value(output, IGT_CONNECTOR_CONTENT_PROTECTION,
> + 0);
This hardcodes UNDESIRED's value. Maybe we can use
igt_output_set_prop_enum instead?
> }
>
> /**
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-08-13 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 7:04 [igt-dev] [PATCH i-g-t] lib/display_require: reset hdcp on all connectors Ramalingam C
2019-08-13 14:22 ` Ser, Simon [this message]
2019-08-13 15:24 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-08-13 23:24 ` [igt-dev] ✓ Fi.CI.IGT: " 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=819ea7c50585114a55ae76fdcacc76798f845ec9.camel@intel.com \
--to=simon.ser@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox