Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Kahola, Mika" <mika.kahola@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/mtl: Introduce FBC B
Date: Fri, 19 Aug 2022 12:51:10 +0300	[thread overview]
Message-ID: <87r11co92p.fsf@intel.com> (raw)
In-Reply-To: <MWHPR1101MB2157EFEF10A5D8A4391C4107EF6A9@MWHPR1101MB2157.namprd11.prod.outlook.com>

On Wed, 17 Aug 2022, "Kahola, Mika" <mika.kahola@intel.com> wrote:
>> -----Original Message-----
>> From: Nikula, Jani <jani.nikula@intel.com>
>> Sent: Wednesday, August 17, 2022 3:26 PM
>> To: intel-gfx@lists.freedesktop.org
>> Cc: Nikula, Jani <jani.nikula@intel.com>; Ville Syrjälä
>> <ville.syrjala@linux.intel.com>; Kahola, Mika <mika.kahola@intel.com>
>> Subject: [PATCH] drm/i915/mtl: Introduce FBC B
>>
>> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>
>> MTL introduces a second FBC engine. The two FBC engines can operate entirely
>> independently, FBC A serving pipe A and FBC B serving pipe B.
>>
>> The one place where things might go a bit wrong is the CFB allocation from
>> stolen. We might have to consider some change to the allocation strategy to
>> have a better chance of both engines being able to allocate its CFB. Maybe FBC
>> A should allocate bottom up and FBC B top down, or something? For the
>> moment the allocation strategy is DRM_MM_INSERT_BEST for both.
>>
>> Cc: Mika Kahola <mika.kahola@intel.com>
>> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Reviewed-by: Mika Kahola <mika.kahola@intel.com>

Thanks for the review, pushed to drm-intel-next.

BR,
Jani.


>
>> ---
>>  drivers/gpu/drm/i915/display/intel_fbc.h | 1 +
>>  drivers/gpu/drm/i915/i915_pci.c          | 3 ++-
>>  2 files changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_fbc.h
>> b/drivers/gpu/drm/i915/display/intel_fbc.h
>> index db60143295ec..4adb98afe6ff 100644
>> --- a/drivers/gpu/drm/i915/display/intel_fbc.h
>> +++ b/drivers/gpu/drm/i915/display/intel_fbc.h
>> @@ -19,6 +19,7 @@ struct intel_plane_state;
>>
>>  enum intel_fbc_id {
>>       INTEL_FBC_A,
>> +     INTEL_FBC_B,
>>
>>       I915_MAX_FBCS,
>>  };
>> diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
>> index 9fd788e147a3..d8446bb25d5e 100644
>> --- a/drivers/gpu/drm/i915/i915_pci.c
>> +++ b/drivers/gpu/drm/i915/i915_pci.c
>> @@ -1111,7 +1111,8 @@ static const struct intel_device_info pvc_info = {
>>  #define XE_LPDP_FEATURES     \
>>       XE_LPD_FEATURES,        \
>>       .display.ver = 14,      \
>> -     .display.has_cdclk_crawl = 1
>> +     .display.has_cdclk_crawl = 1, \
>> +     .display.fbc_mask = BIT(INTEL_FBC_A) | BIT(INTEL_FBC_B)
>>
>>  __maybe_unused
>>  static const struct intel_device_info mtl_info = {
>> --
>> 2.34.1
>

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2022-08-19  9:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 12:26 [Intel-gfx] [PATCH] drm/i915/mtl: Introduce FBC B Jani Nikula
2022-08-17 12:38 ` Kahola, Mika
2022-08-19  9:51   ` Jani Nikula [this message]
2022-08-17 13:17 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-08-17 13:28 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-08-17 14:19 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/mtl: Introduce FBC B (rev2) Patchwork
2022-08-17 14:30 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-08-18 12:14 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/mtl: Introduce FBC B (rev3) Patchwork
2022-08-18 12:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-08-18 23:37 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=87r11co92p.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox