public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Jindal, Sonika" <sonika.jindal@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v2 7/7] drm/i915/bxt: Use correct live status	register for BXT platform
Date: Wed, 26 Aug 2015 09:35:10 +0300	[thread overview]
Message-ID: <876142a76p.fsf@intel.com> (raw)
In-Reply-To: <000C66961D35964B9714611E548C10AD0C2A67CC@BGSMSX104.gar.corp.intel.com>

On Wed, 26 Aug 2015, "Jindal, Sonika" <sonika.jindal@intel.com> wrote:
> Oh, bxt is here..:) Spoke too soon..
> But will need to make it based upon intel_encoder->hpd_pin because of the A0/A1 WA for BXT.

That should anyway be a separate patch changing the port->port to a port
acquired from pin_to_port. We'll take it out after we don't need to
support A0/A1. Also, that should have a comment there.

> Also, we need to make intel_digital_port_connected global to be accessed from intel_hdmi.c

Trivial addition in your series.

BR,
Jani.

>
> Regards,
> Sonika
>
> -----Original Message-----
> From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf Of Jani Nikula
> Sent: Thursday, August 20, 2015 1:18 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Nikula, Jani
> Subject: [Intel-gfx] [PATCH v2 7/7] drm/i915/bxt: Use correct live status register for BXT platform
>
> BXT platform uses live status bits from 0x44440 register to obtain DP status on hotplug. The existing g4x_digital_port_connected() uses a different register and hence misses DP hotplug events on BXT platform. This patch fixes it by using the appropriate register(0x44440) and live status bits(3:5).
>
> Based on a patch by Durgadoss R <durgadoss.r@intel.com>, from whom the commit message is shamelessly copy pasted.
>
> Reported-by: Durgadoss R <durgadoss.r@intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_dp.c | 25 +++++++++++++++++++++++++
>  1 file changed, 25 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c index 36291838409b..508156cc750d 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -4569,6 +4569,29 @@ static bool vlv_digital_port_connected(struct drm_i915_private *dev_priv,
>  	return I915_READ(PORT_HOTPLUG_STAT) & bit;  }
>  
> +static bool bxt_digital_port_connected(struct drm_i915_private *dev_priv,
> +				       struct intel_digital_port *port) {
> +	u32 bit;
> +
> +	switch (port->port) {
> +	case PORT_A:
> +		bit = BXT_DE_PORT_HP_DDIA;
> +		break;
> +	case PORT_B:
> +		bit = BXT_DE_PORT_HP_DDIB;
> +		break;
> +	case PORT_C:
> +		bit = BXT_DE_PORT_HP_DDIC;
> +		break;
> +	default:
> +		MISSING_CASE(port->port);
> +		return false;
> +	}
> +
> +	return I915_READ(GEN8_DE_PORT_ISR) & bit; }
> +
>  /*
>   * intel_digital_port_connected - is the specified port connected?
>   * @dev_priv: i915 private structure
> @@ -4583,6 +4606,8 @@ static bool intel_digital_port_connected(struct drm_i915_private *dev_priv,
>  		return ibx_digital_port_connected(dev_priv, port);
>  	if (HAS_PCH_SPLIT(dev_priv))
>  		return cpt_digital_port_connected(dev_priv, port);
> +	else if (IS_BROXTON(dev_priv))
> +		return bxt_digital_port_connected(dev_priv, port);
>  	else if (IS_VALLEYVIEW(dev_priv))
>  		return vlv_digital_port_connected(dev_priv, port);
>  	else
> --
> 2.1.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-08-26  6:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20  7:47 [PATCH v2 0/7] drm/i915: clean up *_digital_port_connected Jani Nikula
2015-08-20  7:47 ` [PATCH v2 1/7] drm/i915: move ibx_digital_port_connected to intel_dp.c Jani Nikula
2015-08-26  5:04   ` Jindal, Sonika
2015-08-20  7:47 ` [PATCH v2 2/7] drm/i915: make g4x_digital_port_connected return boolean status Jani Nikula
2015-08-20  8:17   ` R, Durgadoss
2015-08-20  7:47 ` [PATCH v2 3/7] drm/i915: add MISSING_CASE annotation to ibx_digital_port_connected Jani Nikula
2015-08-20 14:26   ` R, Durgadoss
2015-08-20  7:47 ` [PATCH v2 4/7] drm/i915: add common intel_digital_port_connected function Jani Nikula
2015-08-26  5:26   ` Jindal, Sonika
2015-08-26 15:18   ` Sivakumar Thulasimani
2015-08-27  7:00     ` Jani Nikula
2015-08-27  8:01       ` Sivakumar Thulasimani
2015-08-27  8:08         ` Jani Nikula
2015-08-27  8:12           ` Sivakumar Thulasimani
2015-08-20  7:47 ` [PATCH v2 5/7] drm/i915: split ibx_digital_port_connected to ibx and cpt variants Jani Nikula
2015-08-20  7:47 ` [PATCH v2 6/7] drm/i915: split g4x_digital_port_connected to g4x and vlv variants Jani Nikula
2015-08-20  7:47 ` [PATCH v2 7/7] drm/i915/bxt: Use correct live status register for BXT platform Jani Nikula
2015-08-26  5:32   ` Jindal, Sonika
2015-08-26  6:35     ` Jani Nikula [this message]
2015-08-26  9:01 ` [PATCH v2 0/7] drm/i915: clean up *_digital_port_connected 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=876142a76p.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sonika.jindal@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