From: Alex Deucher <alexdeucher@gmail.com>
To: Thomas Reim <thomas.reim@nepomuc.de>
Cc: reimth@googlemail.com, Dave Airlie <airlied@redhat.com>,
Mario Kleiner <mario.kleiner@tuebingen.mpg.de>,
Jean Delvare <khali@linux-fr.org>,
Tyson Whitehead <twhitehead@gmail.com>,
Jason Wessel <jason.wessel@windriver.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Thomas Reim <rdratlos@yahoo.co.uk>
Subject: Re: [PATCH 1/1] drm/radeon: Fix Asus M2A-VM HDMI EDID error flooding problem
Date: Wed, 22 Jun 2011 11:45:15 -0400 [thread overview]
Message-ID: <BANLkTin8PpQWrGaCCQMQY+6A5QnXWxsKDQ@mail.gmail.com> (raw)
In-Reply-To: <1308755870.3655.36.camel@Mark-Aurel.gas.de>
On Wed, Jun 22, 2011 at 11:17 AM, Thomas Reim <thomas.reim@nepomuc.de> wrote:
> Dear Alex,
>
>> This is going to enable your quirk on every board with an HDMI port.
>> If we need to add a quirk for your board, let's make it board
>> specific. It might be better to just disable edid polling for certain
>> connectors on certain boards if they cause problems when no monitor is
>> detected.
>>
>> Alex
>
> Initially, I made the quirk only for the Asus board, because I only have
> this one to test. But the quirk applies of course to all boards that use
> the RS690 type chipset.
>
> I went through a couple of the many and various bugs that reported the
> EDID error/dump flooding problem. Beside of RS690, also at least RS630,
> RV770 and R350 are affected by this problem. In addition, I also found a
> bug report on Intel 945 GM that seems to have the same root cause.
>
> The majority of the bugs (ca. 80%) report a problem with the HDMI-A
> connector. 15% have a problem with the DVI-I connector and 5% have a
> problem with the LVDS connector.
>
> The proposed patch currently concentrates on the HDMI-A connector, only.
>
I think it would be better to add a quirk flag and only do the
extended probe on specific boards where it is required. E.g.,
if (radeon_connector->requires_extended_probe)
radeon_ddc_probe_extended();
else
radeon_ddc_probe();
Alex
> Based on Jean's proposal I updated the patch, so that
> radeon_ddc_edid_probe() now replaces radeon_ddc_probe() for all HDMI-A
> connectors.
>
> According to the VESA standards we could also do this for all connector
> types in general. DDC is i2c plus EDID. Without the patch
> radeon_ddc_probe() probes DDC by checking, if data at all can be
> retrieved from i2c port 0x50 (where the EDID is provided). New
> radeon_ddc_edid_probe() just checks in addition, if the EDID header and
> version/revision information is available and according to the VESA
> standards.
>
> Then and only then (for the HDMI-A connectors) we let drm_get_edid() and
> drm_edid_block_valid() check the EDID checksum and probe the validity of
> the EDID.
>
> According to VESA's implementation guide this is the right approach:
> Checking the exact match of the EDID header and that the revision number
> is in valid range is mandatory.
>
> Based on Jean's comments, I believe that it makes sense to have EDID
> polling enabled as there might be temporary communication problems
> between graphics card and monitor. These should be logged. This also
> applies for the buggy HDMI-A connectors, as soon as a monitor is
> connected to them.
>
> Hope this helps you.
>
> Best regards
>
> Thomas
>
>
>
>
next prev parent reply other threads:[~2011-06-22 15:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 15:31 [PATCH 1/1] drm/radeon: Fix Asus M2A-VM HDMI EDID error flooding problem Thomas Reim
2011-06-21 15:37 ` Alex Deucher
2011-06-21 18:03 ` Thomas Reim
2011-06-21 19:27 ` Jean Delvare
2011-06-22 1:11 ` Thomas Reim
2011-06-22 13:53 ` Jean Delvare
2011-06-22 1:20 ` reimth
2011-06-22 1:28 ` Alex Deucher
2011-06-22 15:17 ` Thomas Reim
2011-06-22 15:41 ` Alex Deucher
2011-06-22 15:45 ` Alex Deucher [this message]
2011-06-23 21:57 ` Thomas Reim
2011-06-23 22:05 ` [PATCH] " reimth
2011-06-23 22:55 ` Alex Deucher
2011-06-24 4:02 ` Thomas Reim
2011-06-24 13:36 ` Alex Deucher
2011-06-27 12:14 ` Jean Delvare
2011-07-06 9:35 ` Thomas Reim
2011-07-06 10:09 ` reimth
2011-07-06 12:26 ` Thomas Reim
2011-07-06 15:39 ` Alex Deucher
2011-07-06 15:42 ` Alex Deucher
2011-07-06 23:30 ` [PATCH 0/3] " reimth
2011-07-20 8:34 ` [PATCH] drm/radeon: Fix ECS A740GM-M DVI-D " reimth
2011-07-20 22:18 ` Thomas Reim
2011-07-26 13:05 ` Alex Deucher
2011-07-06 23:30 ` [PATCH 3/3] drm/radeon: Log Subsystem Vendor and Device Information reimth
2011-07-07 13:56 ` Alex Deucher
2011-07-06 23:30 ` [PATCH 2/3] drm/radeon: Fix Asus M2A-VM HDMI EDID error flooding problem reimth
2011-07-07 14:01 ` Alex Deucher
2011-07-26 13:20 ` Dave Airlie
2011-07-26 14:52 ` Alex Deucher
2011-07-26 14:55 ` Alex Deucher
2011-07-06 23:30 ` [PATCH 1/3] drm: Separate EDID Header Check from EDID Block Check reimth
2011-07-06 23:56 ` [stable] " Greg KH
2011-07-07 13:57 ` Alex Deucher
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=BANLkTin8PpQWrGaCCQMQY+6A5QnXWxsKDQ@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason.wessel@windriver.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.kleiner@tuebingen.mpg.de \
--cc=rdratlos@yahoo.co.uk \
--cc=reimth@googlemail.com \
--cc=thomas.reim@nepomuc.de \
--cc=twhitehead@gmail.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;
as well as URLs for NNTP newsgroup(s).