From: Mark Brown <broonie@kernel.org>
To: Mario Limonciello <mario_limonciello@dell.com>
Cc: Matthew Garrett <matthew.garrett@coreos.com>,
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 18:40:36 +0100 [thread overview]
Message-ID: <20150512174036.GI3066@sirena.org.uk> (raw)
In-Reply-To: <5552388C.9000500@dell.com>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
On Tue, May 12, 2015 at 12:29:48PM -0500, Mario Limonciello wrote:
> On 05/12/2015 12:21 PM, Matthew Garrett wrote:
> >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?
If we're waiting for distros to have new enough userspace we're looking
at waiting several years at least, especially when you start looking at
distros like Debian (which two of the users in this thread are, though
I'm not on stable).
> That would enforce that no other machines can use _REV value of 5 to detect
> Linux without breaking the 9343.
What Matthew suggested was making the quirk a compile time option.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-05-12 17:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 23:21 Discussion around quirking the _REV behavior for the XPS 13 (2015) until 4.2 Mario Limonciello
2015-05-04 23:26 ` Mario Limonciello
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
2015-05-12 17:40 ` Mark Brown [this message]
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=20150512174036.GI3066@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=matthew.garrett@coreos.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;
as well as URLs for NNTP newsgroup(s).