Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: imre.deak@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/3] drm/i915/dgfx, mtl+: Disable display functionality if it's globally fused-off
Date: Tue, 07 Feb 2023 14:10:04 +0200	[thread overview]
Message-ID: <87lel9y8v7.fsf@intel.com> (raw)
In-Reply-To: <Y+I3uXy5BpW1zBuh@ideak-desk.fi.intel.com>

On Tue, 07 Feb 2023, Imre Deak <imre.deak@intel.com> wrote:
> On Tue, Feb 07, 2023 at 12:17:59PM +0200, Jani Nikula wrote:
>> Please drop all of these. There's an if (!HAS_DISPLAY()) just a few
>> lines down the purpose of which is to cover all of it in a unified
>> manner.
>
> Yes, missed this and just did the same as on older platforms above. I
> guess
>
> 	runtime->cpu_transcoder_mask = 0;
> 	runtime->fbc_mask = 0;
>
> could be removed from there as well then.

Agreed.


-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-02-07 12:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 16:35 [Intel-gfx] [PATCH 1/3] drm/i915: Move display power initialization during driver probing later Imre Deak
2023-02-06 16:35 ` [Intel-gfx] [PATCH 2/3] drm/i915/dgfx, mtl+: Disable display functionality if it's globally fused-off Imre Deak
2023-02-07 10:17   ` Jani Nikula
2023-02-07 11:37     ` Imre Deak
2023-02-07 12:10       ` Jani Nikula [this message]
2023-02-06 16:35 ` [Intel-gfx] [PATCH 3/3] drm/i915: Factor out a function disabling fused-off display Imre Deak
2023-02-07  2:45   ` iczero
2023-02-07 10:21   ` Jani Nikula
2023-02-07 11:46     ` Imre Deak
2023-02-06 19:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915: Move display power initialization during driver probing later Patchwork
2023-02-07  4:23 ` [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=87lel9y8v7.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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