Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: remove CNL leftover
Date: Fri, 22 Oct 2021 12:02:55 +0300	[thread overview]
Message-ID: <YXJ+PwVjT8Xbfb32@intel.com> (raw)
In-Reply-To: <20211021213213.rl7dyux3sfaczyit@ldmartin-desk2>

On Thu, Oct 21, 2021 at 02:32:13PM -0700, Lucas De Marchi wrote:
> On Thu, Oct 21, 2021 at 10:05:40PM +0300, Ville Syrjälä wrote:
> >On Thu, Oct 21, 2021 at 11:18:47AM -0700, Lucas De Marchi wrote:
> >> We left the definition IS_CANNONLAKE() macro while removing it from the
> >> tree due to having to merge the changes in different branches. Now that
> >> everything is back in sync and nobody is using IS_CANNONLAKE(), we can
> >> safely ditch it.
> >>
> >> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> >
> >Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> >I found another leftover somewhere else, but now I forgot where
> >it was. I guess it'll come back to me eventually.
> 
> drivers/gpu/drm/i915/intel_pch.c, which I suspect is what you're talking
> about due to your recent patches. But that one is correct as we still
> have Cannon Lake Point (and I never remember if P in CNP is for PCH or
> Point) 
> 
> there is another one in a comment in drivers/gpu/drm/i915/gt/intel_gt.c,
> too.

Sleeping on it helped, I now remember that it's the SAGV block time.

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2021-10-22  9:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21 18:18 [Intel-gfx] [PATCH] drm/i915: remove CNL leftover Lucas De Marchi
2021-10-21 19:05 ` Ville Syrjälä
2021-10-21 21:32   ` Lucas De Marchi
2021-10-22  9:02     ` Ville Syrjälä [this message]
2021-10-21 23:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-10-22  2:09 ` [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=YXJ+PwVjT8Xbfb32@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@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