From: Mark Brown <broonie@kernel.org>
To: Mario Limonciello <mario_limonciello@dell.com>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
"robert.moore@intel.com" <robert.moore@intel.com>,
"lv.zheng@intel.com" <lv.zheng@intel.com>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"han.lu@intel.com" <han.lu@intel.com>,
"yang.jie@intel.com" <yang.jie@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Matthew Garrett <mjg59@coreos.com>,
"liam.r.girdwood@intel.com" <liam.r.girdwood@intel.com>
Subject: Re: commit b1ef29725865 (ACPI _REV=2) causes sound regression on Dell XPS 13 [Was: Discussion around quirking the _REV behavior for the XPS 13 (2015) until 4.2]
Date: Tue, 12 May 2015 17:18:49 +0100 [thread overview]
Message-ID: <20150512161849.GD3066@sirena.org.uk> (raw)
In-Reply-To: <55521BA0.3030606@dell.com>
[-- Attachment #1: Type: text/plain, Size: 2330 bytes --]
On Tue, May 12, 2015 at 10:26:24AM -0500, Mario Limonciello wrote:
> On 05/12/2015 05:12 AM, Mark Brown wrote:
> >On Mon, May 11, 2015 at 08:26:58PM +0200, Dominik Brodowski wrote:
Please fix your mail client to word wrap within paragraphs and leave
blank lines between paragraphs. Your current mail client is doing
neither which makes your mails hard to read.
> >Also CCing Matthew who came up with the original version of the version
> >change and Liam who is one of Intel's audio experts.
> >>According to an off-list discussion, the sound breakage (and not just some
> >>jack detection issue) seems to be caused due to alsa-lib being too old.
> >Right, it needs the userspace configuration files installing.
> Is it just configuration files? With 4.1-rc3 I've not been able to
> get sound working mucking with any mixers.
You need PulseAudio 6.0 but otherwise yes, it works for me.
> >>The matter is further complicated by the issue that the driver
> >>asks for some firmware blob intel/IntcPP01.bin which (at least) I
> >>cannot find anywhere.
> >As previously advised that firmware is optional.
> The errors in dmesg make it seem like that was related to the firmware
> missing, but that is a red herring it sounds like.
Yes, it is.
> >Does this also affect other behaviour of the system? I'd be pretty
> >unhappy if it introduce power regressions for example, I mostly don't use
> >audio on my laptops but I care a lot about how long it'll run
> >disconnected. It *is* quite a new laptop and my experience installing
> >was very much that it was in bringup (though quite a bit of this was
> >userspace).
> I just tried it with 4.1-rc3 from Ubuntu's mainline PPA and an Ubuntu
> 15.04 userspace. It does affect the behavior of the system. See
> all the PCM errors in dmesg:
That wasn't my question. I'm asking what else the firmware is changing
based on detecting Linux, we don't want to just move onto a different
set of bugs somewhere else.
> https://bugzilla.kernel.org/attachment.cgi?id=176511
> At least with BIOS A03 (latest), Ubuntu 15.04 (3.19ish and modern
> userspace) or with 4.0 and recent userspace the experience shouldn't
> be bringup.
I'm not seeing any of the hw_params() issues with v4.1 - are you perhaps
using an old linux-firmware? I don't know how up to date Ubuntu is
there.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-05-12 16:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55401602.5050907@dell.com>
[not found] ` <55480021.1090402@dell.com>
2015-05-11 18:26 ` commit b1ef29725865 (ACPI _REV=2) causes sound regression on Dell XPS 13 [Was: Discussion around quirking the _REV behavior for the XPS 13 (2015) until 4.2] Dominik Brodowski
2015-05-11 19:01 ` Mario Limonciello
2015-05-12 7:27 ` Jie, Yang
2015-05-12 10:12 ` Mark Brown
2015-05-12 15:26 ` Mario Limonciello
2015-05-12 16:18 ` Mark Brown [this message]
2015-05-12 16:45 ` Mario Limonciello
2015-05-12 17:35 ` Mark Brown
2015-05-13 2:14 ` Jie, Yang
2015-05-13 21:32 ` Mario Limonciello
2015-05-12 17:21 ` Matthew Garrett
2015-05-12 17:29 ` Mario Limonciello
2015-05-12 17:40 ` Mark Brown
2015-05-12 17:43 ` Matthew Garrett
2015-05-12 17:49 ` Mario Limonciello
2015-05-12 23:38 ` Rafael J. Wysocki
2015-05-13 6:36 ` Dominik Brodowski
2015-05-13 13:44 ` Rafael J. Wysocki
2015-05-12 17:32 ` Mark Brown
2015-05-12 17:13 ` Dominik Brodowski
2015-05-12 17:30 ` Mark Brown
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=20150512161849.GD3066@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=han.lu@intel.com \
--cc=liam.r.girdwood@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=lv.zheng@intel.com \
--cc=mario_limonciello@dell.com \
--cc=mjg59@coreos.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--cc=yang.jie@intel.com \
/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