From: Matthew Garrett <matthew.garrett@coreos.com>
To: Mario Limonciello <mario_limonciello@dell.com>
Cc: Mark Brown <broonie@kernel.org>,
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 10:43:33 -0700 [thread overview]
Message-ID: <CAPeXnHss+k4xqYDZsDycKEAtLGMBbsnsMiHsZ_voigbPoq3vUw@mail.gmail.com> (raw)
In-Reply-To: <5552388C.9000500@dell.com>
On Tue, May 12, 2015 at 10:29 AM, Mario Limonciello
<mario_limonciello@dell.com> wrote:
> Just to be clear, from the Dell side only the XPS 13 9343 has this _REV
> behavior.
The Inspiron 7437 queries _REV and uses it to modify its EC behaviour,
and apparently breaks on Linux without that.
> 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.
DMI quirking is fine, but it has to be behind a config option. We're
going to have to carry the quirk for several years because we have to
support old userspace for an arbitrarily long time, and if there's no
config option then Linux will be stuck in HDA mode for that entire
time.
--
Matthew Garrett | matthew.garrett@coreos.com
next prev parent reply other threads:[~2015-05-12 17:43 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
2015-05-12 17:43 ` Matthew Garrett [this message]
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=CAPeXnHss+k4xqYDZsDycKEAtLGMBbsnsMiHsZ_voigbPoq3vUw@mail.gmail.com \
--to=matthew.garrett@coreos.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=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;
as well as URLs for NNTP newsgroup(s).