From: Nick Bowler <nbowler@elliptictech.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Wu Fengguang <fengguang.wu@intel.com>,
Keith Packard <keithp@keithp.com>
Subject: Re: Linux 3.3-rc2
Date: Wed, 1 Feb 2012 12:56:51 -0500 [thread overview]
Message-ID: <20120201175651.GA3300@elliptictech.com> (raw)
In-Reply-To: <CA+55aFye5iedspjus4YLi+r77Xq74bCq+MqU0HrTmDC5Dveivg@mail.gmail.com>
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/)
next prev parent reply other threads:[~2012-02-01 17:57 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 [this message]
2012-02-02 3:35 ` Wu Fengguang
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=20120201175651.GA3300@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=fengguang.wu@intel.com \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.