alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: tiwai@suse.de, patches.audio@intel.com,
	alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH v2 0/8] ASoC: Intel: refactor common SST IPC handling
Date: Thu, 21 May 2015 22:14:51 +0100	[thread overview]
Message-ID: <1432242891.6818.26.camel@loki> (raw)
In-Reply-To: <1432027840-18711-1-git-send-email-vinod.koul@intel.com>

On Tue, 2015-05-19 at 15:00 +0530, Vinod Koul wrote:
> This series refactors the common SST IPC code to remove some hardcoded
> assumption which are no longer valid for future platforms like Skylake,
> These are made configurable and right configuration applied for respective
> drivers. The changes are mailbox sizes and dsp busy checks.
> 
> changes in v2:
>  - fix the mem allocation for IPC mailbox
> 
> Subhransu S. Prusty (8):
>   ASoC: Intel: Create an ops to check for DSP busy
>   ASoC: Intel: Move the busy check to ops for Baytrail
>   ASoC: Intel: Move the busy check to ops for HSW
>   ASoC: Intel: Remove the direct register reference from common ipc
>   ASoC: Intel: Allow to configure max size for mailbox data
>   ASoC: Intel: Initialize max mailbox size for baytrail
>   ASoC: Intel: Initialize max mailbox size for haswell
>   ASoC: Intel: Allocate for the mailbox with max size
> 
>  sound/soc/intel/baytrail/sst-baytrail-ipc.c | 11 ++++++++++
>  sound/soc/intel/common/sst-ipc.c            | 34 +++++++++++++++++++++++++----
>  sound/soc/intel/common/sst-ipc.h            |  7 ++++--
>  sound/soc/intel/haswell/sst-haswell-ipc.c   | 12 ++++++++++
>  4 files changed, 58 insertions(+), 6 deletions(-)
> 

Acked-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>

      parent reply	other threads:[~2015-05-21 21:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19  9:30 [PATCH v2 0/8] ASoC: Intel: refactor common SST IPC handling Vinod Koul
2015-05-19  9:30 ` [PATCH v2 1/8] ASoC: Intel: Create an ops to check for DSP busy Vinod Koul
2015-05-19  9:30 ` [PATCH v2 2/8] ASoC: Intel: Move the busy check to ops for Baytrail Vinod Koul
2015-05-19  9:30 ` [PATCH v2 3/8] ASoC: Intel: Move the busy check to ops for HSW Vinod Koul
2015-05-19  9:30 ` [PATCH v2 4/8] ASoC: Intel: Remove the direct register reference from common ipc Vinod Koul
2015-05-19  9:30 ` [PATCH v2 5/8] ASoC: Intel: Allow to configure max size for mailbox data Vinod Koul
2015-05-19  9:30 ` [PATCH v2 6/8] ASoC: Intel: Initialize max mailbox size for baytrail Vinod Koul
2015-05-19  9:30 ` [PATCH v2 7/8] ASoC: Intel: Initialize max mailbox size for haswell Vinod Koul
2015-05-22 18:23   ` Mark Brown
2015-05-19  9:30 ` [PATCH v2 8/8] ASoC: Intel: Allocate for the mailbox with max size Vinod Koul
2015-05-19 10:42   ` Takashi Iwai
2015-05-19 11:07     ` Vinod Koul
2015-05-21 21:14 ` Liam Girdwood [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=1432242891.6818.26.camel@loki \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=patches.audio@intel.com \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@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).