From: Mario Limonciello <mario_limonciello@dell.com>
To: Matthew Garrett <matthew.garrett@coreos.com>,
Mark Brown <broonie@kernel.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"robert.moore@intel.com" <robert.moore@intel.com>,
Dominik Brodowski <linux@dominikbrodowski.net>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Matthew Garrett <mjg59@coreos.com>,
"lv.zheng@intel.com" <lv.zheng@intel.com>,
"liam.r.girdwood@intel.com" <liam.r.girdwood@intel.com>,
"han.lu@intel.com" <han.lu@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 12:29:48 -0500 [thread overview]
Message-ID: <5552388C.9000500@dell.com> (raw)
In-Reply-To: <CAPeXnHtdU=9bMjHh8NSArYngxDC1wSp3ZDiN96e5gHB_LQjr5g@mail.gmail.com>
On 05/12/2015 12:21 PM, Matthew Garrett wrote:
> On Tue, May 12, 2015 at 9:18 AM, Mark Brown <broonie@kernel.org> wrote:
>> You need PulseAudio 6.0 but otherwise yes, it works for me.
> Since there's no way to get this working without using new userspace,
> we're basically stuck with having to support _REV 5. And since we're
> supposed to support old userspace basically forever, this isn't going
> to be something that we can just remove in a few months. But since the
> hardware is intended to be used in I2S mode, we don't want this quirk
> to be there forever. So we're basically left with adding
> CONFIG_ACPI_WORKAROUND_BROKEN_DELLS which enables the quirk, default
> it to Y and then let distributions set it to N when they've got
> sufficiently new userspace. Unless someone has a better plan?
Just to be clear, from the Dell side only the XPS 13 9343 has this _REV
behavior.
What's wrong with a DMI quirk until I2S is mature on the kernel side and
userspace is new enough in distros? Is it too early in boot for DMI
quirks? That would enforce that no other machines can use _REV value of
5 to detect Linux without breaking the 9343.
next prev parent reply other threads:[~2015-05-12 17:30 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
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 [this message]
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=5552388C.9000500@dell.com \
--to=mario_limonciello@dell.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.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=matthew.garrett@coreos.com \
--cc=mjg59@coreos.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@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