All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Jackson <ajax@redhat.com>
To: Ian Pilcher <arequipeno@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: -next trees
Date: Wed, 26 Sep 2012 13:00:36 -0400	[thread overview]
Message-ID: <1348678836.4244.38.camel@atropine> (raw)
In-Reply-To: <5061FC41.7080009@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1401 bytes --]

On Tue, 2012-09-25 at 13:47 -0500, Ian Pilcher wrote:

> In the meantime, I would like to move the ball forward on this issue.
> As I see it, there 3 issues that have become conflated:
> 
> 1.  The display (LG L246WP) is confused by *any* InfoFrames.

If this is still the case after applying:

commit adf00b26d18e1b3570451296e03bcb20e4798cdd
Author: Paulo Zanoni <paulo.r.zanoni@intel.com>
Date:   Tue Sep 25 13:23:34 2012 -0300

    drm/i915: make sure we write all the DIP data bytes

Then I suspect I'm compelled to agree that we need a quirk to forcibly
disable InfoFrames entirely.  I don't like to be difficult about this,
but the HDMI spec is quite clear that sinks _must_ accept InfoFrames
defined in either the CEA or HDMI specs, so if we're seeing that class
of failure I tend to strongly suspect our drivers first.

> 3.  drm_detect_monitor_audio is returning true for the LG L246WP, which
>      definitely doesn't have any audio capabilities.  This may be a bug
>      in the display's EDID, or it may be a parsing error.

The display is definitely a filthy liar then:

  Audio data block
    Linear PCM, max channels 1
    Supported sample rates (kHz): 48 44.1 32
    Supported sample sizes (bits): 24 20 16

Hooray for hardware.  Not sure what the logic should be for whether to
send HDMI audio or not, I'll re-read the appropriate scrolls.

- ajax

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

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

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2012-09-26 17:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13  1:44 -next trees Dave Airlie
2012-09-13 22:10 ` Alex Deucher
2012-09-17 16:25 ` Rob Clark
2012-09-22  9:43 ` Paul Menzel
2012-09-23  4:34 ` Ian Pilcher
2012-09-24 14:34   ` Adam Jackson
2012-09-25 18:47     ` Ian Pilcher
2012-09-26 17:00       ` Adam Jackson [this message]
2012-09-26 21:04         ` Ian Pilcher
2012-09-27 14:42           ` Daniel Vetter
2012-09-28  7:03           ` [PATCH v5 0/3] Enhanced EDID quirk functionality Ian Pilcher
2012-09-28  7:03             ` [PATCH v5 1/3] drm: Add user-defined EDID quirks capability Ian Pilcher
2012-10-09 12:15               ` Jani Nikula
2012-10-09 15:13                 ` Ian Pilcher
2012-10-10  6:31                   ` Jani Nikula
2012-09-28  7:03             ` [PATCH v5 2/3] drm: Add EDID quirk to disable HDMI InfoFrames Ian Pilcher
2012-09-28  7:03             ` [PATCH v5 3/3] drm: Add EDID quirk for LG L246WP Ian Pilcher
2012-10-08 23:22             ` [PATCH v5 0/3] Enhanced EDID quirk functionality Ian Pilcher
2012-10-09 15:18               ` Adam Jackson
2016-09-28  3:31 -next trees Dave Airlie
2016-09-28 21:07 ` Alex Deucher
2016-09-29  9:47   ` Daniel Vetter
2016-09-29 16:23 ` Thierry Reding

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=1348678836.4244.38.camel@atropine \
    --to=ajax@redhat.com \
    --cc=arequipeno@gmail.com \
    --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.