From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Runyan, Arthur J" <arthur.j.runyan@intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 05/11] drm/i915: Rename BXT PORTA HPD defines
Date: Thu, 27 Aug 2015 18:50:29 +0300 [thread overview]
Message-ID: <20150827155029.GJ5176@intel.com> (raw)
In-Reply-To: <C7E999358BBE9E45938BA940F5F511087583C8EF@fmsmsx116.amr.corp.intel.com>
On Wed, Aug 26, 2015 at 09:59:13PM +0000, Runyan, Arthur J wrote:
>
> >From: Ville Syrjälä [mailto:ville.syrjala@linux.intel.com]
> >> On Wed, Aug 26, 2015 at 04:13:52PM -0300, Paulo Zanoni wrote:
> ...
> >> Although the doc for LPT _suggests_ this is only for LPT:LP, it
> >> doesn't mark this bit as LPT:LP-specific just like it marks all the
> >> other LPT:LP-specific bits in every register, so I wonder if this is
> >> really LPT:LP or if there's another way to find this out, like some
> >> strap or VBT bit.
> >
> >Hmm. Indeed. There is that note about the enable being in the north
> >on DevLPT:H. I guess that's what gave me the idea for this patch. But
> >the rest of the text just talks about PCH being on the same package or
> >not. Not sure if the two conditions are entirely the same thing.
> >
> >For HSW the north register says we need this on DevHSW:ULT. For BDW it
> >refers us to a package type indication in FUSE_STRAP3, but the only
> >relevant looking bit is the ULT mode bit, which it also says is
> >currently unused and should be ignored :(
> >
> >Art, could you help us out here? How should we actually determine
> >(on HSW/BDW) whether to enable the DDI A HPD in the north, south,
> >or both?
>
> The north and south hotplug control registers have text to try to explain this in the DDI A HPD enable fields, which I pasted below. You always enable north. You additionally enable south if CPU and PCH are in the same package.
OK thanks. That more or less matches my original understanding.
>
> "This only applies to systems that have the CPU and PCH in the same package, where the DDI A HPD input is connected to the PCH and the HPD must be enabled in both the North Display Engine Registers HOTPLUG_CTL and the South Display Engine Registers SHOTPLUG_CTL. The HPD status is found in North Display Engine Registers HOTPLUG_CTL.
>
> On systems that have the CPU and PCH in separate packages, the DDI A HPD input is connected to the CPU, and the DDI A HPD input must be enabled in only the North Display Engine Registers HOTPLUG_CTL."
>
> That fuse may not be correct on all SKUs, but I assume you have other ways to recognize what kind of package it is. I originally listed out ULT and ULX, but it became more complicated with BDW.
I'm not aware of any way of identifying the package type. My original
assumption was LPT-LP -> MCP, LPT-H -> separate package, and most of
the material I've managed to dig up would seem to support that. But
it's hard to be sure.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-08-27 15:50 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 15:44 [PATCH 00/11] drm/i915: Port A HPD and other HPD cleanups ville.syrjala
2015-08-12 15:44 ` [PATCH 01/11] drm/i915: Clean up various HPD defines ville.syrjala
2015-08-17 19:51 ` Paulo Zanoni
2015-08-26 18:23 ` Paulo Zanoni
2015-08-12 15:44 ` [PATCH 02/11] drm/i915; Extract intel_hpd_enabled_irqs() ville.syrjala
2015-08-17 20:06 ` Paulo Zanoni
2015-08-19 17:02 ` Ville Syrjälä
2015-08-26 18:30 ` Paulo Zanoni
2015-08-12 15:44 ` [PATCH 03/11] drm/i915: Factor out ilk_update_display_irq() ville.syrjala
2015-08-26 18:46 ` Paulo Zanoni
2015-08-12 15:44 ` [PATCH 04/11] drm/i915: Add HAS_PCH_LPT_LP() macro ville.syrjala
2015-08-26 18:58 ` Paulo Zanoni
2015-08-27 16:32 ` Ville Syrjälä
2015-08-12 15:44 ` [PATCH 05/11] drm/i915: Rename BXT PORTA HPD defines ville.syrjala
2015-08-26 19:13 ` Paulo Zanoni
2015-08-26 19:43 ` Ville Syrjälä
2015-08-26 21:59 ` Runyan, Arthur J
2015-08-27 15:50 ` Ville Syrjälä [this message]
2015-08-27 19:34 ` Runyan, Arthur J
2015-08-27 19:52 ` Ville Syrjälä
2015-08-27 16:39 ` Ville Syrjälä
2015-08-12 15:44 ` [PATCH 06/11] drm/i915: Introduce spt_irq_handler() ville.syrjala
2015-08-26 21:44 ` Paulo Zanoni
2015-08-27 7:38 ` Jani Nikula
2015-08-27 16:13 ` Ville Syrjälä
2015-08-27 17:52 ` Ville Syrjälä
2015-08-12 15:44 ` [PATCH 07/11] drm/i915: Add port A HPD support for ILK/SNB ville.syrjala
2015-08-27 18:24 ` Paulo Zanoni
2015-08-12 15:44 ` [PATCH 08/11] drm/i915: Add port A HPD support for IVB/HSW ville.syrjala
2015-08-14 9:17 ` Daniel Vetter
2015-08-27 18:30 ` Paulo Zanoni
2015-08-12 15:44 ` [PATCH 09/11] drm/i915: LPT:LP needs port A HPD enabled in both north and south ville.syrjala
2015-08-27 18:40 ` Paulo Zanoni
2015-08-12 15:44 ` [PATCH 10/11] drm/i915: Add port A HPD support for BDW ville.syrjala
2015-08-27 19:29 ` Paulo Zanoni
2015-08-27 19:51 ` Ville Syrjälä
2015-08-12 15:44 ` [PATCH 11/11] drm/i915: Add port A HPD support for SPT ville.syrjala
2015-08-27 20:26 ` Paulo Zanoni
2015-08-19 18:13 ` [PATCH 12/11] drm/i915: Reinitialize HPD after runtime D3 ville.syrjala
2015-08-27 20:36 ` Paulo Zanoni
2015-08-19 19:11 ` [PATCH 00/11] drm/i915: Port A HPD and other HPD cleanups Ville Syrjälä
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=20150827155029.GJ5176@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=arthur.j.runyan@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 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.