linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Nick Bowler <nbowler@elliptictech.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Keith Packard <keithp@keithp.com>
Subject: Re: Linux 3.3-rc2
Date: Thu, 2 Feb 2012 11:35:24 +0800	[thread overview]
Message-ID: <20120202033524.GA11360@localhost> (raw)
In-Reply-To: <20120201175651.GA3300@elliptictech.com>

Nick,

[snip]
> However, the _very next commit_:
> 
>   2deed761188d ("drm/i915: HDMI hot remove notification to audio driver")
> 
> reintroduces the log spam every mode change, with two additional lines
> printed each time (the lines prefixed with an asterisk are new):
> 
> * HDMI hot plug event: Codec=3 Pin=3 Presence_Detect=0 ELD_Valid=1
> * HDMI status: Codec=3 Pin=3 Presence_Detect=0 ELD_Valid=0
>   HDMI hot plug event: Codec=3 Pin=3 Presence_Detect=1 ELD_Valid=1
>   HDMI status: Codec=3 Pin=3 Presence_Detect=1 ELD_Valid=1
>   HDMI: detected monitor W2253 at connection type HDMI
>   HDMI: available speakers: FL/FR
>   HDMI: supports coding type LPCM: channels = 2, rates = 32000 44100 48000, bits = 16 20 24

Actually we have another patch to disable all the above printk lines:

alsa: hide HDMI/ELD printks unless in debug kernels
http://lists.freedesktop.org/archives/intel-gfx/2011-November/013322.html

And the plan is to merge it in the next release of all the ELD fixes,
which should be 3.4.

Thanks,
Fengguang

  reply	other threads:[~2012-02-02  3:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 21:59 Linux 3.3-rc2 Linus Torvalds
2012-02-01 17:56 ` Nick Bowler
2012-02-02  3:35   ` Wu Fengguang [this message]
2012-04-02 15:56     ` Nick Bowler
2012-02-02 21:05 ` Roland Dreier
2012-02-03 18:31   ` Linus Torvalds
     [not found] <20120201150015.EBB2413A4D6@koiott.cyber.ee>
2012-02-01 15:16 ` Meelis Roos

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=20120202033524.GA11360@localhost \
    --to=fengguang.wu@intel.com \
    --cc=keithp@keithp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbowler@elliptictech.com \
    --cc=torvalds@linux-foundation.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 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).