From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: igt-dev <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t v2 1/2] tests/intel_dp_compliance: use device coherent mapping instead of mmap_gtt
Date: Fri, 07 Feb 2020 19:27:23 -0800 [thread overview]
Message-ID: <87zhdtwyg4.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20200207134527.17205-1-ramalingam.c@intel.com>
On Fri, 07 Feb 2020 05:45:26 -0800, Ramalingam C wrote:
>
> As tiling is not used we use the device coherent mapping instead of
> mmap_gtt.
>
> v2:
> instead of skipping device coherent mapping is used. [Ashutosh]
>
> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> ---
> tools/intel_dp_compliance.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/tools/intel_dp_compliance.c b/tools/intel_dp_compliance.c
> index 5cc3d37a71d6..2d42cb1a7b6f 100644
> --- a/tools/intel_dp_compliance.c
> +++ b/tools/intel_dp_compliance.c
> @@ -451,9 +451,9 @@ static int setup_framebuffers(struct connector *dp_conn)
> igt_assert(dp_conn->fb);
>
> /* Map the mapping of GEM object into the virtual address space */
> - dp_conn->pixmap = gem_mmap__gtt(drm_fd,
> + dp_conn->pixmap = gem_mmap__device_coherent(drm_fd,
> dp_conn->fb_video_pattern.gem_handle,
> - dp_conn->fb_video_pattern.size,
> + 0, dp_conn->fb_video_pattern.size,
> PROT_READ | PROT_WRITE);
> if (dp_conn->pixmap == NULL)
> return -1;
> @@ -481,9 +481,9 @@ static int setup_failsafe_framebuffer(struct connector *dp_conn)
> igt_assert(dp_conn->failsafe_fb);
>
> /* Map the mapping of GEM object into the virtual address space */
> - dp_conn->failsafe_pixmap = gem_mmap__gtt(drm_fd,
> + dp_conn->failsafe_pixmap = gem_mmap__device_coherent(drm_fd,
> dp_conn->fb_failsafe_pattern.gem_handle,
> - dp_conn->fb_failsafe_pattern.size,
> + 0, dp_conn->fb_failsafe_pattern.size,
> PROT_READ | PROT_WRITE);
> if (dp_conn->failsafe_pixmap == NULL)
> return -1;
> @@ -518,9 +518,9 @@ static int setup_video_pattern_framebuffer(struct connector *dp_conn)
> igt_assert(dp_conn->test_pattern.fb);
>
> /* Map the mapping of GEM object into the virtual address space */
> - dp_conn->test_pattern.pixmap = gem_mmap__gtt(drm_fd,
> + dp_conn->test_pattern.pixmap = gem_mmap__device_coherent(drm_fd,
> dp_conn->test_pattern.fb_pattern.gem_handle,
> - dp_conn->test_pattern.fb_pattern.size,
> + 0, dp_conn->test_pattern.fb_pattern.size,
> PROT_READ | PROT_WRITE);
> if (dp_conn->test_pattern.pixmap == NULL)
> return -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-02-08 3:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 13:45 [igt-dev] [PATCH i-g-t v2 1/2] tests/intel_dp_compliance: use device coherent mapping instead of mmap_gtt Ramalingam C
2020-02-07 13:45 ` [igt-dev] [PATCH i-g-t v2 2/2] tests/i915_pm_rpm: " Ramalingam C
2020-02-07 14:44 ` Chris Wilson
2020-02-10 5:47 ` Ramalingam C
2020-02-10 6:36 ` Dixit, Ashutosh
2020-02-17 9:40 ` [igt-dev] [PATCH i-g-t] tests/i915_pm_rpm: mmap type based dynamic subtests Ramalingam C
2020-02-17 9:44 ` Ramalingam C
2020-02-18 7:45 ` Chris Wilson
2020-02-18 9:07 ` C, Ramalingam
2020-02-18 10:59 ` Chris Wilson
2020-02-18 11:45 ` Chris Wilson
2020-03-10 3:27 ` [igt-dev] [PATCH i-g-t v2 2/2] tests/i915_pm_rpm: use device coherent mapping instead of mmap_gtt Dixit, Ashutosh
2020-02-07 15:05 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,v2,1/2] tests/intel_dp_compliance: " Patchwork
2020-02-08 3:27 ` Dixit, Ashutosh [this message]
2020-02-10 15:32 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-02-17 11:25 ` [igt-dev] ✗ GitLab.Pipeline: failure for series starting with [i-g-t,v2,1/2] tests/intel_dp_compliance: use device coherent mapping instead of mmap_gtt (rev2) Patchwork
2020-02-17 14:19 ` [igt-dev] ✓ Fi.CI.BAT: success " 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=87zhdtwyg4.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--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