From: Ramalingam C <ramalingam.c@intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Cc: igt-dev@lists.freedesktop.org, jani.nikula@intel.com,
petri.latvala@intel.com, martin.peres@intel.com
Subject: Re: [igt-dev] [RFC i-g-t 2/2] tests/kms_content_protection: Remove pre-existing SRM table before the test
Date: Mon, 1 Jun 2020 16:16:08 +0530 [thread overview]
Message-ID: <20200601104608.GB20219@intel.com> (raw)
In-Reply-To: <20200601084000.31583-3-ankit.k.nautiyal@intel.com>
On 2020-06-01 at 14:10:00 +0530, Ankit Nautiyal wrote:
> This is to check the case with missing SRM, which should be treated as
> device with no revoked keys.
>
> Kernel patch fixing such a bug :
> https://patchwork.freedesktop.org/patch/361346/?series=75939&rev=2
>
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
> tests/kms_content_protection.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
> index a6a64a28..832c9077 100644
> --- a/tests/kms_content_protection.c
> +++ b/tests/kms_content_protection.c
> @@ -75,6 +75,8 @@ __u8 facsimile_srm[] = {
> 0x83, 0xAA, 0xC2, 0x5B, 0x24, 0xB3, 0x36, 0x84, 0x94, 0x75, 0x34, 0xDB,
> 0x10, 0x9E, 0x3B, 0x23, 0x13, 0xD8, 0x7A, 0xC2, 0x30, 0x79, 0x84};
>
> +const char *srm_fw = "/lib/firmware/display_hdcp_srm.bin";
> +
> static void flip_handler(int fd, unsigned int sequence, unsigned int tv_sec,
> unsigned int tv_usec, void *_data)
> {
> @@ -438,8 +440,7 @@ static bool write_srm_as_fw(const __u8 *srm, int len)
> {
> int fd, ret, total = 0;
>
> - fd = open("/lib/firmware/display_hdcp_srm.bin",
> - O_WRONLY | O_CREAT, S_IRWXU);
> + fd = open(srm_fw, O_WRONLY | O_CREAT, S_IRWXU);
> do {
> ret = write(fd, srm + total, len - total);
> if (ret < 0)
> @@ -783,6 +784,11 @@ igt_main
> data.drm_fd = drm_open_driver_master(DRIVER_ANY);
>
> igt_display_require(&data.display, data.drm_fd);
> +
> + /* Remove pre-existing srm table */
> + if (access(srm_fw, F_OK) == 0)
> + igt_assert_f(!remove(srm_fw),
> + "Failed to delete previous srm table\n");
Looks good to me.
Reviewed-by: Ramalingam C <ramalingam.c@intel.com>
> }
>
> for (i = 0; i < ARRAY_SIZE(hdcp_protocol); i++) {
> --
> 2.17.1
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-06-01 10:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 8:39 [igt-dev] [RFC i-g-t 0/2] tests/kms_content_protection: Enhancements Ankit Nautiyal
2020-06-01 8:39 ` [igt-dev] [RFC i-g-t 1/2] tests/kms_content_protection: Bifurcate tests into HDCP1.4 & 2.2 Ankit Nautiyal
2020-06-01 10:41 ` Ramalingam C
2020-06-08 8:37 ` Nautiyal, Ankit K
2020-06-01 8:40 ` [igt-dev] [RFC i-g-t 2/2] tests/kms_content_protection: Remove pre-existing SRM table before the test Ankit Nautiyal
2020-06-01 10:46 ` Ramalingam C [this message]
2020-06-01 9:16 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_content_protection: Enhancements (rev2) Patchwork
2020-06-01 11:33 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=20200601104608.GB20219@intel.com \
--to=ramalingam.c@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=martin.peres@intel.com \
--cc=petri.latvala@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