linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mario Limonciello <mario_limonciello@dell.com>
To: 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>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"broonie@kernel.org" <broonie@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>
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: Mon, 11 May 2015 14:01:11 -0500	[thread overview]
Message-ID: <5550FC77.5000401@dell.com> (raw)
In-Reply-To: <20150511182658.GA8516@isilmar-3.linta.de>

On 05/11/2015 01:26 PM, Dominik Brodowski wrote:
> Hi,
>
> (CC'ing sound experts)
>
> indeed, commit b1ef29725865 causes a severe regression -- actually, it
> causes sound to be totally unusuable on the Dell XPS 13 (2015) on
> Debian jessie, while it works fine in 4.0 / with b1ef29725865 reverted.
>
> 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.
> 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.
>
> Under the no-regression rule, this means that either b1ef29725865 needs
> to be reverted or we need to find another solution to this matter, such as
> an override. And I think it is needed for longer than just for 4.1, as it
> will continue to be cause regressions on quite recent userspace.
>
> Best,
> 	Dominik
>
>
> PS/OT: Probably I'm preaching to the choir, but @Mario: it's a pity the
> XPS (or some versions of it) with pre-installed Ubuntu actually ships
> with a Wifi adapter which seems to be unsupported by upstream Linux...
>
>
Dominik,

Yes I've noticed it's acting much worse for me too with 4.1-rc2 on Ubuntu 15.04 userspace (which is quite new indeed).  I really think the right solution is some sort of quirk against the XPS 13 on the _REV behavior until this is reasonably mature.

OT: Yes, this feedback has been taken to heart by the team.  We're working on adding more variants with alternate adapters.  :)

  reply	other threads:[~2015-05-11 19:01 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 [this message]
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
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=5550FC77.5000401@dell.com \
    --to=mario_limonciello@dell.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=han.lu@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=lv.zheng@intel.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).