[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120201175651.GA3300@elliptictech.com>
Date: Wed, 1 Feb 2012 12:56:51 -0500
From: Nick Bowler <nbowler@...iptictech.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Wu Fengguang <fengguang.wu@...el.com>,
Keith Packard <keithp@...thp.com>
Subject: Re: Linux 3.3-rc2
On 2012-01-31 13:59 -0800, Linus Torvalds wrote:
> Ok, so for no real reason at all - except me being disorganized and
> just not thinking about it - rc2 is several days delayed. It's closer
> to two weeks rather than the standard one week I try to have between
> rc's.
[...]
> Go forth and test.
So, the HDMI log spam I reported against 3.2-rc1 in this thread:
http://permalink.gmane.org/gmane.linux.kernel/1212638
is actually slightly worse now (see below), despite the fact that it was
eliminated by the patch I tested. Looking at the git log, I see a patch
similar to the one sent to me was merged as part of a larger series:
3a9627f4fbb0 ("drm/i915: dont trigger hotplug events on unchanged ELD")
and indeed, by building the tree after checking out that specific commit
there is no spam. 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
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists