From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Hogander\, Jouni" <jouni.hogander@intel.com>,
"intel-gfx\@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>, "Souza\,
Jose" <jose.souza@intel.com>
Cc: "Kahola\, Mika" <mika.kahola@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/adlp: Extend PSR2 support in transcoder B
Date: Wed, 27 Oct 2021 17:42:48 +0300 [thread overview]
Message-ID: <87k0hyh6l3.fsf@intel.com> (raw)
In-Reply-To: <a36cf418169109b18845eac552d450dadee1e6ca.camel@intel.com>
On Wed, 27 Oct 2021, "Hogander, Jouni" <jouni.hogander@intel.com> wrote:
> On Tue, 2021-10-26 at 15:33 -0700, José Roberto de Souza wrote:
>> PSR2 is supported in transcoder A and B on Alderlake-P.
>>
>> BSpec: 49185
>> Cc: Mika Kahola <mika.kahola@intel.com>
>> Cc: Jouni Hogander <jouni.hogander@intel.com>
>> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
>
> LGTM
>
> Reviewed-by: Jouni Högander <jouni.hogander@intel.com>
Since INVALID_TRANSCODER is a thing, I'd actually prefer:
trans == TRANSCODER_A || trans == TRANSCODER_B
It's not likely INVALID_TRANSCODER will ever end up here, but I tried to
look and it's actually not trivial to say this will never happen. I
prefer the defensive approach.
BR,
Jani.
>
>> ---
>> drivers/gpu/drm/i915/display/intel_psr.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c
>> b/drivers/gpu/drm/i915/display/intel_psr.c
>> index d35db50ef967a..710b911b065b9 100644
>> --- a/drivers/gpu/drm/i915/display/intel_psr.c
>> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
>> @@ -588,7 +588,9 @@ static void hsw_activate_psr2(struct intel_dp
>> *intel_dp)
>> static bool
>> transcoder_has_psr2(struct drm_i915_private *dev_priv, enum
>> transcoder trans)
>> {
>> - if (DISPLAY_VER(dev_priv) >= 12)
>> + if (IS_ALDERLAKE_P(dev_priv))
>> + return trans <= TRANSCODER_B;
>> + else if (DISPLAY_VER(dev_priv) >= 12)
>> return trans == TRANSCODER_A;
>> else
>> return trans == TRANSCODER_EDP;
>
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2021-10-27 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 22:33 [Intel-gfx] [PATCH] drm/i915/adlp: Extend PSR2 support in transcoder B José Roberto de Souza
2021-10-26 23:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-10-27 1:14 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-10-27 7:28 ` [Intel-gfx] [PATCH] " Hogander, Jouni
2021-10-27 14:42 ` Jani Nikula [this message]
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=87k0hyh6l3.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=jouni.hogander@intel.com \
--cc=mika.kahola@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.