From: "Sharma, Shashank" <shashank.sharma@intel.com>
To: Animesh Manna <animesh.manna@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Michel Thierry <michel.thierry@intel.com>,
Jani Nikula <jani.nikula@intel.com>
Subject: Re: [PATCH v6 06/10] drm/i915/dsb: functions to enable/disable DSB engine.
Date: Thu, 12 Sep 2019 19:04:37 +0530 [thread overview]
Message-ID: <5cf9ca64-e832-e601-7121-7dc384ef7b31@intel.com> (raw)
In-Reply-To: <20190911191133.23383-7-animesh.manna@intel.com>
On 9/12/2019 12:41 AM, Animesh Manna wrote:
> DSB will be used for performance improvement for some special scenario.
> DSB engine will be enabled based on need and after completion of its work
> will be disabled. Api added for enable/disable operation by using DSB_CTRL
> register.
>
> v1: Initial version.
> v2: POSTING_READ added after writing control register. (Shashank)
> v3: cosmetic changes done. (Shashank)
>
> Cc: Michel Thierry <michel.thierry@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Shashank Sharma <shashank.sharma@intel.com>
> Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dsb.c | 40 ++++++++++++++++++++++++
> drivers/gpu/drm/i915/i915_reg.h | 1 +
> 2 files changed, 41 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dsb.c b/drivers/gpu/drm/i915/display/intel_dsb.c
> index b1da2b06263a..2b0ffc0afb74 100644
> --- a/drivers/gpu/drm/i915/display/intel_dsb.c
> +++ b/drivers/gpu/drm/i915/display/intel_dsb.c
> @@ -26,6 +26,46 @@ static inline bool is_dsb_busy(struct intel_dsb *dsb)
> return DSB_STATUS & I915_READ(DSB_CTRL(pipe, dsb->id));
> }
>
> +static inline bool intel_dsb_enable_engine(struct intel_dsb *dsb)
> +{
> + struct intel_crtc *crtc = container_of(dsb, typeof(*crtc), dsb);
> + struct drm_i915_private *dev_priv = to_i915(crtc->base.dev);
> + enum pipe pipe = crtc->pipe;
> + u32 dsb_ctrl;
> +
> + dsb_ctrl = I915_READ(DSB_CTRL(pipe, dsb->id));
> + if (DSB_STATUS & dsb_ctrl) {
> + DRM_DEBUG_KMS("DSB engine is busy.\n");
> + return false;
> + }
> +
> + dsb_ctrl |= DSB_ENABLE;
> + I915_WRITE(DSB_CTRL(pipe, dsb->id), dsb_ctrl);
> +
> + POSTING_READ(DSB_CTRL(pipe, dsb->id));
> + return true;
> +}
> +
> +static inline bool intel_dsb_disable_engine(struct intel_dsb *dsb)
> +{
> + struct intel_crtc *crtc = container_of(dsb, typeof(*crtc), dsb);
> + struct drm_i915_private *dev_priv = to_i915(crtc->base.dev);
> + enum pipe pipe = crtc->pipe;
> + u32 dsb_ctrl;
> +
> + dsb_ctrl = I915_READ(DSB_CTRL(pipe, dsb->id));
> + if (DSB_STATUS & dsb_ctrl) {
> + DRM_DEBUG_KMS("DSB engine is busy.\n");
> + return false;
> + }
> +
> + dsb_ctrl &= ~DSB_ENABLE;
Do we really need to care about reading the reg val first and then
disabling it ? I can understand that for enable().
How about this:
if (!dsb_is_busy()) {
I915_WRITE(DSB_CTRL(pipe, dsb->id), 0);
POSTING_READ();
return true;
}
DRM_DEBUG_KMS("DSB engine is busy.\n");
return false;
But this is optional suggestion, you can take a call on this.
> + I915_WRITE(DSB_CTRL(pipe, dsb->id), dsb_ctrl);
> +
> + POSTING_READ(DSB_CTRL(pipe, dsb->id));
> + return true;
> +}
> +
> struct intel_dsb *
> intel_dsb_get(struct intel_crtc *crtc)
> {
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index 9188a0b53538..2dbaa49f5c74 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -11688,6 +11688,7 @@ enum skl_power_gate {
> #define DSBSL_INSTANCE(pipe, id) (_DSBSL_INSTANCE_BASE + \
> (pipe) * 0x1000 + (id) * 100)
> #define DSB_CTRL(pipe, id) _MMIO(DSBSL_INSTANCE(pipe, id) + 0x8)
> +#define DSB_ENABLE (1 << 31)
> #define DSB_STATUS (1 << 0)
>
With or without suggested change above: Feel free to use
Reviewed-by: Shashank Sharma <shashank.sharma@intel.com>
- Shashank
> #endif /* _I915_REG_H_ */
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-09-12 13:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 19:11 [PATCH v6 00/10] DSB enablement Animesh Manna
2019-09-11 19:11 ` [PATCH v6 01/10] drm/i915/dsb: feature flag added for display state buffer Animesh Manna
2019-09-12 12:09 ` Sharma, Shashank
2019-09-11 19:11 ` [PATCH v6 02/10] drm/i915/dsb: DSB context creation Animesh Manna
2019-09-12 12:31 ` Sharma, Shashank
2019-09-12 12:47 ` Jani Nikula
2019-09-11 19:11 ` [PATCH v6 03/10] drm/i915/dsb: single register write function for DSB Animesh Manna
2019-09-12 12:48 ` Sharma, Shashank
2019-09-12 12:51 ` Jani Nikula
2019-09-12 13:00 ` Sharma, Shashank
2019-09-12 13:07 ` Animesh Manna
2019-09-12 13:20 ` Sharma, Shashank
2019-09-11 19:11 ` [PATCH v6 04/10] drm/i915/dsb: Indexed " Animesh Manna
2019-09-12 13:18 ` Sharma, Shashank
2019-09-11 19:11 ` [PATCH v6 05/10] drm/i915/dsb: Check DSB engine status Animesh Manna
2019-09-12 13:21 ` Sharma, Shashank
2019-09-11 19:11 ` [PATCH v6 06/10] drm/i915/dsb: functions to enable/disable DSB engine Animesh Manna
2019-09-12 13:34 ` Sharma, Shashank [this message]
2019-09-11 19:11 ` [PATCH v6 07/10] drm/i915/dsb: function to trigger workload execution of DSB Animesh Manna
2019-09-12 13:36 ` Sharma, Shashank
2019-09-12 13:39 ` Jani Nikula
2019-09-12 13:58 ` Sharma, Shashank
2019-09-16 19:23 ` Jani Nikula
2019-09-11 19:11 ` [PATCH v6 08/10] drm/i915/dsb: Enable gamma lut programming using DSB Animesh Manna
2019-09-12 13:07 ` Jani Nikula
2019-09-12 13:26 ` Animesh Manna
2019-09-17 7:30 ` Jani Nikula
2019-09-17 9:19 ` Animesh Manna
2019-09-11 19:11 ` [PATCH v6 09/10] drm/i915/dsb: Enable DSB for gen12 Animesh Manna
2019-09-12 14:00 ` Sharma, Shashank
2019-09-11 19:11 ` [PATCH v6 10/10] drm/i915/dsb: Documentation for DSB Animesh Manna
2019-09-12 7:02 ` ✗ Fi.CI.CHECKPATCH: warning for DSB enablement. (rev6) Patchwork
2019-09-12 7:04 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-09-12 7:25 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-12 11:50 ` ✗ 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=5cf9ca64-e832-e601-7121-7dc384ef7b31@intel.com \
--to=shashank.sharma@intel.com \
--cc=animesh.manna@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=michel.thierry@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