Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Krzysztof Helt <krzysztof.h1@gmail.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: full duplex AD1848 (was SC-6000 driver)
Date: Fri, 07 Sep 2007 14:00:59 +0200	[thread overview]
Message-ID: <46E13D7B.4030206@gmail.com> (raw)
In-Reply-To: <20070907103447.226b5ae3.krzysztof.h1@gmail.com>

On 09/07/2007 10:34 AM, Krzysztof Helt wrote:

> According to a datasheet, the AD1848K (which was a popular version of
> AD1848) is full-duplex (can work in single-dma mode or with two dma
> channels).

Yes, I see...

> The AD1848 in my SC-6000 is not the K version (at least it is not marked
> on the chip) but I saw a photo on the net with SC-6000 and AD1848K (it
> had no YMF-262 chip but a different one).
> 
> I am looking for the AD1848 datasheet  for the pre-K version (or list of 
> differences between K and earlier versions).

Can also only find the K datasheet. Not sure what's up with that -- the 
existing ad1848 driver is simplex only.

> Also, I would like to know how you put your SG card into full-duplex
> mode.

That may be the easiest test yes. Try setting bit 2 of mss_config (| 4). 
This seems to be the generic way to enable duplex on mss/wss and it works 
here. The capture channel is fixed for a fiven playback channel:

P = 0 ==> C = 1
P = 1 ==> C = 0
P = 3 ==> C = 0

By the way -- I'm running into a bug somewhere in cs4231_lib where sometimes 
the playback IRQ stops firing when you start a capture. Stopping both the 
capture and playback and then re-starting the playback works, after which 
things may or may not hang again at re-starting the capture.

Could also be a hardware bug I guess -- will need to test further again 
(sigh). But just in case you'd also run into this, don't give up on 
ful-duplex if it only sometimes doesn't work right, as there might very well 
be a bug lurking in cs4231_lib.

(bug cannot be in my own code, as that's just setup and nowhere to be found 
anymore when things are running).

Rene.

  reply	other threads:[~2007-09-07 12:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06  6:49 [PATCH] Gallant SC-6000 driver (4th version) Krzysztof Helt
2007-09-06 10:12 ` Rene Herman
2007-09-06 11:20   ` Rene Herman
2007-09-06 14:03     ` Krzysztof Helt
2007-09-06 15:18       ` Rene Herman
2007-09-07  8:34         ` full duplex AD1848 (was SC-6000 driver) Krzysztof Helt
2007-09-07 12:00           ` Rene Herman [this message]
2007-09-06 21:12   ` [PATCH] Gallant SC-6000 driver (4th version) Krzysztof Helt
2007-09-06 21:16     ` Rene Herman
2007-09-07 11:11       ` Takashi Iwai
2007-09-07 12:11         ` Rene Herman

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=46E13D7B.4030206@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=krzysztof.h1@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox