From: David Henningsson <david.henningsson@canonical.com>
To: alsa-devel@alsa-project.org, tiwai@suse.de
Cc: fengguang.wu@intel.com, pierre-louis.bossart@linux.intel.com,
David Henningsson <david.henningsson@canonical.com>
Subject: [PATCH v2 0/4] Make HDMI ELD usable for hotplug
Date: Tue, 19 Feb 2013 09:47:33 +0100 [thread overview]
Message-ID: <1361263657-15888-1-git-send-email-david.henningsson@canonical.com> (raw)
New day, new patches. This time there is a proper lock around
access to the ELD buffer. I hope this satisfies the previous
comments.
I've also tested the patches together with some PulseAudio patches
I'm writing and the notification works just fine. The ELD data
shows up 300 ms after hotplug, so it's likely the first repoll
giving me new ELD data).
David Henningsson (4):
ALSA: hda - hdmi: ELD shouldn't be valid after unplug
ALSA: hda - hdmi: Do not expose eld data when eld is invalid
ALSA: hda - hdmi: protect access to ELD buffer
ALSA: hda - hdmi: Notify userspace when ELD control changes
sound/pci/hda/hda_eld.c | 12 ++++++--
sound/pci/hda/hda_local.h | 3 ++
sound/pci/hda/patch_hdmi.c | 67 +++++++++++++++++++++++++++++++++++---------
3 files changed, 66 insertions(+), 16 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-02-19 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 8:47 David Henningsson [this message]
2013-02-19 8:47 ` [PATCH v2 1/4] ALSA: hda - hdmi: ELD shouldn't be valid after unplug David Henningsson
2013-02-19 8:47 ` [PATCH v2 2/4] ALSA: hda - hdmi: Do not expose eld data when eld is invalid David Henningsson
2013-02-19 8:47 ` [PATCH v2 3/4] ALSA: hda - hdmi: protect access to ELD buffer David Henningsson
2013-02-19 9:15 ` Takashi Iwai
2013-02-19 9:45 ` David Henningsson
2013-02-19 8:47 ` [PATCH v2 4/4] ALSA: hda - hdmi: Notify userspace when ELD control changes David Henningsson
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=1361263657-15888-1-git-send-email-david.henningsson@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=fengguang.wu@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
/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).