From: Takashi Iwai <tiwai@suse.de>
To: Ian W MORRISON <ianwmorrison@gmail.com>
Cc: alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: HDMI LPE audio on Intel Compute Stick 2nd Gen (CHT)
Date: Sun, 22 Oct 2017 15:20:13 +0200 [thread overview]
Message-ID: <s5hzi8js4j6.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAFXWsS9i0f7vpdiCBtxkzOpQ_aC9C2w0vJ6qoTr__1UzDugzGw@mail.gmail.com>
On Sun, 22 Oct 2017 15:00:12 +0200,
Ian W MORRISON wrote:
>
> On 21 October 2017 at 03:53, Takashi Iwai <tiwai@suse.de> wrote:
>
> > On Fri, 20 Oct 2017 17:54:45 +0200,
> > Pierre-Louis Bossart wrote:
> > >
> > > 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.
> >
> > Right, it's a new feature that was recently added, for supporting
> > multiple HDMI/DPs. The latest PA should be able to check the jack
> > detection of each port, so that it can switch to the actually
> > connected one.
> >
> >
> > Takashi
> >
>
> Thanks for the explanation. The PA package for Ubuntu is a bit behind (v8
> for 16.04 LST and v10 for latest 17.10) so it will be easier for users just
> to edit /etc/pulse/default.pa in the interim. But is there a way to stop
> the multiple and repeating "Audio Port: ASoC: no backend DAIs enabled for
> Audio Port" messages in dmesg from occurring without modifying the distro's
> kernel?
The DAI backend has nothing to do with HDMI LPE audio. It's from ASoC
Intel SST driver. You need to set up the routing either via UCM or
manually.
Takashi
next prev parent reply other threads:[~2017-10-22 13:20 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
2017-10-20 16:53 ` Takashi Iwai
2017-10-22 13:00 ` Ian W MORRISON
2017-10-22 13:20 ` Takashi Iwai [this message]
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=s5hzi8js4j6.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=ianwmorrison@gmail.com \
--cc=pierre-louis.bossart@linux.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).