From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 0/7] ASoC: Intel: Add support for Baytrail SST DSP
Date: Mon, 24 Feb 2014 20:16:01 +0000 [thread overview]
Message-ID: <1393272961.2323.75.camel@loki> (raw)
In-Reply-To: <1393255622-31365-1-git-send-email-jarkko.nikula@linux.intel.com>
On Mon, 2014-02-24 at 17:26 +0200, Jarkko Nikula wrote:
> This set adds support for Baytrail SST DSP with RT5640 based machine
> driver. Design is quite similar and is actually inherited from Intel
> Haswell SST DSP drivers that were posted recently. Reason for another
> implementation is that there are more differences than similarities
> between Haswell and Baytrail.
>
> First difference comes from the SHIM registers that are 32-bit on
> Haswell and 64-bit on Baytrail. Also memory map and message mailbox is
> different. Second difference is message passing and message headers
> between host and SST DSP. For instance the DSP notifies the host using
> different SHIM registers and bits than on Haswell.
>
> Biggest difference comes from the DSP firmware. It has different IPC
> messages, stream setup and how DMA pointer is tracked. Currently
> firmware has less features than Haswell DSP firmware and it doesn't
> support compress offload and volume controls support.
>
> The RT5640 based machine driver is for our customer reference boards
> but at quick test it appears to work on Asus T100 too. Note currently
> the SST is the I2S master on this machine driver and codec is set to
> use I2C BCLK as it's input clock.
>
> Jarkko Nikula (7):
> ASoC: Intel: Add Baytrail SST ID and Baytrail specific register bits
> ASoC: Intel: Add Intel Baytrail SST DSP support
> ASoC: Intel: Add Intel Baytrail SST DSP IPC support
> ASoC: Intel: Add Intel Baytrail SST PCM platform driver
> ASoC: Intel: Add machine driver for Baytrail SST with RT5640 codec
> ASoC: Intel: Add Baytrail SST and byt-rt5640 machine driver probing
> ASoC: Intel: Add build support for Baytrail SST
>
All
Acked-by: Liam Girdwood <liam.r.girdwood@intel.com>
next prev parent reply other threads:[~2014-02-24 20:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 15:26 [PATCH 0/7] ASoC: Intel: Add support for Baytrail SST DSP Jarkko Nikula
2014-02-24 15:26 ` [PATCH 1/7] ASoC: Intel: Add Baytrail SST ID and Baytrail specific register bits Jarkko Nikula
2014-02-24 15:26 ` [PATCH 2/7] ASoC: Intel: Add Intel Baytrail SST DSP support Jarkko Nikula
2014-02-24 15:26 ` [PATCH 3/7] ASoC: Intel: Add Intel Baytrail SST DSP IPC support Jarkko Nikula
2014-02-24 15:26 ` [PATCH 4/7] ASoC: Intel: Add Intel Baytrail SST PCM platform driver Jarkko Nikula
2014-02-24 15:27 ` [PATCH 5/7] ASoC: Intel: Add machine driver for Baytrail SST with RT5640 codec Jarkko Nikula
2014-02-25 4:42 ` Mark Brown
2014-02-24 15:27 ` [PATCH 6/7] ASoC: Intel: Add Baytrail SST and byt-rt5640 machine driver probing Jarkko Nikula
2014-02-24 15:27 ` [PATCH 7/7] ASoC: Intel: Add build support for Baytrail SST Jarkko Nikula
2014-02-24 20:16 ` Liam Girdwood [this message]
2014-02-25 4:44 ` [PATCH 0/7] ASoC: Intel: Add support for Baytrail SST DSP 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=1393272961.2323.75.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=lgirdwood@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox