All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Nick Bowler" <nbowler@draconx.ca>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: PROBLEM: Intel HDMI output busticated on 4.4 (regression)
Date: Wed, 10 Feb 2016 11:00:58 +0200	[thread overview]
Message-ID: <8737t10wj9.fsf@intel.com> (raw)
In-Reply-To: <CADyTPEzA7MKvXCH5iLuD_abAQnkwAQ0EDt9e_hQGD26Qf6uN7g@mail.gmail.com>

On Tue, 09 Feb 2016, Nick Bowler <nbowler@draconx.ca> wrote:
> On 2/9/16, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
>> 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)
>
> Well, I applied this on 4.5-rc3 and it seems to fix things.

Ville, please do a proper patch, using your best judgement on elk
vs. ctg difference.

BR,
Jani.

>
> Thanks,
>   Nick
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Nick Bowler" <nbowler@draconx.ca>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel\@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: PROBLEM: Intel HDMI output busticated on 4.4 (regression)
Date: Wed, 10 Feb 2016 11:00:58 +0200	[thread overview]
Message-ID: <8737t10wj9.fsf@intel.com> (raw)
In-Reply-To: <CADyTPEzA7MKvXCH5iLuD_abAQnkwAQ0EDt9e_hQGD26Qf6uN7g@mail.gmail.com>

On Tue, 09 Feb 2016, Nick Bowler <nbowler@draconx.ca> wrote:
> On 2/9/16, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
>> 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)
>
> Well, I applied this on 4.5-rc3 and it seems to fix things.

Ville, please do a proper patch, using your best judgement on elk
vs. ctg difference.

BR,
Jani.

>
> Thanks,
>   Nick
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2016-02-10  9:01 UTC|newest]

Thread overview: 22+ 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  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 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 16:39                 ` Sharma, Shashank
2016-02-09 17:03                 ` Ville Syrjälä
2016-02-09 17:03                   ` Ville Syrjälä
2016-02-09 17:36                   ` Ville Syrjälä
2016-02-09 18:22                     ` Ville Syrjälä
2016-02-09 18:22                       ` Ville Syrjälä
2016-02-10  4:43                       ` Sharma, Shashank
2016-02-10  4:43                         ` Sharma, Shashank
2016-02-09 18:02                   ` Nick Bowler
2016-02-10  9:00                     ` Jani Nikula [this message]
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=8737t10wj9.fsf@intel.com \
    --to=jani.nikula@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=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 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.