linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mario Limonciello <mario_limonciello@dell.com>
To: "Jie, Yang" <yang.jie@intel.com>, Mark Brown <broonie@kernel.org>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
	"Moore, Robert" <robert.moore@intel.com>,
	"Zheng, Lv" <lv.zheng@intel.com>,
	"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"Lu, Han" <han.lu@intel.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Matthew Garrett <mjg59@coreos.com>,
	"Girdwood, Liam R" <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: Wed, 13 May 2015 16:32:29 -0500	[thread overview]
Message-ID: <5553C2ED.2030406@dell.com> (raw)
In-Reply-To: <E7B1D079BA13FB44A978CC8F69C7D6A9055272E4@SHSMSX101.ccr.corp.intel.com>



On 05/12/2015 09:14 PM, Jie, Yang wrote:
>   
> Hi Mario, can you try disabling pulseaudio to see if anything change?
> Once I got one XPS 13 9343, I can debug on it, we have ordered it, but been
> told still need wait 4 more weeks for lacking of the LCD screen materials.
>
> ~Keyon
>
>

Keyon,

Yes, if I kill pulseaudio (and prevent it from starting back up), I am 
able to get audio by running:
speaker-test -c 2 -t wav -D plughw:broadwellrt286

I've tried to remove .config/pulse, but it's still not working at all 
when pulse launches up.

Thanks,

  reply	other threads:[~2015-05-13 21:32 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 [this message]
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=5553C2ED.2030406@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=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).