Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, subhransu.s.prusty@intel.com,
	lgirdwood@gmail.com
Subject: Re: [PATCH v4 2/7] ASoC: Intel: mrfld - Add DSP load and management
Date: Mon, 20 Oct 2014 11:11:49 +0530	[thread overview]
Message-ID: <20141020054149.GC28745@intel.com> (raw)
In-Reply-To: <s5hy4seucfk.wl-tiwai@suse.de>

On Fri, Oct 17, 2014 at 02:07:43PM +0200, Takashi Iwai wrote:
> At Fri, 17 Oct 2014 14:01:47 +0200,
> Mark Brown wrote:
> > 
> > On Fri, Oct 17, 2014 at 12:04:56PM +0200, Takashi Iwai wrote:
> > > Vinod Koul wrote:
> > 
> > > > I will work on moving memcpy32_toio to core and move users as well :)

And I did prepare RFC for that and had to trash it :(

Turns out we already have an API for this in kernel.

While adding the new header, though it should be io.h, stumbled upon not
much used __iowrite32_copy() which seems to be the API I need.

I am testing it as we speak, will send conversion patch today.

-- 
~Vinod

> > 
> > > We can move them into sound/core/memory.c.  They are pretty small and
> > > useful.
> > 
> > It's not really anything to do with sound though, the other users are
> > MTD devices at the minute.
> 
> Yeah, we can move up again, then :)
> 
> I think it's even not bad to have it as a static inline function.
> 
> 
> Takashi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

-- 

  reply	other threads:[~2014-10-20  6:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 14:30 [PATCH v4 0/7] ASoC: Intel: sst - add the merrifield IPC driver Vinod Koul
2014-10-16 14:30 ` [PATCH v4 1/7] ASoC: Intel: mrfld - add the dsp sst driver Vinod Koul
2014-10-17  9:11   ` Mark Brown
2014-10-16 14:30 ` [PATCH v4 2/7] ASoC: Intel: mrfld - Add DSP load and management Vinod Koul
2014-10-17  9:44   ` Mark Brown
2014-10-17  9:18     ` Vinod Koul
2014-10-17 10:04       ` Takashi Iwai
2014-10-17 12:01         ` Mark Brown
2014-10-17 12:07           ` Takashi Iwai
2014-10-20  5:41             ` Vinod Koul [this message]
2014-10-20 15:29               ` Mark Brown
2014-10-20 16:07                 ` Vinod Koul
2014-10-16 14:30 ` [PATCH v4 3/7] ASoC: Intel: sst - add pcm ops handling Vinod Koul
2014-10-17 12:07   ` Mark Brown
2014-10-17 11:35     ` Vinod Koul
2014-10-16 14:30 ` [PATCH v4 4/7] ASoC: Intel: sst: Add IPC handling Vinod Koul
2014-10-17 12:09   ` Mark Brown
2014-10-17 11:55     ` Vinod Koul
2014-10-17 13:53       ` Mark Brown
2014-10-20  5:18         ` Vinod Koul
2014-10-16 14:30 ` [PATCH v4 5/7] ASoC: Intel: sst: add stream operations Vinod Koul
2014-10-16 14:30 ` [PATCH v4 6/7] ASoC: Intel: sst: Add some helper functions Vinod Koul
2014-10-16 14:30 ` [PATCH v4 7/7] ASoC: Intel: sst: Add makefile and kconfig changes Vinod Koul
2014-10-17 12:15 ` [PATCH v4 0/7] ASoC: Intel: sst - add the merrifield IPC driver Mark Brown
2014-10-17 11:56   ` Vinod Koul

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=20141020054149.GC28745@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=subhransu.s.prusty@intel.com \
    --cc=tiwai@suse.de \
    /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