From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Nicola Lunghi <nicola.lunghi@emutex.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ASoC Sound Driver I2S over LPE, Intel Baytrail SoC. MinnowBoard Max
Date: Mon, 2 Oct 2017 13:22:05 -0500 [thread overview]
Message-ID: <d2a80c3a-9624-4c71-63ef-d60d1141c2cf@linux.intel.com> (raw)
In-Reply-To: <fff69ce9-69f5-9e44-820a-c6c29ca2898f@emutex.com>
On 10/02/2017 11:14 AM, Nicola Lunghi wrote:
> Dear Pierre Louis
>
> We are having problems enabling I2S output with the UP board.
>
> We have currently two boards one based on Cherry Trail Platform and
> one on the Apollo Lake.
>
> We want for now enable only I2S output without codec on kernel 4.9/4.10.
>
> Can you give us some hint about the required ACPI asl code to add in
> the ACPI and if there's something else required in the Linux kernel?
in theory all you need to do is enable the NOCODEC option, make sure
that all other machine drivers are removed from the build and only add
in ASL the bare minimum to make the audio DSP enumerate (as in make sure
that all codecs are removed from the BIOS as well).
On Minnowboard MAX, I used this code
https://github.com/plbossart/MinnowBoardMaxFirmware/blob/master/AudioSsdtUpdate/LPEX.asl
You would need to compare with the existing BIOS since there might be
some differences with CHT.
I have not done this work on APL and it's likely different since it's
based on PCI.
prev parent reply other threads:[~2017-10-02 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 1:31 ASoC Sound Driver I2S over LPE, Intel Baytrail SoC. MinnowBoard Max Michael Pogrebinsky
2015-11-10 18:53 ` Pierre-Louis Bossart
2015-11-10 19:59 ` Michael Pogrebinsky
2015-11-11 2:18 ` Michael Pogrebinsky
2015-11-11 15:50 ` Pierre-Louis Bossart
2015-11-11 17:53 ` Michael Pogrebinsky
2017-10-02 16:14 ` Nicola Lunghi
2017-10-02 18:22 ` 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=d2a80c3a-9624-4c71-63ef-d60d1141c2cf@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=nicola.lunghi@emutex.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).