Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Shankar, Uma" <uma.shankar@intel.com>
To: "Manna, Animesh" <animesh.manna@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "Das, Nirmoy" <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dsb: modified to drm_info in dsb_prepare()
Date: Tue, 5 Apr 2022 11:44:33 +0000	[thread overview]
Message-ID: <e23dbc95903a4e2eab4fcffa5be6b2cc@intel.com> (raw)
In-Reply-To: <20220325161140.11906-1-animesh.manna@intel.com>



> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Animesh
> Manna
> Sent: Friday, March 25, 2022 9:42 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Das, Nirmoy <nirmoy.das@intel.com>
> Subject: [Intel-gfx] [PATCH] drm/i915/dsb: modified to drm_info in dsb_prepare()
> 
> The request to aqquire gem resources is failing for DSB in rare scenario where it is
> busy and the register programming will be done through mmio fallback path.
> 
> DSB has extra advantage of faster register programming which may go away
> through mmio path. Adding wait for gem resource also may not be right as anyways
> losing time.
> 
> To make the CI execution happy replaced drm_err() to drm_info() for printing debug
> info during dsb buffer preparation.
> 
> v1: Initial version.
> v2: Added print for mmio fallback at out label. [Nirmoy]
> v3: Improved debug message. [Nirmoy]

Pushed to drm-intel-next. Thanks for the patch and reviews.

Regards,
Uma Shankar

> Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
> Cc: Nirmoy Das <nirmoy.das@linux.intel.com>
> Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_dsb.c | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_dsb.c
> b/drivers/gpu/drm/i915/display/intel_dsb.c
> index b34a67309976..c4affcb216fd 100644
> --- a/drivers/gpu/drm/i915/display/intel_dsb.c
> +++ b/drivers/gpu/drm/i915/display/intel_dsb.c
> @@ -283,14 +283,12 @@ void intel_dsb_prepare(struct intel_crtc_state
> *crtc_state)
> 
>  	obj = i915_gem_object_create_internal(i915, DSB_BUF_SIZE);
>  	if (IS_ERR(obj)) {
> -		drm_err(&i915->drm, "Gem object creation failed\n");
>  		kfree(dsb);
>  		goto out;
>  	}
> 
>  	vma = i915_gem_object_ggtt_pin(obj, NULL, 0, 0, 0);
>  	if (IS_ERR(vma)) {
> -		drm_err(&i915->drm, "Vma creation failed\n");
>  		i915_gem_object_put(obj);
>  		kfree(dsb);
>  		goto out;
> @@ -298,7 +296,6 @@ void intel_dsb_prepare(struct intel_crtc_state *crtc_state)
> 
>  	buf = i915_gem_object_pin_map_unlocked(vma->obj, I915_MAP_WC);
>  	if (IS_ERR(buf)) {
> -		drm_err(&i915->drm, "Command buffer creation failed\n");
>  		i915_vma_unpin_and_release(&vma, I915_VMA_RELEASE_MAP);
>  		kfree(dsb);
>  		goto out;
> @@ -311,6 +308,10 @@ void intel_dsb_prepare(struct intel_crtc_state *crtc_state)
>  	dsb->ins_start_offset = 0;
>  	crtc_state->dsb = dsb;
>  out:
> +	if (!crtc_state->dsb)
> +		drm_info(&i915->drm,
> +			 "DSB queue setup failed, will fallback to MMIO for display
> HW
> +programming\n");
> +
>  	intel_runtime_pm_put(&i915->runtime_pm, wakeref);  }
> 
> --
> 2.29.0


  parent reply	other threads:[~2022-04-05 11:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25 16:11 [Intel-gfx] [PATCH] drm/i915/dsb: modified to drm_info in dsb_prepare() Animesh Manna
2022-03-25 19:07 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915/dsb: modified to drm_info in dsb_prepare() (rev3) Patchwork
2022-03-25 19:30 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-04-01 15:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-01 17:05 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-04-01 22:22 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2022-04-01 22:30 ` Patchwork
2022-04-05 11:44 ` Shankar, Uma [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-25 14:28 [Intel-gfx] [PATCH] drm/i915/dsb: modified to drm_info in dsb_prepare() Animesh Manna
2022-03-25 14:58 ` Das, Nirmoy
2022-03-24  7:43 Animesh Manna
2022-03-24  9:08 ` Das, Nirmoy
2022-03-25 13:22   ` Manna, Animesh
2022-03-25 13:39     ` Das, Nirmoy

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=e23dbc95903a4e2eab4fcffa5be6b2cc@intel.com \
    --to=uma.shankar@intel.com \
    --cc=animesh.manna@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nirmoy.das@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