All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
	patches@opensource.wolfsonmicro.com,
	vinod.koul@linux.jf.intel.com, liam.r.girdwood@intel.com
Subject: Re: [PATCH v2] ASoC: soc-compress: Add support for not memory mapped	DSPs
Date: Wed, 30 Jan 2013 19:02:32 -0800	[thread overview]
Message-ID: <20130131030232.GB3143@intel.com> (raw)
In-Reply-To: <20130129185116.GA27083@opensource.wolfsonmicro.com>

On Tue, Jan 29, 2013 at 06:51:16PM +0000, Charles Keepax wrote:
> The ASoC compressed API did not implement the copy callback in its
> compressed ops which is required for DSPs that are not memory mapped.
> This patch adds a second set of compressed ops which does implement the
> copy callback and uses that when copy is defined in the platform
> compressed ops, ie. when the DSP is not memory mapped.
> 
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
> @@ -335,14 +352,23 @@ int soc_new_compress(struct snd_soc_pcm_runtime *rtd, int num)
>  		return -ENOMEM;
>  	}
>  
> -	compr->ops = &soc_compr_ops;
> +	compr->ops = kmemdup(&soc_compr_ops, sizeof(soc_compr_ops), GFP_KERNEL);
You forgot to free this memory when device is destoryed

--
~Vinod

  reply	other threads:[~2013-01-31  3:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25  9:00 [PATCH] ASoC: soc-compress: Add support for not memory mapped DSPs Charles Keepax
2013-01-28  4:04 ` Vinod Koul
2013-01-28  4:56   ` Mark Brown
2013-01-28  6:09     ` Vinod Koul
2013-01-28  6:44       ` Mark Brown
2013-01-28  9:34         ` Vinod Koul
2013-01-28 10:49           ` Charles Keepax
2013-01-29 18:51             ` [PATCH v2] " Charles Keepax
2013-01-31  3:02               ` Vinod Koul [this message]
2013-02-05 10:41                 ` [PATCH v3] " Charles Keepax
2013-02-05 11:54                   ` Vinod Koul
2013-02-05 13:56                   ` 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=20130131030232.GB3143@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=liam.r.girdwood@intel.com \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@linux.jf.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 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.