public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Clint Taylor <clinton.a.taylor@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: revert intel_dp_probe_oui call during HPD interrupt handler
Date: Fri, 06 Jun 2014 09:36:22 -0700	[thread overview]
Message-ID: <5391EE06.6050507@intel.com> (raw)
In-Reply-To: <20140605092629.GV7416@phenom.ffwll.local>

On 06/05/2014 02:26 AM, Daniel Vetter wrote:
> On Wed, Jun 04, 2014 at 03:29:41PM -0700, clinton.a.taylor@intel.com wrote:
>> From: Clint Taylor <clinton.a.taylor@intel.com>
>>
>> Remove OUI read function from the lower half interrupt handler. Upon
>> closing the eDP panel lid an HPD interrupt is generated. The lower half
>> handler calls intel_dp_probe_oui() as part of intel_dp_detect().
>> intel_dp_probe_oui() enables eDP VDD and subsequently disables eDP VDD
>> causing another HPD interrupt. This cycle repeats every 3.6 seconds with
>> VDD asserted for 3.5 of those seconds until the lid is opened again.
>>
>> Revert of 0d198328538276c4459ef5de081e68ae60e6c4c2
>> Revert of 351cfc34db8decb0c5cc1aac7cf1780a0e45c8b1
>>
>> Signed-off-by: Clint Taylor <clinton.a.taylor@intel.com>
>
> Hm, this is funky ... we currently don't handle port A hotplug events, and
> we filter hotplug events properly.
>
This is a Port A panel on ValleyView.


> How does this exactly blow up for you? Or is this port D?
>
[  219.723752] [drm:ironlake_panel_vdd_off_sync], PP_STATUS: 0x00000000 
PP_CONTROL: 0xabcd0000
[  219.823937] [drm:valleyview_irq_handler], hotplug event received, 
stat 0x20100000
[  219.823964] [drm:intel_hpd_irq_handler], Received HPD interrupt on 
PIN 5 - cnt: 0
[  219.824153] [drm:i915_hotplug_work_func], running encoder hotplug 
functions
[  219.824175] [drm:i915_hotplug_work_func], Connector eDP-1 (pin 5) 
received hotplug event.
[  219.824193] [drm:i915_hotplug_work_func], Connector HDMI-A-1 (pin 5) 
received hotplug event.
[  219.824213] [drm:intel_dp_detect], [CONNECTOR:14:eDP-1]
[  219.824229] [drm:ironlake_edp_panel_vdd_on], Turn eDP VDD on

The valleyview_irq_handler() is receiving the HPD event and 
i915_hotplug_work_func() is calling intel_dp_detect().



> We might want to have some filtering here checking whether the edp panel
> is on or off. Also the delayed work is _way_ too long.

We could filter if the lid is closed, but it seemed a lot safer to 
remove the function. Or we could move the Sink and branch OUI reads to 
the training function. If OUI is necessary we should probably also save 
the values to the context.

> -Daniel
>
>> ---
>>   drivers/gpu/drm/i915/intel_dp.c |   23 -----------------------
>>   1 file changed, 23 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
>> index 2a00cb8..246d2c1 100644
>> --- a/drivers/gpu/drm/i915/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/intel_dp.c
>> @@ -2867,27 +2867,6 @@ intel_dp_get_dpcd(struct intel_dp *intel_dp)
>>   	return true;
>>   }
>>
>> -static void
>> -intel_dp_probe_oui(struct intel_dp *intel_dp)
>> -{
>> -	u8 buf[3];
>> -
>> -	if (!(intel_dp->dpcd[DP_DOWN_STREAM_PORT_COUNT] & DP_OUI_SUPPORT))
>> -		return;
>> -
>> -	intel_edp_panel_vdd_on(intel_dp);
>> -
>> -	if (intel_dp_dpcd_read_wake(&intel_dp->aux, DP_SINK_OUI, buf, 3) == 3)
>> -		DRM_DEBUG_KMS("Sink OUI: %02hx%02hx%02hx\n",
>> -			      buf[0], buf[1], buf[2]);
>> -
>> -	if (intel_dp_dpcd_read_wake(&intel_dp->aux, DP_BRANCH_OUI, buf, 3) == 3)
>> -		DRM_DEBUG_KMS("Branch OUI: %02hx%02hx%02hx\n",
>> -			      buf[0], buf[1], buf[2]);
>> -
>> -	edp_panel_vdd_off(intel_dp, false);
>> -}
>> -
>>   int intel_dp_sink_crc(struct intel_dp *intel_dp, u8 *crc)
>>   {
>>   	struct intel_digital_port *intel_dig_port = dp_to_dig_port(intel_dp);
>> @@ -3178,8 +3157,6 @@ intel_dp_detect(struct drm_connector *connector, bool force)
>>   	if (status != connector_status_connected)
>>   		goto out;
>>
>> -	intel_dp_probe_oui(intel_dp);
>> -
>>   	if (intel_dp->force_audio != HDMI_AUDIO_AUTO) {
>>   		intel_dp->has_audio = (intel_dp->force_audio == HDMI_AUDIO_ON);
>>   	} else {
>> --
>> 1.7.9.5
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>

  parent reply	other threads:[~2014-06-06 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 22:29 [PATCH] drm/i915: revert intel_dp_probe_oui call during HPD interrupt handler clinton.a.taylor
2014-06-05  9:26 ` Daniel Vetter
2014-06-06  9:41   ` Jani Nikula
2014-06-06 18:13     ` Clint Taylor
2014-06-06 19:54       ` Jani Nikula
2014-06-06 20:14         ` Dave Airlie
2014-06-06 20:17           ` Daniel Vetter
2014-06-06 16:36   ` Clint Taylor [this message]
     [not found]   ` <5390AB8D.4080908@outlook.or.com>
2014-06-06 17:24     ` 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=5391EE06.6050507@intel.com \
    --to=clinton.a.taylor@intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=daniel@ffwll.ch \
    /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