From: vathsala nagaraju <vathsala.nagaraju@intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/psr: enable psr1 on psr2 panels
Date: Wed, 11 Apr 2018 15:01:24 +0530 [thread overview]
Message-ID: <5ACDD5EC.90503@intel.com> (raw)
In-Reply-To: <20180406190652.GE8964@intel.com>
+ puthik
On Saturday 07 April 2018 12:36 AM, Vivi, Rodrigo wrote:
> On Fri, Apr 06, 2018 at 12:10:24PM -0700, Dhinakaran Pandiyan wrote:
>>
>>
>> On Sat, 2018-04-07 at 00:12 +0530, vathsala nagaraju wrote:
>>> From: Vathsala Nagaraju <vathsala.nagaraju@intel.com>
>>>
>>> Adds force_psr1 mod parameter to enable psr1 on psr2 panels.
>>> useful in cases where psr2 fails and user wants to enable
>>> psr1 feature for power saving until a fix
>>> is provided for psr2.
> The parameters shouldn't be used by users to select a configuration.
> They are marked as unsafe. We should only enable the feature when
> we are comfortable it doesn't cause trouble.
The idea was to give user the option to switch to psr1 ,if they want to.
>
>>
>> We should perhaps make enable_psr=1 enable just PSR1. I am not
>> comfortable that we enable PSR2 at all, there are no tests in IGT for
>> selective update, seems like nobody really knows exactly how well it
>> works.
with enable_psr , we are deciding whether to use psr1/psr2.
we can reuse enable_psr.
> Agreed. Probably good for now to avoid PSR2 in all situations and only
> allow PSR2 when we are properly testing it.
>
>>
>>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>>> Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
>>> Cc: José Roberto de Souza <jose.souza@intel.com>
>>> Signed-off-by: Vathsala Nagaraju <vathsala.nagaraju@intel.com>
>>> ---
>>> drivers/gpu/drm/i915/i915_params.c | 5 +++++
>>> drivers/gpu/drm/i915/i915_params.h | 1 +
>>> drivers/gpu/drm/i915/intel_psr.c | 2 ++
>>> 3 files changed, 8 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/i915/i915_params.c b/drivers/gpu/drm/i915/i915_params.c
>>> index 08108ce..5b6f5af 100644
>>> --- a/drivers/gpu/drm/i915/i915_params.c
>>> +++ b/drivers/gpu/drm/i915/i915_params.c
>>> @@ -95,6 +95,11 @@ struct i915_params i915_modparams __read_mostly = {
>>> "(0=disabled, 1=enabled - link mode chosen per-platform, 2=force link-standby mode, 3=force link-off mode) "
>>> "Default: -1 (use per-chip default)");
>>>
>>> +i915_param_named_unsafe(force_psr1, int, 0600,
>>> + "Enable PSR1 on PSR2 Panel "
>>> + "(0=disabled, 1=enabled) "
>>> + "Default: -1 (use per-chip default)");
>>> +
>>> i915_param_named_unsafe(alpha_support, bool, 0400,
>>> "Enable alpha quality driver support for latest hardware. "
>>> "See also CONFIG_DRM_I915_ALPHA_SUPPORT.");
>>> diff --git a/drivers/gpu/drm/i915/i915_params.h b/drivers/gpu/drm/i915/i915_params.h
>>> index c963603..1f5dd1c 100644
>>> --- a/drivers/gpu/drm/i915/i915_params.h
>>> +++ b/drivers/gpu/drm/i915/i915_params.h
>>> @@ -44,6 +44,7 @@
>>> param(int, enable_fbc, -1) \
>>> param(int, enable_ppgtt, -1) \
>>> param(int, enable_psr, -1) \
>>> + param(int, force_psr1, -1) \
>>> param(int, disable_power_well, -1) \
>>> param(int, enable_ips, 1) \
>>> param(int, invert_brightness, 0) \
>>> diff --git a/drivers/gpu/drm/i915/intel_psr.c b/drivers/gpu/drm/i915/intel_psr.c
>>> index 2d53f73..415e377 100644
>>> --- a/drivers/gpu/drm/i915/intel_psr.c
>>> +++ b/drivers/gpu/drm/i915/intel_psr.c
>>> @@ -540,6 +540,8 @@ void intel_psr_compute_config(struct intel_dp *intel_dp,
>>>
>>> crtc_state->has_psr = true;
>>> crtc_state->has_psr2 = intel_psr2_config_valid(intel_dp, crtc_state);
>>> + if (i915_modparams.force_psr1 == 1 && crtc_state->has_psr2)
>>> + crtc_state->has_psr2 = false;
>>> DRM_DEBUG_KMS("Enabling PSR%s\n", crtc_state->has_psr2 ? "2" : "");
>>> }
>>>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-04-11 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 18:42 [PATCH] drm/i915/psr: enable psr1 on psr2 panels vathsala nagaraju
2018-04-06 19:07 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-04-06 19:10 ` [PATCH] " Dhinakaran Pandiyan
2018-04-06 19:06 ` Rodrigo Vivi
2018-04-11 9:31 ` vathsala nagaraju [this message]
2018-04-11 14:40 ` Rodrigo Vivi
2018-04-11 17:58 ` Pandiyan, Dhinakaran
2018-04-06 19:24 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-04-06 23:47 ` ✗ Fi.CI.IGT: warning " 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=5ACDD5EC.90503@intel.com \
--to=vathsala.nagaraju@intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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