Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Remy Bruno <remy.bruno@trinnov.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: RME 9632 - Problem half solved
Date: Fri, 06 Oct 2006 19:12:07 +0200	[thread overview]
Message-ID: <s5h64exs714.wl%tiwai@suse.de> (raw)
In-Reply-To: <20061006135355.GA22664@trinnov.com>

At Fri, 6 Oct 2006 15:53:55 +0200,
Remy Bruno wrote:
> 
> Hello,
> 
> I solved the matrix problem. In fact, it was quite obvious by looking at the
> hdsp driver code. The 9632 card was considered as a 9652 regarding the matrix,
> and so the offsets in the matrix were wrong. See the attached patch. I think
> the "switch()" statement should be replaced by an "if (hdsp->firmware_rev >=
> 0x96)", which would allow the next firmwares of the hdsp9632 to be considered
> as hdsp9632 and not as 9652.

Could you give a proper changelog text and a signed-off-by line to
merge your patch into ALSA tree?

> 
> For the frequency problem, I got an answer from RME which explains that another
> register needs to be set (together with the freq0, 1, 2 bits of the control
> register). This register is the "DDS" register. Here is how it should be
> computed:
> UINT64 CalcDDSValue(UINT64 rate)
> {
>         if (rate >= 112000)
>                 rate /= 4;
>         else if (rate >= 56000)
>                 rate /= 2;
> 
>         return 104857600000000 / rate;
> }
> MemBase[FREQ_REG] = (ULONG)CalcDDSValue(new_rate)
> 
> Any ideas of what the offset of this register is? If not, I will ask him. BTW,
> this register exists only for the 9632 and not for the 9652.

Hm, the numerator is pretty big, it's 0x100000 * 10^7.
A clock with fixed point?

Anyway, remember that you cannot use 64bit division in the linux
kernel code as it is.  You can use a macro div64_32 defined in pcm.h,
though.


Takashi

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2006-10-06 17:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-03 10:37 RME 9632 Remy Bruno
2006-10-06 13:53 ` RME 9632 - Problem half solved Remy Bruno
2006-10-06 17:12   ` Takashi Iwai [this message]
2006-10-09 10:18     ` Remy Bruno

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=s5h64exs714.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=remy.bruno@trinnov.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