All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Srivatsa, Anusha" <anusha.srivatsa@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	"Nikula, Jani" <jani.nikula@intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>, Ingo Molnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>
Subject: RE: [v3 0/3] Introduce Raptor Lake S
Date: Mon, 6 Dec 2021 04:29:30 +0000	[thread overview]
Message-ID: <72998a361a854e59acdbe1ec2c75a0a2@intel.com> (raw)
In-Reply-To: <7576de4a-fbd9-ea5c-2d3d-1c5ada9f30e1@linux.intel.com>



> -----Original Message-----
> From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Sent: Friday, December 3, 2021 2:57 PM
> To: Srivatsa, Anusha <anusha.srivatsa@intel.com>; intel-
> gfx@lists.freedesktop.org
> Cc: x86@kernel.org; dri-devel@lists.freedesktop.org; Ingo Molnar
> <mingo@redhat.com>; Borislav Petkov <bp@alien8.de>; Dave Hansen
> <dave.hansen@linux.intel.com>; Joonas Lahtinen
> <joonas.lahtinen@linux.intel.com>; Nikula, Jani <jani.nikula@intel.com>
> Subject: Re: [v3 0/3] Introduce Raptor Lake S
> 
> 
> On 03/12/2021 06:35, Anusha Srivatsa wrote:
> > Raptor Lake S(RPL-S) is a version 12
> > Display, Media and Render. For all i915 purposes it is the same as
> > Alder Lake S (ADL-S).
> >
> > The series introduces it as a subplatform of ADL-S. The one difference
> > is the GuC submission which is default on RPL-S but was not the case
> > with ADL-S.
> 
> As a side note, not a blocker of any kind, I am slightly disheartened but the
> confusion of ADL_P and ADL_S being separate platforms, but then RPL_S is
> subplatform of ADL_S. Maybe it is just me not being able to keep track of
> things.
> 
> > All patches are reviewed. Jani has acked the series.
> > Looking for other acks in order to merge these to respective branches.
> 
> Which branches would that be for this series? First two to drm-intel-next and
> last one to drm-intel-gt-next? Is that complication needed and/or worth the
> effort?

Tvrtko,
 All three have to land to drm-intel-next. The last one has dependency on the first patch and is a trivial change.

Anusha
> Regards,
> 
> Tvrtko
> 
> > Cc: x86@kernel.org
> > Cc: dri-devel@lists.freedesktop.org
> > Cc: Ingo Molnar <mingo@redhat.com>
> > Cc: Borislav Petkov <bp@alien8.de>
> > Cc: Dave Hansen <dave.hansen@linux.intel.com>
> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> > Acked-by: Jani Nikula <jani.nikula@intel.com>
> >
> > Anusha Srivatsa (3):
> >    drm/i915/rpl-s: Add PCI IDS for Raptor Lake S
> >    drm/i915/rpl-s: Add PCH Support for Raptor Lake S
> >    drm/i915/rpl-s: Enable guc submission by default
> >
> >   arch/x86/kernel/early-quirks.c           | 1 +
> >   drivers/gpu/drm/i915/gt/uc/intel_uc.c    | 2 +-
> >   drivers/gpu/drm/i915/i915_drv.h          | 2 ++
> >   drivers/gpu/drm/i915/i915_pci.c          | 1 +
> >   drivers/gpu/drm/i915/intel_device_info.c | 7 +++++++
> >   drivers/gpu/drm/i915/intel_device_info.h | 3 +++
> >   drivers/gpu/drm/i915/intel_pch.c         | 1 +
> >   drivers/gpu/drm/i915/intel_pch.h         | 1 +
> >   include/drm/i915_pciids.h                | 9 +++++++++
> >   9 files changed, 26 insertions(+), 1 deletion(-)
> >

WARNING: multiple messages have this Message-ID (diff)
From: "Srivatsa, Anusha" <anusha.srivatsa@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	"Nikula, Jani" <jani.nikula@intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>, Ingo Molnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>
Subject: Re: [Intel-gfx] [v3 0/3] Introduce Raptor Lake S
Date: Mon, 6 Dec 2021 04:29:30 +0000	[thread overview]
Message-ID: <72998a361a854e59acdbe1ec2c75a0a2@intel.com> (raw)
In-Reply-To: <7576de4a-fbd9-ea5c-2d3d-1c5ada9f30e1@linux.intel.com>



> -----Original Message-----
> From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Sent: Friday, December 3, 2021 2:57 PM
> To: Srivatsa, Anusha <anusha.srivatsa@intel.com>; intel-
> gfx@lists.freedesktop.org
> Cc: x86@kernel.org; dri-devel@lists.freedesktop.org; Ingo Molnar
> <mingo@redhat.com>; Borislav Petkov <bp@alien8.de>; Dave Hansen
> <dave.hansen@linux.intel.com>; Joonas Lahtinen
> <joonas.lahtinen@linux.intel.com>; Nikula, Jani <jani.nikula@intel.com>
> Subject: Re: [v3 0/3] Introduce Raptor Lake S
> 
> 
> On 03/12/2021 06:35, Anusha Srivatsa wrote:
> > Raptor Lake S(RPL-S) is a version 12
> > Display, Media and Render. For all i915 purposes it is the same as
> > Alder Lake S (ADL-S).
> >
> > The series introduces it as a subplatform of ADL-S. The one difference
> > is the GuC submission which is default on RPL-S but was not the case
> > with ADL-S.
> 
> As a side note, not a blocker of any kind, I am slightly disheartened but the
> confusion of ADL_P and ADL_S being separate platforms, but then RPL_S is
> subplatform of ADL_S. Maybe it is just me not being able to keep track of
> things.
> 
> > All patches are reviewed. Jani has acked the series.
> > Looking for other acks in order to merge these to respective branches.
> 
> Which branches would that be for this series? First two to drm-intel-next and
> last one to drm-intel-gt-next? Is that complication needed and/or worth the
> effort?

Tvrtko,
 All three have to land to drm-intel-next. The last one has dependency on the first patch and is a trivial change.

Anusha
> Regards,
> 
> Tvrtko
> 
> > Cc: x86@kernel.org
> > Cc: dri-devel@lists.freedesktop.org
> > Cc: Ingo Molnar <mingo@redhat.com>
> > Cc: Borislav Petkov <bp@alien8.de>
> > Cc: Dave Hansen <dave.hansen@linux.intel.com>
> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> > Acked-by: Jani Nikula <jani.nikula@intel.com>
> >
> > Anusha Srivatsa (3):
> >    drm/i915/rpl-s: Add PCI IDS for Raptor Lake S
> >    drm/i915/rpl-s: Add PCH Support for Raptor Lake S
> >    drm/i915/rpl-s: Enable guc submission by default
> >
> >   arch/x86/kernel/early-quirks.c           | 1 +
> >   drivers/gpu/drm/i915/gt/uc/intel_uc.c    | 2 +-
> >   drivers/gpu/drm/i915/i915_drv.h          | 2 ++
> >   drivers/gpu/drm/i915/i915_pci.c          | 1 +
> >   drivers/gpu/drm/i915/intel_device_info.c | 7 +++++++
> >   drivers/gpu/drm/i915/intel_device_info.h | 3 +++
> >   drivers/gpu/drm/i915/intel_pch.c         | 1 +
> >   drivers/gpu/drm/i915/intel_pch.h         | 1 +
> >   include/drm/i915_pciids.h                | 9 +++++++++
> >   9 files changed, 26 insertions(+), 1 deletion(-)
> >

  reply	other threads:[~2021-12-06 10:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03  6:35 [v3 0/3] Introduce Raptor Lake S Anusha Srivatsa
2021-12-03  6:35 ` [Intel-gfx] " Anusha Srivatsa
2021-12-03  6:35 ` [v3 1/3] drm/i915/rpl-s: Add PCI IDS for " Anusha Srivatsa
2021-12-03  6:35   ` [Intel-gfx] " Anusha Srivatsa
2021-12-08 20:56   ` Dave Hansen
2021-12-08 20:56     ` [Intel-gfx] " Dave Hansen
2021-12-09 10:14     ` Srivatsa, Anusha
2021-12-09 10:14       ` Srivatsa, Anusha
2021-12-03  6:35 ` [v3 2/3] drm/i915/rpl-s: Add PCH Support " Anusha Srivatsa
2021-12-03  6:35   ` [Intel-gfx] " Anusha Srivatsa
2021-12-03  6:35 ` [v3 3/3] drm/i915/rpl-s: Enable guc submission by default Anusha Srivatsa
2021-12-03  6:35   ` [Intel-gfx] " Anusha Srivatsa
2021-12-03  8:25 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce Raptor Lake S (rev5) Patchwork
2021-12-03  8:27 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-12-03  8:53 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-12-03  9:27 ` [v3 0/3] Introduce Raptor Lake S Tvrtko Ursulin
2021-12-03  9:27   ` [Intel-gfx] " Tvrtko Ursulin
2021-12-06  4:29   ` Srivatsa, Anusha [this message]
2021-12-06  4:29     ` Srivatsa, Anusha
2021-12-07  9:53     ` Srivatsa, Anusha
2021-12-07  9:53       ` [Intel-gfx] " Srivatsa, Anusha
2021-12-08  9:52     ` Tvrtko Ursulin
2021-12-08  9:52       ` [Intel-gfx] " Tvrtko Ursulin

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=72998a361a854e59acdbe1ec2c75a0a2@intel.com \
    --to=anusha.srivatsa@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=mingo@redhat.com \
    --cc=tvrtko.ursulin@linux.intel.com \
    --cc=x86@kernel.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 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.