Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Klaus Fetscher <K.Fetscher@t-online.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA Driver for ARM-Linux 2.6
Date: Mon, 16 Aug 2004 15:05:43 +0200	[thread overview]
Message-ID: <s5h4qn3b5co.wl@alsa2.suse.de> (raw)
In-Reply-To: <4120A964.8080402@fetron.de>

At Mon, 16 Aug 2004 14:32:36 +0200,
Klaus Fetscher wrote:
> 
> Hallo Takashi,
> 
> thanks for your answer.
> 
> >>we want to program an ALSA driver for a Codec which communicates over an 
> >>I2S interface with an ARM9 processor.
> >>I have read several messages regarding ALSA-Drivers, Linux 2.6 and ARM 
> >>and know I am a little bit confused.
> >>
> >>Is it possible to use ALSA with ARM or need we some patches for the ARM 
> >>CPU ?
> >>
> >>I have read, that the sa11xx-uda1341 driver is not a good starting point 
> >>for implementing a driver. Which is a better solution ?
> >>    
> >>
> >
> >  
> >
> Does the driver under sound/arm/sa11xx-uda1341.c in the current 2.6.7 
> kernel tree work with ALSA ?

Well, I'm not sure about this.  Someone told that it's broken.
I even didn't take a deep look yet.  But, as written above, it should
work if the driver doesn't use mmap.

> If yes, I will change this file for my requirements or do you have a 
> better idea ?

Depends.  If the board design is similar with sa11xx-uda1341, it's
an easier start point.  (I believe sa11xx-uda1341 driver can be more
generalized, though.)


> The CPU communicates with the Sound Chip over a I2S interface. Shall I 
> make a new subdirectory  /sound/i2s or /sound/i2c/i2s for the I2S stuff 
> or do you recommand another directory ?

Unless you need the "generic" i2s support over different
architectures, you should put the stuff locally in your driver code.

> 
> >In general, ALSA has a problem on architectures like ARM about cache
> >and mmap.  So far, the ALSA should work fine on ARM, too, if the
> >driver doesn't use mmap.
> >
> >Russell King has some patches to fix this issue, which I will merge
> >later on our tree.
> >
> >  
> >
> If I don't use mmap in the driver (actually, sa11xx-uda1341.c don't use 
> this function) I don't need this patches, correct ?

Yes (but again, I haven't tested ARM at all by myself).


Takashi


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

      parent reply	other threads:[~2004-08-16 13:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 20:11 ALSA Driver for ARM-Linux 2.6 Klaus Fetscher
2004-08-16 10:40 ` Takashi Iwai
     [not found]   ` <4120A964.8080402@fetron.de>
2004-08-16 13:05     ` Takashi Iwai [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=s5h4qn3b5co.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=K.Fetscher@t-online.de \
    --cc=alsa-devel@lists.sourceforge.net \
    /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