All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Pilcher <arequipeno@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>, Adam Jackson <ajax@redhat.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: -next queue and EDID stuff
Date: Wed, 29 Aug 2012 14:53:03 -0500	[thread overview]
Message-ID: <503E731F.2020303@gmail.com> (raw)
In-Reply-To: <20120829075616.GA5278@phenom.ffwll.local>

On 08/29/2012 02:56 AM, Daniel Vetter wrote:
> Wrt intel infoframes issues: Have you retested on latest 3.6-rc kernels?
> We've fixed quite a few bugs for our infoframe support recently ...

Tested just now.  The behavior has changed.  I now need to use *both*
flags to make my display work with an Intel GPU.  (Previously, the
NO_AUDIO flag was sufficient to make the display work with Intel
graphics.)  Presumably, the Intel driver is now sending AVI InfoFrames.

Thinking a bit more about this, I'm starting to rethink my assertion
that the Intel driver is at fault here.  On one hand, it doesn't make
any sense to send audio InfoFrames to a non-HDMI display.  (BTW, I'm
assuming that a display with a DisplayPort port will show up as HDMI.)

On the other hand, it can be argued that the DRM layer is giving
conflicting information to the driver -- drm_detect_hdmi_monitor is
returning FALSE, but drm_detect_monitor_audio is returning TRUE.  AFAIK,
this doesn't make any sense either.

This leads me to propose that drm_detect_monitor_audio return FALSE if
either EDID_QUIRK_DISABLE_INFOFRAMES or EDID_QUIRK_NO_AUDIO is set.

bool drm_detect_monitor_audio(struct edid *edid)
{
         u8 *edid_ext;
         int i, j;
         bool has_audio = false;
         int start_offset, end_offset;
         char buf[EDID_DISPLAY_ID_BUF_SIZE];

         if (edid_get_quirks(edid) & (EDID_QUIRK_NO_AUDIO |
                                      EDID_QUIRK_DISABLE_INFOFRAMES)) {
                 DRM_INFO("Disabling HDMI audio on display %s "
                          "due to EDID quirk\n",
                          drm_edid_display_id_format(edid->display_id,
                                                     buf, 1));
                 goto end;
         }

         ...

EDID_QUIRK_DISABLE_INFOFRAMES would then be sufficient to make the LG
L246WP work with both nVidia and Intel GPUs.  (ATI GPUs should work as
well; I just don't have any hardware to test.)

Ajax - Does this address your objections?  If so, I'll spin another
patch set.

Thanks!

-- 
========================================================================
Ian Pilcher                                         arequipeno@gmail.com
"If you're going to shift my paradigm ... at least buy me dinner first."
========================================================================

  reply	other threads:[~2012-08-29 19:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23 23:50 -next queue and EDID stuff Dave Airlie
2012-08-27 20:24 ` Adam Jackson
2012-08-27 20:34   ` Alex Deucher
2012-08-27 20:47     ` Adam Jackson
2012-08-27 21:51   ` Daniel Vetter
2012-08-27 23:04   ` Ben Skeggs
2012-08-28 23:33   ` Ian Pilcher
2012-08-29  0:13     ` Adam Jackson
2012-08-29  4:18       ` Ian Pilcher
2012-08-29  7:56         ` Daniel Vetter
2012-08-29 19:53           ` Ian Pilcher [this message]
2012-08-29 21:38             ` Adam Jackson
2012-08-30  5:23               ` Ian Pilcher
2012-08-30  7:41                 ` Daniel Vetter
2012-09-04 14:02                 ` Ian Pilcher
2012-09-11 13:59                   ` Ian Pilcher
2012-08-28  8:41 ` Baurzhan Ismagulov

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=503E731F.2020303@gmail.com \
    --to=arequipeno@gmail.com \
    --cc=ajax@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.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.