public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jayakumar alsa <jayakumar.alsa@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: perex@suse.cz, mj@ucw.cz, alsa-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [Alsa-devel] [RFC 2.6.13.1 1/1] CS5535 AUDIO ALSA driver
Date: Thu, 15 Sep 2005 20:32:28 +0800	[thread overview]
Message-ID: <47f5dce3050915053266745a8f@mail.gmail.com> (raw)
In-Reply-To: <s5hk6hi8wnr.wl%tiwai@suse.de>

On 9/15/05, Takashi Iwai <tiwai@suse.de> wrote:
> Just small glitches I found below:

Much appreciated. Thanks for reviewing. :-)

> You can put this header filer into sound/pci/cs5535, so that it won't
> be exported.  Then you don't need __KERNEL__ check, too.

Will do.

> > +     u16 eot:1;
> > +} cs5535audio_dma_desc_t;
> 
> The bitfield isn't portable to use to comminucate with the hardware.
> Better to use u16 and normal bit operations.

I think 5535 is x86-32 specific, but you are right, I shouldn't use
bit fields. I'll convert over to masks.

> The loop with do_delay() should be replaced with more portable ones
> like msleep().

Will do.

> 
> > +{
> > +     unsigned long regdata=0;
> 
> Unnecessary initialization :)

Good catch.

> > +     cs5535au = kcalloc(1, sizeof(*cs5535au), GFP_KERNEL);
> 
> Let's use the new kzalloc().

Will do.

> > +     spin_lock(&cs5535au->reg_lock);
> > +     dma->ops->disable_dma(cs5535au);
> > +     dma->ops->setup_prd(cs5535au, jmpprd_addr);
> > +     spin_unlock(&cs5535au->reg_lock);
> 
> You need spin_lock_irq() here, instead.
> 

Got it. Will do.

Thanks,
jk

      reply	other threads:[~2005-09-15 12:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15  9:04 [RFC 2.6.13.1 1/1] CS5535 AUDIO ALSA driver jayakumar.alsa
2005-09-15  9:33 ` David Vrabel
2005-09-15 10:15 ` [Alsa-devel] " Takashi Iwai
2005-09-15 12:32   ` jayakumar alsa [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=47f5dce3050915053266745a8f@mail.gmail.com \
    --to=jayakumar.alsa@gmail.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    --cc=perex@suse.cz \
    --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