From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/8] drm/i915/bios: parse DDI ports also for CHV for HDMI DDC pin and DP AUX channel
Date: Mon, 9 Oct 2017 19:45:46 +0300 [thread overview]
Message-ID: <20171009164546.GF10981@intel.com> (raw)
In-Reply-To: <d0815082cb98487618429b62414854137049b888.1506586821.git.jani.nikula@intel.com>
On Thu, Sep 28, 2017 at 11:21:57AM +0300, Jani Nikula wrote:
> While technically CHV isn't DDI, we do look at the VBT based DDI port
> info for HDMI DDC pin and DP AUX channel. (We call these "alternate",
> but they're really just something that aren't platform defaults.)
>
> In commit e4ab73a13291 ("drm/i915: Respect alternate_ddc_pin for all DDI
> ports") Ville writes, "IIRC there may be CHV system that might actually
> need this."
>
> I'm not sure why there couldn't be even more platforms that need this,
> but start conservative, and parse the info for CHV in addition to DDI.
Going back as far as VLV might make some sense since it came out at around
the same time as HSW, and IIRC the VBT versions seen on VLV and HSW are
more less the same.
Series lgtm
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=100553
> Reported-by: Marek Wilczewski <mw@3cte.pl>
> Cc: stable@vger.kernel.org
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/intel_bios.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_bios.c b/drivers/gpu/drm/i915/intel_bios.c
> index 3747d8df0175..6b8d396ab605 100644
> --- a/drivers/gpu/drm/i915/intel_bios.c
> +++ b/drivers/gpu/drm/i915/intel_bios.c
> @@ -1247,7 +1247,7 @@ static void parse_ddi_ports(struct drm_i915_private *dev_priv,
> {
> enum port port;
>
> - if (!HAS_DDI(dev_priv))
> + if (!HAS_DDI(dev_priv) && !IS_CHERRYVIEW(dev_priv))
> return;
>
> if (!dev_priv->vbt.child_dev_num)
> --
> 2.11.0
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2017-10-09 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 8:21 [PATCH 0/8] drm/i915/bios: VBT parsing fixes and cleanups Jani Nikula
2017-09-28 8:21 ` [PATCH 1/8] drm/i915/bios: parse DDI ports also for CHV for HDMI DDC pin and DP AUX channel Jani Nikula
2017-10-09 16:45 ` Ville Syrjälä [this message]
2017-10-10 10:18 ` Jani Nikula
2017-09-28 8:21 ` [PATCH 2/8] drm/i915/bios: refactor parse general definitions Jani Nikula
2017-09-28 8:21 ` [PATCH 3/8] drm/i915/bios: don't initialize fields based on vbt version Jani Nikula
2017-09-28 8:22 ` [PATCH 4/8] drm/i915/bios: remove an unnecessary temp variable Jani Nikula
2017-09-28 8:22 ` [PATCH 5/8] drm/i915/bios: cleanup comments and useless return Jani Nikula
2017-09-28 8:22 ` [PATCH 6/8] drm/i915/bios: merge parse_device_mapping() into parse_general_definitions() Jani Nikula
2017-09-28 8:22 ` [PATCH 7/8] drm/i915/bios: parse SDVO device mapping from pre-parsed child devices Jani Nikula
2017-09-28 8:22 ` [PATCH 8/8] drm/i915/bios: don't pass bdb to parsers that don't parse VBT directly Jani Nikula
2017-09-28 8:47 ` ✓ Fi.CI.BAT: success for drm/i915/bios: VBT parsing fixes and cleanups Patchwork
2017-09-28 9:53 ` ✓ 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=20171009164546.GF10981@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=stable@vger.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 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).