All of lore.kernel.org
 help / color / mirror / Atom feed
From: Knut Petersen <Knut_Petersen@t-online.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915/sdvo: If at first we don't succeed in reading the response, wait
Date: Tue, 25 Jan 2011 23:01:45 +0100	[thread overview]
Message-ID: <4D3F4849.4030905@t-online.de> (raw)
In-Reply-To: <1295967967-26041-1-git-send-email-chris@chris-wilson.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1735 bytes --]

Am 25.01.2011 16:06, schrieb Chris Wilson:
> We were not pausing after detecting the response was pending and so did
> not allow the hardware sufficient time to complete before aborting. This
> lead to transient failures whilst probing SDVO devices.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
>
> Knut, this should fix one of the failures in the log:
>
> [  680.371855] [drm:intel_sdvo_debug_write], SDVOC: W: 0B (SDVO_CMD_GET_ATTACHED_DISPLAYS)
> [  680.417190] [drm:intel_sdvo_write_cmd], command returns response Pending [4]
>
> which caused the detect routine to return connector_status_unknown.
>
> However, there is still immediately following that:
>
> [  680.419880] [drm:intel_sdvo_debug_write], SDVOC: W: 11 00 00 (SDVO_CMD_SET_TARGET_OUTPUT)
> [  680.450190] [drm:intel_sdvo_write_cmd], command returns response Invalid arg 
> [3]
>
> which implies that we are mishandling that odd VGA-2 connector.
> -Chris
>
>   

Well, you are great, better than you thought yourself ;-)

The floating VGA-2 status is rock solid now, both problems solved.

The machine idles at 800Mhz, load increases speed to 1860 MHz. The code had
actually less time to execute under load, time became to short without
the delay ...

I think that patch also should be a candidate for 2.6.37.1 as it fixes a
regression
introduced in 2.6.37.

Something new:

Have a look at the attached new log.  I connected a 2nd monitor, so
there is a monitor attached to both
the VGA-1 and DVI-1 connectors. At the framebuffer console prompt (no X
running)
I changed to console 2 and back to console 1. The log starts at the
point of switching
back to console 1. Now ... shouldn't I read something about a
output_poll_execute for VGA-1?

Knut




[-- Attachment #2: 2Chris --]
[-- Type: text/plain, Size: 2772 bytes --]

[  629.662700] [drm:drm_crtc_helper_set_config],
[  629.662705] [drm:drm_crtc_helper_set_config], [CRTC:3] [FB:87] #connectors=1 (x y) (0 0)
[  629.662724] [drm:drm_crtc_helper_set_config], [CONNECTOR:5:VGA-1] to [CRTC:3]
[  629.662728] [drm:drm_crtc_helper_set_config], [CONNECTOR:8:DVI-D-1] to [CRTC:4]
[  629.662732] [drm:drm_crtc_helper_set_config], Setting connector DPMS state to on
[  629.662735] [drm:drm_crtc_helper_set_config],  [CONNECTOR:5:VGA-1] set DPMS on
[  629.662739] [drm:drm_crtc_helper_set_config],
[  629.662741] [drm:drm_crtc_helper_set_config], [CRTC:4] [FB:87] #connectors=1 (x y) (0 0)
[  629.662749] [drm:drm_crtc_helper_set_config], [CONNECTOR:5:VGA-1] to [CRTC:3]
[  629.662753] [drm:drm_crtc_helper_set_config], [CONNECTOR:8:DVI-D-1] to [CRTC:4]
[  629.662756] [drm:drm_crtc_helper_set_config], Setting connector DPMS state to on
[  629.662760] [drm:drm_crtc_helper_set_config],  [CONNECTOR:8:DVI-D-1] set DPMS on

[  631.576055] [drm:intel_sdvo_debug_write], SDVOB: W: 0B                         (SDVO_CMD_GET_ATTACHED_DISPLAYS)
[  631.587810] [drm:intel_sdvo_read_response], SDVOB: R: (Success) 01 00
[  631.604015] [drm:intel_sdvo_detect], SDVO response 1 0 [1]
[  631.606959] [drm:intel_sdvo_debug_write], SDVOB: W: 7A 02                      (SDVO_CMD_SET_CONTROL_BUS_SWITCH)
[  631.624124] [drm:intel_sdvo_debug_write], SDVOB: W: 7A 02                      (SDVO_CMD_SET_CONTROL_BUS_SWITCH)
[  631.755023] [drm:output_poll_execute], [CONNECTOR:8:DVI-D-1] status updated from 1 to 1
[  631.758257] [drm:intel_sdvo_debug_write], SDVOC: W: 0B                         (SDVO_CMD_GET_ATTACHED_DISPLAYS)
[  631.839893] [drm:intel_sdvo_read_response], SDVOC: R: (Success) 00 00
[  631.860027] [drm:intel_sdvo_detect], SDVO response 0 0 [2]
[  631.862974] [drm:output_poll_execute], [CONNECTOR:44:VGA-2] status updated from 2 to 2

[  634.880024] [drm:intel_sdvo_debug_write], SDVOB: W: 0B                         (SDVO_CMD_GET_ATTACHED_DISPLAYS)
[  634.895785] [drm:intel_sdvo_read_response], SDVOB: R: (Success) 01 00
[  634.920022] [drm:intel_sdvo_detect], SDVO response 1 0 [1]
[  634.922971] [drm:intel_sdvo_debug_write], SDVOB: W: 7A 02                      (SDVO_CMD_SET_CONTROL_BUS_SWITCH)
[  634.945705] [drm:intel_sdvo_debug_write], SDVOB: W: 7A 02                      (SDVO_CMD_SET_CONTROL_BUS_SWITCH)
[  635.270273] [drm:output_poll_execute], [CONNECTOR:8:DVI-D-1] status updated from 1 to 1
[  635.288772] [drm:intel_sdvo_debug_write], SDVOC: W: 0B                         (SDVO_CMD_GET_ATTACHED_DISPLAYS)
[  635.449262] [drm:intel_sdvo_read_response], SDVOC: R: (Success) 00 00
[  635.493740] [drm:intel_sdvo_detect], SDVO response 0 0 [2]
[  635.510435] [drm:output_poll_execute], [CONNECTOR:44:VGA-2] status updated from 2 to 2

  reply	other threads:[~2011-01-25 22:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 18:48 [BUG/REGRESSION] DRM / i915 / 2.6.37 and 2.6.38-rc*: DVI output gets disabled/reenabled under load Knut Petersen
2011-01-24 19:13 ` Chris Wilson
2011-01-25 11:50   ` Knut Petersen
2011-01-25 12:11     ` Chris Wilson
2011-01-25 12:35       ` Knut Petersen
2011-01-25 13:50         ` Chris Wilson
2011-01-25 14:14       ` Knut Petersen
2011-01-25 14:44         ` Chris Wilson
2011-01-25 15:06     ` [PATCH] drm/i915/sdvo: If at first we don't succeed in reading the response, wait Chris Wilson
2011-01-25 22:01       ` Knut Petersen [this message]
2011-01-25 22:11         ` [PATCH] drm/i915/sdvo: If at first we dont " Chris Wilson
2011-01-25 22:32           ` Knut Petersen

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=4D3F4849.4030905@t-online.de \
    --to=knut_petersen@t-online.de \
    --cc=chris@chris-wilson.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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.