All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/xe: Use XE_BO_FLAG_NEEDS_WC_CPU for DSB
Date: Mon, 23 Sep 2024 20:52:46 -0700	[thread overview]
Message-ID: <85jzf1g12p.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20240920190107.156914-2-maarten.lankhorst@linux.intel.com>

On Fri, 20 Sep 2024 12:01:07 -0700, Maarten Lankhorst wrote:
>
> Now that we have an explicit flag, we can stop abusing the scanout flag
> for this.
>
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> ---
>  drivers/gpu/drm/xe/display/xe_dsb_buffer.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/display/xe_dsb_buffer.c b/drivers/gpu/drm/xe/display/xe_dsb_buffer.c
> index 9f941fc2e36b..59c5aedefc25 100644
> --- a/drivers/gpu/drm/xe/display/xe_dsb_buffer.c
> +++ b/drivers/gpu/drm/xe/display/xe_dsb_buffer.c
> @@ -47,7 +47,7 @@ bool intel_dsb_buffer_create(struct intel_crtc *crtc, struct intel_dsb_buffer *d
>				   NULL, PAGE_ALIGN(size),
>				   ttm_bo_type_kernel,
>				   XE_BO_FLAG_VRAM_IF_DGFX(xe_device_get_root_tile(xe)) |
> -				   XE_BO_FLAG_SCANOUT | XE_BO_FLAG_GGTT);
> +				   XE_BO_FLAG_NEEDS_WC_CPU | XE_BO_FLAG_GGTT);

Also delete the comment just above the function call above: "Set scanout
flag for WC mapping".

>	if (IS_ERR(obj)) {
>		kfree(vma);
>		return false;
> --
> 2.45.2
>

  reply	other threads:[~2024-09-24  3:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-20 19:01 [PATCH 1/2] drm/xe: Add XE_BO_FLAG_NEEDS_WC_CPU and unify mapping for page tables Maarten Lankhorst
2024-09-20 19:01 ` [PATCH 2/2] drm/xe: Use XE_BO_FLAG_NEEDS_WC_CPU for DSB Maarten Lankhorst
2024-09-24  3:52   ` Dixit, Ashutosh [this message]
2024-09-20 19:07 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe: Add XE_BO_FLAG_NEEDS_WC_CPU and unify mapping for page tables Patchwork
2024-09-20 19:07 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-20 19:08 ` ✓ CI.KUnit: success " Patchwork
2024-09-20 19:20 ` ✓ CI.Build: " Patchwork
2024-09-20 19:22 ` ✓ CI.Hooks: " Patchwork
2024-09-20 19:24 ` ✓ CI.checksparse: " Patchwork
2024-09-20 19:42 ` ✓ CI.BAT: " Patchwork
2024-09-21  0:52 ` ✗ CI.FULL: failure " Patchwork
2024-09-24  3:52 ` [PATCH 1/2] " Dixit, Ashutosh
2024-09-25 23:05 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe: Add XE_BO_FLAG_NEEDS_WC_CPU and unify mapping for page tables. (rev2) Patchwork
2024-09-25 23:05 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-25 23:06 ` ✓ CI.KUnit: success " Patchwork
2024-09-25 23:18 ` ✓ CI.Build: " Patchwork
2024-09-25 23:20 ` ✓ CI.Hooks: " Patchwork
2024-09-25 23:21 ` ✓ CI.checksparse: " Patchwork
2024-09-26  0:00 ` ✓ CI.BAT: " Patchwork
2024-09-26  4:46 ` ✗ CI.FULL: failure " Patchwork
2024-09-26  8:23 ` 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=85jzf1g12p.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.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.