From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Freaky <freaky2000@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: No audio on Lenovo Miix 320
Date: Tue, 27 Mar 2018 10:48:14 -0500 [thread overview]
Message-ID: <59eca166-888f-d211-8d35-d760786fbf8f@linux.intel.com> (raw)
In-Reply-To: <CAEw6ZytwPFpHskzAUJBtF9_MupiJ2obOx6n8sJ8Oo8gZZ4A1Mg@mail.gmail.com>
On 3/27/18 5:56 AM, Freaky wrote:
> Hi there,
>
> we're having some issues getting the audio working on a Lenovo Miix 320.
>
> On some forums they say it should work after
> blacklisting snd_hdmi_lpe_audio. Have blacklisted this, and there's one
> audio card less now, but still no go unfortunately.
>
> Currently running with 4.15.10 from Fedora 27.
>
> It logs a lot of: "Audio Port: ASoC: no backend DAIs enabled for Audio
> Port" lines.
You need a UCM file or to set the mixers. This is a user-space
configuration issue, the kernel is doing what it's supposed to do.
>
> Any ideas on how to troubleshoot this? Saw similar problems in
> https://bugzilla.kernel.org/show_bug.cgi?id=96691 but this seems to be for
> another codec/DAI. Also, their system seems to be a Baytrail Atom, this is
> a Cherrytrail. Not sure if any of the patches are applicable.
the UCM or mixer settings is not related to the SOC but to the card name
and codec capabilities. We share the same settings between Baytrail and
Cherrytrail.
>
> dmesg is attached.
>
> I can patch, build and test kernels. Coding is another story however :).
>
> Any help is appreciated.
>
> Kind regards,
>
>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
prev parent reply other threads:[~2018-03-27 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 10:56 No audio on Lenovo Miix 320 Freaky
2018-03-27 15:48 ` Pierre-Louis Bossart [this message]
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=59eca166-888f-d211-8d35-d760786fbf8f@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=freaky2000@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.