All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Remy Bruno <remy.bruno@trinnov.com>
Cc: Winfried Ritsch <ritsch@iem.at>, alsa-devel@lists.sourceforge.net
Subject: Re: RME AES32 & MADI
Date: Wed, 14 Feb 2007 16:00:02 +0100	[thread overview]
Message-ID: <s5hr6ssbx8t.wl%tiwai@suse.de> (raw)
In-Reply-To: <20070213104406.GA9387@trinnov.com>

Thanks for the patch.  Just a few comments below:

At Tue, 13 Feb 2007 11:44:06 +0100,
Remy Bruno wrote:
> @@ -943,12 +965,17 @@ static int hdspm_set_rate(struct hdspm *
>  	hdspm->control_register |= rate_bits;
>  	hdspm_write(hdspm, HDSPM_controlRegister, hdspm->control_register);
>  
> -	if (rate > 96000 /* 64000*/)
> -		hdspm->channel_map = channel_map_madi_qs;
> -	else if (rate > 48000)
> -		hdspm->channel_map = channel_map_madi_ds;
> -	else 
> -		hdspm->channel_map = channel_map_madi_ss;
> +	/* For AES32, need to set DDS value in FREQ register
> +	   For MADI, also apparently */
> +	hdspm_set_dds_value(hdspm, rate);
> +	
> +	if (hdspm->is_aes32 && rate != current_rate) {
> +		hdspm_write(hdspm, HDSPM_eeprom_wr, 0);
> +	}

Remove braces.

>  static int snd_hdspm_playback_open(struct snd_pcm_substream *substream)
>  {
>  	struct hdspm *hdspm = snd_pcm_substream_chip(substream);
>  	struct snd_pcm_runtime *runtime = substream->runtime;
>  
> -	snd_printdd("Open device substream %d\n", substream->stream);
> -
>  	spin_lock_irq(&hdspm->lock);
>  
>  	snd_pcm_set_sync(substream);
>  
>  	runtime->hw = snd_hdspm_playback_subinfo;
> +	runtime->dma_area = hdspm->playback_buffer;
> +	runtime->dma_bytes = HDSPM_DMA_AREA_BYTES;

Why this?  They are overwritten anyway in hw_params call.

> @@ -4011,6 +4143,8 @@ static int snd_hdspm_capture_open(struct
>  	spin_lock_irq(&hdspm->lock);
>  	snd_pcm_set_sync(substream);
>  	runtime->hw = snd_hdspm_capture_subinfo;
> +	runtime->dma_area = hdspm->capture_buffer;
> +	runtime->dma_bytes = HDSPM_DMA_AREA_BYTES;

Ditto.

> @@ -4184,7 +4325,8 @@ static int __devinit snd_hdspm_prealloca
>  	pcm = hdspm->pcm;
>  
>  /*	wanted = HDSPM_DMA_AREA_BYTES + 4096;*/	/* dont know why, but it works */
> -	wanted = HDSPM_DMA_AREA_BYTES;
> +	/* Two times, for both input and output */
> +	wanted = 2 * HDSPM_DMA_AREA_BYTES;

This shouldn't be necessary.  Since the buffer size for each stream is
fixed, it's not necessarily bigger than that.


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:[~2007-02-14 15:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31 12:11 RME AES32 & MADI Remy Bruno
2007-02-02 18:39 ` Takashi Iwai
2007-02-05  9:27   ` Winfried Ritsch
2007-02-05 10:11     ` Takashi Iwai
2007-02-13 10:44     ` Remy Bruno
2007-02-14 15:00       ` Takashi Iwai [this message]
2007-02-20 17:04         ` Remy Bruno
2007-02-22 15:37           ` Takashi Iwai
2007-02-28 17:29             ` Remy Bruno
2007-03-08 13:40               ` Takashi Iwai

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=s5hr6ssbx8t.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=remy.bruno@trinnov.com \
    --cc=ritsch@iem.at \
    /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.