public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: ville.syrjala@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/i915: Allow HDMI+HDMI cloning on g4x
Date: Wed, 5 Mar 2014 19:21:58 +0100	[thread overview]
Message-ID: <20140305182158.GW17001@phenom.ffwll.local> (raw)
In-Reply-To: <1393856131-16961-5-git-send-email-ville.syrjala@linux.intel.com>

On Mon, Mar 03, 2014 at 04:15:31PM +0200, ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> BSpec is a bit unclear whether HDMI+HDMI cloning should work on g4x.
> Tests on real hardware say that it does. Since g4x can't send
> infoframes to more than one HDMI port anyway, we don't lose anything
> by allow it.
> 
> For PCH platforms BSpec explicitly forbids HDMI+HDMI cloning.
> 
> Whether HDMI+HDMI cloning might also work on VLV is a bit unclear, but
> since we'd at least lose the capability of sending infoframes to more
> than one cloned HDMI port, it doesn't seem like a good idea to allow it.
> 
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=73850
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>  drivers/gpu/drm/i915/intel_hdmi.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
> index 9dacb33..4eb30d8 100644
> --- a/drivers/gpu/drm/i915/intel_hdmi.c
> +++ b/drivers/gpu/drm/i915/intel_hdmi.c
> @@ -1316,6 +1316,13 @@ void intel_hdmi_init(struct drm_device *dev, int hdmi_reg, enum port port)
>  	intel_encoder->type = INTEL_OUTPUT_HDMI;
>  	intel_encoder->crtc_mask = (1 << 0) | (1 << 1) | (1 << 2);
>  	intel_encoder->cloneable = 1 << INTEL_OUTPUT_ANALOG;
> +	/*
> +	 * BSpec is unclear about HDMI+HDMI cloning on g4x, but it seems
> +	 * to work on real hardware. And since g4x can send infoframes to
> +	 * only one port anyway, nothing is lost by allowing it.
> +	 */
> +	if (IS_G4X(dev))

Why restrict this? The per-encoder infoframe setup should dtrt everywhere
else I hope ...
-Daniel

> +		intel_encoder->cloneable |= 1 << INTEL_OUTPUT_HDMI;
>  
>  	intel_dig_port->port = port;
>  	intel_dig_port->hdmi.hdmi_reg = hdmi_reg;
> -- 
> 1.8.3.2
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-03-05 18:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03 14:15 [PATCH 0/4] drm/915: Relax output cloning restrictions ville.syrjala
2014-03-03 14:15 ` [PATCH 1/4] drm/i915: Make encoder cloning more flexible ville.syrjala
2014-03-05 18:20   ` Daniel Vetter
2014-03-05 18:47     ` Ville Syrjälä
2014-03-10 18:27   ` Rodrigo Vivi
2014-03-10 19:17     ` Ville Syrjälä
2014-03-03 14:15 ` [PATCH 2/4] drm/i915: Don't use HDMI 12bpc when cloning with other encoder types ville.syrjala
2014-03-10 18:31   ` Rodrigo Vivi
2014-03-03 14:15 ` [PATCH 3/4] drm/i915: Allow HDMI+VGA cloning ville.syrjala
2014-03-10 18:41   ` Rodrigo Vivi
2014-03-03 14:15 ` [PATCH 4/4] drm/i915: Allow HDMI+HDMI cloning on g4x ville.syrjala
2014-03-05 18:21   ` Daniel Vetter [this message]
2014-03-05 18:41     ` Ville Syrjälä
2014-03-10 18:50   ` Rodrigo Vivi
2014-03-10 20:49     ` Daniel Vetter

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=20140305182158.GW17001@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@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