Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org, lgirdwood@gmail.com
Subject: Re: [PATCH 1/5] ASoC: intel: use __iowrite32_copy for 32	bit copy
Date: Mon, 20 Oct 2014 18:44:52 +0530	[thread overview]
Message-ID: <20141020131452.GG28745@intel.com> (raw)
In-Reply-To: <s5h1tq3m12a.wl-tiwai@suse.de>

On Mon, Oct 20, 2014 at 01:29:33PM +0200, Takashi Iwai wrote:
> At Mon, 20 Oct 2014 15:29:04 +0530,
> Vinod Koul wrote:
> > 
> > The driver was using own method to do 32bit copy, turns out we have a kernel
> > API so use that instead
> > 
> > Tested-by: Subhransu S. Prusty <subhransu.s.prusty@intel.com>
> > Signed-off-by: Vinod Koul <vinod.koul@intel.com>
> > ---
> >  sound/soc/intel/sst/sst_loader.c |    9 +++------
> >  1 files changed, 3 insertions(+), 6 deletions(-)
> > 
> > diff --git a/sound/soc/intel/sst/sst_loader.c b/sound/soc/intel/sst/sst_loader.c
> > index b6d27c1..40e501b 100644
> > --- a/sound/soc/intel/sst/sst_loader.c
> > +++ b/sound/soc/intel/sst/sst_loader.c
> > @@ -41,12 +41,9 @@
> >  
> >  static void memcpy32_toio(void __iomem *dst, const void *src, int count)
> >  {
> > -	int i;
> > -	const u32 *src_32 = src;
> > -	u32 *dst_32 = dst;
> > -
> > -	for (i = 0; i < count/sizeof(u32); i++)
> > -		writel(*src_32++, dst_32++);
> > +	/* __iowrite32_copy uses 32-bit count values so dev by 4 for right
> > +	 * count in words */
> 
> s/dev/div/
> 
> Also, it's worth to make it inline, although the compiler would do it
> automatically in most cases like this.
Yes it did, although it would make sense to do so here as well

-- 
~Vinod

> 
> 
> Takashi
> 
> > +	__iowrite32_copy(dst, src, count/4);
> >  }
> >  
> >  /**
> > -- 
> > 1.7.0.4
> > 
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> > 

-- 

  reply	other threads:[~2014-10-20 13:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20  9:59 [PATCH 0/5] ASoC: intel: fix to sst driver series Vinod Koul
2014-10-20  9:59 ` [PATCH 1/5] ASoC: intel: use __iowrite32_copy for 32 bit copy Vinod Koul
2014-10-20 11:29   ` Takashi Iwai
2014-10-20 13:14     ` Vinod Koul [this message]
2014-10-20  9:59 ` [PATCH 2/5] ASoC: intel: log an error on double free Vinod Koul
2014-10-20 11:30   ` Takashi Iwai
2014-10-20 13:14     ` Vinod Koul
2014-10-20  9:59 ` [PATCH 3/5] ASoC: intel: fix the kernldoc comment Vinod Koul
2014-10-20  9:59 ` [PATCH 4/5] ASoC: intel: explain why block not found isn't error always Vinod Koul
2014-10-20  9:59 ` [PATCH 5/5] ASoC: intel: use __iowrite32_copy for 32 bit copy 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=20141020131452.GG28745@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.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