public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Sharma, Shashank" <shashank.sharma@intel.com>
Cc: Nick Bowler <nbowler@draconx.ca>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: PROBLEM: Intel HDMI output busticated on 4.4 (regression)
Date: Tue, 9 Feb 2016 19:36:41 +0200	[thread overview]
Message-ID: <20160209173641.GU23290@intel.com> (raw)
In-Reply-To: <20160209170351.GT23290@intel.com>

On Tue, Feb 09, 2016 at 07:03:51PM +0200, Ville Syrjälä wrote:
> On Tue, Feb 09, 2016 at 04:39:21PM +0000, Sharma, Shashank wrote:
> > Hi Nick, 
> > 
> > Sonika is OOO for this week. 
> > AFAIK about this issue, looks like the live status is not getting set for your system, on HPD. 
> > 
> > As per the Bspec, we must check live status before trying to read EDID. 
> > Is it possible for you to check with an HDMI analyzer and probe live status register ?
> 
> BTW I'm not at all convinced about the current live status bit defines
> we have for g4x. Supposedly someone tested them and found that they
> don't match the spec, but IIRC when I tried them on one g4x machine
> here, they did match the spec (well, at least for the ports present
> on that particular board).
> 
> So something like this may or may not help:
> 
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index 188ad5de020f..80c08016e522 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -3302,9 +3302,9 @@ enum skl_disp_power_wells {
>   * Please check the detailed lore in the commit message for for experimental
>   * evidence.
>   */
> -#define   PORTD_HOTPLUG_LIVE_STATUS_G4X		(1 << 29)
> +#define   PORTD_HOTPLUG_LIVE_STATUS_G4X		(1 << 27)
>  #define   PORTC_HOTPLUG_LIVE_STATUS_G4X		(1 << 28)
> -#define   PORTB_HOTPLUG_LIVE_STATUS_G4X		(1 << 27)
> +#define   PORTB_HOTPLUG_LIVE_STATUS_G4X		(1 << 29)
>  /* VLV DP/HDMI bits again match Bspec */
>  #define   PORTD_HOTPLUG_LIVE_STATUS_VLV		(1 << 27)
>  #define   PORTC_HOTPLUG_LIVE_STATUS_VLV		(1 << 28)

Just retested the g4x machine here, and port B is definitely on bit 29,
port C on bit 28. No port D on ELK, so can't check that. So either
someone made a fumble when they tested this originally, or some boards
are just wired incorrectly, or CTG is where it was tested and that
actually disagrees with the spec for some reason.

> -- 
> 2.4.10
> 
> 
> > 
> > Regards
> > Shashank
> > -----Original Message-----
> > From: Nick Bowler [mailto:nbowler@draconx.ca] 
> > Sent: Tuesday, February 09, 2016 10:03 PM
> > To: Jindal, Sonika
> > Cc: linux-kernel@vger.kernel.org; dri-devel@lists.freedesktop.org; Daniel Vetter; Sharma, Shashank
> > Subject: Re: PROBLEM: Intel HDMI output busticated on 4.4 (regression)
> > 
> > On 1/28/16, Nick Bowler <nbowler@draconx.ca> wrote:
> > > On 2016-01-21, Nick Bowler <nbowler@draconx.ca> wrote:
> > >> On 2016-01-21, Jindal, Sonika <sonika.jindal@intel.com> wrote:
> > >>> On 1/21/2016 8:59 AM, Nick Bowler wrote:
> > >>>> On 1/20/16, Nick Bowler <nbowler@draconx.ca> wrote:
> > >>>>> On 2016-01-20, Jindal, Sonika <sonika.jindal@intel.com> wrote:
> > >> [...]
> > >>>>>> Does the same system works with any other monitor?
> > >>>>> I'll see if I can find another to try.
> > >>>> I tried another monitor, and the same problem occurs.
> > >>> Which make are these monitors?
> > >>
> > >>  - LG Flatron W2253V
> > >>  - Dell E228WFPc
> > >>
> > >>> Do you have any other system other than G45?
> > >>
> > >> Nothing else with Linux 4.4, unfortunately.
> > >
> > > Anything else you want me to try?
> > >
> > > This issue is still present in 4.5-rc1.
> > 
> > Ping?
> > 
> > HDMI is still broken on my system in 4.5-rc3.
> > 
> > Cheers,
> >   Nick
> > _______________________________________________
> > dri-devel mailing list
> > dri-devel@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/dri-devel
> 
> -- 
> Ville Syrjälä
> Intel OTC
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2016-02-09 17:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 22:26 PROBLEM: Intel HDMI output busticated on 4.4 (regression) Nick Bowler
2016-01-20  4:30 ` Jindal, Sonika
2016-01-20 15:33   ` Nick Bowler
2016-01-21  3:29     ` Nick Bowler
2016-01-21 11:07       ` Jindal, Sonika
2016-01-21 13:57         ` Nick Bowler
2016-01-28  6:00           ` Nick Bowler
2016-02-09 16:33             ` Nick Bowler
2016-02-09 16:39               ` Sharma, Shashank
2016-02-09 17:03                 ` Ville Syrjälä
2016-02-09 17:36                   ` Ville Syrjälä [this message]
2016-02-09 18:22                     ` Ville Syrjälä
2016-02-10  4:43                       ` Sharma, Shashank
2016-02-09 18:02                   ` Nick Bowler
2016-02-10  9:00                     ` Jani Nikula

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=20160209173641.GU23290@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbowler@draconx.ca \
    --cc=shashank.sharma@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