All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Sasha Khapyorsky <sashak@smlink.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ali5451.c: M5451 info needed
Date: Mon, 23 May 2005 12:17:17 +0200	[thread overview]
Message-ID: <s5hu0ku2qmq.wl@alsa2.suse.de> (raw)
In-Reply-To: <20050522001953.GG27978@tecr>

At Sun, 22 May 2005 03:19:53 +0300,
Sasha Khapyorsky wrote:
> 
> Hi,
> 
> I'm trying now to add MC97 modem support for ALi M5451 (ali5451.c driver).
> There is preliminary patch attached (not for inclusion yet: at least
> big clean up is needed). I don't have device data sheets and patch was
> based on existed audio code.
> 
> Basically it works in both directions playback and capture. But dma is
> configured so that interrupt is generated at middle of buffer regardless to
> period_size value. Same story with audio capture.
> 
> Anybody know how to config M5451 dma so that it will be able to work
> with multiple blocks and generate interrupts at period_size (if possible)?
> And/or may point me to data sheet or at least M5451 dma related info?

I don't know of the datasheet of this chipset.  IIRC, we got a source
code from Acer, but not a datasheet.

Anyway, ali5451 looks pretty similar with Trident 4D DX/NX.
The chip supports only 2 fixed periods.  If you need more periods,
allocate an extra voice with the period size and let it generating
interrupts but not producing sounds.


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click

  reply	other threads:[~2005-05-23 10:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-22  0:19 ali5451.c: M5451 info needed Sasha Khapyorsky
2005-05-23 10:17 ` Takashi Iwai [this message]
2005-05-23 19:37   ` Sasha Khapyorsky

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=s5hu0ku2qmq.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=sashak@smlink.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.