From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Cc: "S, Deepak" <deepak.s@intel.com>
Subject: Re: [PATCH 1/5] drm/i915/kbl: Add Kabylake PCI ID
Date: Tue, 6 Oct 2015 17:31:30 +0000 [thread overview]
Message-ID: <1444152765.22060.61.camel@intel.com> (raw)
In-Reply-To: <87a8rw9xdu.fsf@intel.com>
On Tue, 2015-10-06 at 12:09 +0300, Jani Nikula wrote:
> On Tue, 06 Oct 2015, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> > From: Deepak S <deepak.s@intel.com>
> >
> > v2: separate out device info into different GT (Damien)
> > v3: Add is_kabylake to the KBL gt3 structuer (Damien)
> > Sort the platforms in older -> newer order (Damien)
> >
> > Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
> > Signed-off-by: Deepak S <deepak.s@intel.com>
> > Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_drv.c | 33
> > ++++++++++++++++++++++++++++++++-
> > drivers/gpu/drm/i915/i915_drv.h | 2 ++
> > include/drm/i915_pciids.h | 29 +++++++++++++++++++++++++++++
> > 3 files changed, 63 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_drv.c
> > b/drivers/gpu/drm/i915/i915_drv.c
> > index 1cb6b82..f42102d 100644
> > --- a/drivers/gpu/drm/i915/i915_drv.c
> > +++ b/drivers/gpu/drm/i915/i915_drv.c
> > @@ -394,6 +394,34 @@ static const struct intel_device_info
> > intel_broxton_info = {
> > IVB_CURSOR_OFFSETS,
> > };
> >
> > +static const struct intel_device_info intel_kabylake_info = {
> > + .is_preliminary = 1,
> > + .is_skylake = 1,
>
> Now's the time to call the shots, is this really a good idea or not?
> See
> VLV vs. CHV, we (okay, the royal we) still confuse ourselves with
> IS_VALLEYVIEW.
>
> Granted, 74 call sites for IS_SKYLAKE(), all of those would need to
> be
> patched. We'd need something like "is skylake family" including SKL
> and
> KBL. Some of them might be changed to be more like feature flags,
> which
> is something we've decided we need to do more anyway.
To be honest I also don't like this approach as I didn't like the chv
is vlv one. I always get confused and I thought about changing
everything many times during last week, but as you pointed out it would
be a change in many entries and not sure what others opinion was since
I never saw any complain about this patch before neither the vlv-chv
ones...
But if you and Daniel prefer I can do a
s/IS_SKYLAKE(dev)/IS_KABYLAKE(dev) || IS_SKYLAKE(dev)
Just let me know...
The IS_SKYLAKE_FAMILY I don't like much because it will still confuse
people because in ark they will probably be 2 different "families" if
they continue with the current scheme they are using so far.
>
> BR,
> Jani.
>
>
> > + .is_kabylake = 1,
> > + .gen = 9, .num_pipes = 3,
> > + .need_gfx_hws = 1, .has_hotplug = 1,
> > + .ring_mask = RENDER_RING | BSD_RING | BLT_RING |
> > VEBOX_RING,
> > + .has_llc = 1,
> > + .has_ddi = 1,
> > + .has_fbc = 1,
> > + GEN_DEFAULT_PIPEOFFSETS,
> > + IVB_CURSOR_OFFSETS,
> > +};
> > +
> > +static const struct intel_device_info intel_kabylake_gt3_info = {
> > + .is_preliminary = 1,
> > + .is_skylake = 1,
> > + .is_kabylake = 1,
> > + .gen = 9, .num_pipes = 3,
> > + .need_gfx_hws = 1, .has_hotplug = 1,
> > + .ring_mask = RENDER_RING | BSD_RING | BLT_RING |
> > VEBOX_RING | BSD2_RING,
> > + .has_llc = 1,
> > + .has_ddi = 1,
> > + .has_fbc = 1,
> > + GEN_DEFAULT_PIPEOFFSETS,
> > + IVB_CURSOR_OFFSETS,
> > +};
> > +
> > /*
> > * Make sure any device matches here are from most specific to
> > most
> > * general. For example, since the Quanta match is based on the
> > subsystem
> > @@ -434,7 +462,10 @@ static const struct intel_device_info
> > intel_broxton_info = {
> > INTEL_SKL_GT1_IDS(&intel_skylake_info), \
> > INTEL_SKL_GT2_IDS(&intel_skylake_info), \
> > INTEL_SKL_GT3_IDS(&intel_skylake_gt3_info), \
> > - INTEL_BXT_IDS(&intel_broxton_info)
> > + INTEL_BXT_IDS(&intel_broxton_info), \
> > + INTEL_KBL_GT1_IDS(&intel_kabylake_info), \
> > + INTEL_KBL_GT2_IDS(&intel_kabylake_info), \
> > + INTEL_KBL_GT3_IDS(&intel_kabylake_gt3_info)
> >
> > static const struct pci_device_id pciidlist[] = { /
> > * aka */
> > INTEL_PCI_IDS,
> > diff --git a/drivers/gpu/drm/i915/i915_drv.h
> > b/drivers/gpu/drm/i915/i915_drv.h
> > index 824e724..f7e9d7e 100644
> > --- a/drivers/gpu/drm/i915/i915_drv.h
> > +++ b/drivers/gpu/drm/i915/i915_drv.h
> > @@ -765,6 +765,7 @@ struct intel_csr {
> > func(is_valleyview) sep \
> > func(is_haswell) sep \
> > func(is_skylake) sep \
> > + func(is_kabylake) sep \
> > func(is_preliminary) sep \
> > func(has_fbc) sep \
> > func(has_pipe_cxsr) sep \
> > @@ -2464,6 +2465,7 @@ struct drm_i915_cmd_table {
> > #define IS_BROADWELL(dev) (!INTEL_INFO(dev)->is_valleyview
> > && IS_GEN8(dev))
> > #define IS_SKYLAKE(dev) (INTEL_INFO(dev)->is_skylake)
> > #define IS_BROXTON(dev) (!INTEL_INFO(dev)->is_skylake &&
> > IS_GEN9(dev))
> > +#define IS_KABYLAKE(dev) (INTEL_INFO(dev)->is_kabylake)
> > #define IS_MOBILE(dev) (INTEL_INFO(dev)->is_mobile)
> > #define IS_HSW_EARLY_SDV(dev) (IS_HASWELL(dev) && \
> > (INTEL_DEVID(dev) & 0xFF00) ==
> > 0x0C00)
> > diff --git a/include/drm/i915_pciids.h b/include/drm/i915_pciids.h
> > index 17c4456..2e7a159 100644
> > --- a/include/drm/i915_pciids.h
> > +++ b/include/drm/i915_pciids.h
> > @@ -291,4 +291,33 @@
> > INTEL_VGA_DEVICE(0x1A84, info), \
> > INTEL_VGA_DEVICE(0x5A84, info)
> >
> > +#define INTEL_KBL_GT1_IDS(info) \
> > + INTEL_VGA_DEVICE(0x5913, info), /* ULT GT1.5 */ \
> > + INTEL_VGA_DEVICE(0x5915, info), /* ULX GT1.5 */ \
> > + INTEL_VGA_DEVICE(0x5917, info), /* DT GT1.5 */ \
> > + INTEL_VGA_DEVICE(0x5906, info), /* ULT GT1 */ \
> > + INTEL_VGA_DEVICE(0x590E, info), /* ULX GT1 */ \
> > + INTEL_VGA_DEVICE(0x5902, info), /* DT GT1 */ \
> > + INTEL_VGA_DEVICE(0x590B, info), /* Halo GT1 */ \
> > + INTEL_VGA_DEVICE(0x590A, info) /* SRV GT1 */
> > +
> > +#define INTEL_KBL_GT2_IDS(info) \
> > + INTEL_VGA_DEVICE(0x5916, info), /* ULT GT2 */ \
> > + INTEL_VGA_DEVICE(0x5921, info), /* ULT GT2F */ \
> > + INTEL_VGA_DEVICE(0x591E, info), /* ULX GT2 */ \
> > + INTEL_VGA_DEVICE(0x5912, info), /* DT GT2 */ \
> > + INTEL_VGA_DEVICE(0x591B, info), /* Halo GT2 */ \
> > + INTEL_VGA_DEVICE(0x591A, info), /* SRV GT2 */ \
> > + INTEL_VGA_DEVICE(0x591D, info) /* WKS GT2 */
> > +
> > +#define INTEL_KBL_GT3_IDS(info) \
> > + INTEL_VGA_DEVICE(0x5926, info), /* ULT GT3 */ \
> > + INTEL_VGA_DEVICE(0x592B, info), /* Halo GT3 */ \
> > + INTEL_VGA_DEVICE(0x592A, info) /* SRV GT3 */
> > +
> > +#define INTEL_KBL_IDS(info) \
> > + INTEL_KBL_GT1_IDS(info), \
> > + INTEL_KBL_GT2_IDS(info), \
> > + INTEL_KBL_GT3_IDS(info)
> > +
> > #endif /* _I915_PCIIDS_H */
> > --
> > 2.4.3
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-10-06 17:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 22:44 [PATCH 0/5] Introduce Kabylake Support Rodrigo Vivi
2015-10-05 22:44 ` [PATCH 1/5] drm/i915/kbl: Add Kabylake PCI ID Rodrigo Vivi
2015-10-06 9:09 ` Jani Nikula
2015-10-06 17:31 ` Vivi, Rodrigo [this message]
2015-10-07 13:55 ` Daniel Vetter
2015-10-07 14:34 ` Ville Syrjälä
2015-10-06 19:59 ` Ville Syrjälä
2015-10-06 9:11 ` Jani Nikula
2015-10-05 22:44 ` [PATCH 2/5] drm/i915/kbl: Use propper ddi buffer translation table for Kabylake ULT and ULX Rodrigo Vivi
2015-10-05 22:44 ` [PATCH 3/5] drm/i915/kbl: Kabylake A0 is based on Skylake H0 Rodrigo Vivi
2015-10-06 9:24 ` Jani Nikula
2015-10-06 17:43 ` Vivi, Rodrigo
2015-10-06 20:51 ` Rodrigo Vivi
2015-10-06 21:09 ` Ben Widawsky
2015-10-07 8:07 ` Jani Nikula
2015-10-05 22:44 ` [PATCH 4/5] drm/i915/kbl: Fix DMC load on Kabylake Rodrigo Vivi
2015-10-05 22:44 ` [PATCH 5/5] drm/i915/kbl: drm/i915: Avoid GuC loading for now " Rodrigo Vivi
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=1444152765.22060.61.camel@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=deepak.s@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.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;
as well as URLs for NNTP newsgroup(s).