From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Mario Limonciello <mario_limonciello@dell.com>
Cc: Matt Fleming <matt@codeblueprint.co.uk>,
Jason Ekstrand <jason@jlekstrand.net>,
LKML <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Bard Liao <bardliao@realtek.com>,
linux-acpi@vger.kernel.org, lenb@kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: Re: [PATCH] ACPI: Adjust the return value of _REV on x86
Date: Tue, 24 Mar 2015 09:17:37 +0000 [thread overview]
Message-ID: <1427188657.7155.11.camel@loki> (raw)
In-Reply-To: <5510FB37.6030808@dell.com>
On Tue, 2015-03-24 at 00:50 -0500, Mario Limonciello wrote:
> I believe a majority of the kernel work is complete, but from some off
> kernel mailing list discussions I understand that pulseaudio doesn't
> understand the control interface that gets used for I2S for jack
> detection.
There is some work in progress here to standardise the jack kcontrols
between HDA, ASoC and other ALSA drivers. I would expect this to be
upstream in the next week or two.
> UCM can't be used for it.
UCM configs and jack support for this DSP and codec combination have now
been upstreamed :)
> This leads to a really confusing mixer design that needs a variety of
> toggles manually changed when headphones or a headset get plugged in.
Generic patches to support UCM jack switching are now upstream in
pulseaudio too.
> There have also been some stability problem with audio reported
> after a few days usage.
Can you send these to me privately.
Thanks
Liam
next prev parent reply other threads:[~2015-03-24 9:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 8:50 [PATCH] ACPI: Adjust the return value of _REV on x86 Matthew Garrett
2015-03-14 19:58 ` Jason Ekstrand
2015-03-16 23:21 ` Jason Ekstrand
2015-03-23 12:04 ` Matt Fleming
2015-03-24 5:50 ` Mario Limonciello
2015-03-24 9:17 ` Liam Girdwood [this message]
2015-03-24 14:41 ` Mario Limonciello
2015-03-24 15:24 ` Matt Fleming
2015-03-24 17:22 ` Mario Limonciello
2015-03-24 18:01 ` Matthew Garrett
2015-03-24 19:53 ` Mario Limonciello
2015-03-24 20:00 ` Matthew Garrett
2015-03-24 20:02 ` Rafael J. Wysocki
2015-03-24 20:21 ` Mario Limonciello
2015-03-16 20:34 ` Al Stone
2015-03-16 21:01 ` Matthew Garrett
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=1427188657.7155.11.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=bardliao@realtek.com \
--cc=jason@jlekstrand.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=matt@codeblueprint.co.uk \
--cc=mjg59@srcf.ucam.org \
--cc=rjw@rjwysocki.net \
/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).