From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Ian W MORRISON <ianwmorrison@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: HDMI LPE audio on Intel Compute Stick 2nd Gen (CHT)
Date: Fri, 20 Oct 2017 10:54:45 -0500 [thread overview]
Message-ID: <11e337a4-0656-50d3-3c16-56cc437a32c7@linux.intel.com> (raw)
In-Reply-To: <CAFXWsS8THagHnx9BPurw4+3a+xH6DP653MjwjTSkYhU3zLmZHQ@mail.gmail.com>
On 10/20/17 8:45 AM, Ian W MORRISON wrote:
>> I've just noticed that non of the kernels from v4.13 and up run on my
>>> Intel Compute Stick (2nd gen Cherry Trail STK1AW32SC) unit and have
>>> HDMI LPE audio working.
>>>
>>
>> I have not tested HDMI in a while but I am not aware of any issues either.
>> There were some patches recently to fix PulseAudio problems and I suppose
>> some folks used a recent kernel?
>>
>>
> It actually happened since v4.12 as now I get three HDMI LPE Audio devices
> show up with 'aplay -l' rather than just one. Only 'device 2' works so if I
> change the sink to use that device I get sound. So basically it can be
> fixed in userland however I'm seeing others with different devices also
> complaining how audio is broken and I think it is something that many users
> don't know to fix. Is it worth looking into further or just leaving it as a
> known issue?
I don't think it's a bug, it's a feature...
The jack information tells you which device is connected/active, so
userspace has all the data needed to select the right routing.
next prev parent reply other threads:[~2017-10-20 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 10:50 HDMI LPE audio on Intel Compute Stick 2nd Gen (CHT) Ian W MORRISON
2017-10-17 13:55 ` Pierre-Louis Bossart
2017-10-20 13:45 ` Ian W MORRISON
2017-10-20 15:54 ` Pierre-Louis Bossart [this message]
2017-10-20 16:53 ` Takashi Iwai
2017-10-22 13:00 ` Ian W MORRISON
2017-10-22 13:20 ` Takashi Iwai
2017-10-22 13:25 ` Pierre-Louis Bossart
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=11e337a4-0656-50d3-3c16-56cc437a32c7@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=ianwmorrison@gmail.com \
--cc=tiwai@suse.de \
/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).