From: Clemens Ladisch <clemens@ladisch.de>
To: Knut Petersen <Knut_Petersen@t-online.de>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] rme96 synchronization support
Date: Mon, 05 Aug 2013 15:18:59 +0200 [thread overview]
Message-ID: <51FFA643.7060504@ladisch.de> (raw)
In-Reply-To: <51FF9C55.80701@t-online.de>
Knut Petersen wrote:
> SNDRV_PCM_INFO_MMAP_VALID |
> + SNDRV_PCM_INFO_SYNC_START |
Please use tabs like in other similar parts of the file.
> static void
> -snd_rme96_playback_start(struct rme96 *rme96,
> +snd_rme96_playcap_start(struct rme96 *rme96,
> int from_pause)
> {
> if (!from_pause) {
> writel(0, rme96->iobase + RME96_IO_RESET_PLAY_POS);
> + writel(0, rme96->iobase + RME96_IO_RESET_REC_POS);
> }
> -
> - rme96->wcreg |= RME96_WCR_START;
> + rme96->wcreg |= (RME96_WCR_START | RME96_WCR_START_2);
> writel(rme96->wcreg, rme96->iobase + RME96_IO_CONTROL_REGISTER);
> }
>
> static void
> +snd_rme96_playback_start(struct rme96 *rme96,
> + int from_pause)
> +{
> + if ((rme96->playback_substream && rme96->capture_substream) &&
> + (rme96->playback_substream->group == rme96->capture_substream->group)) {
> + snd_rme96_playcap_start(rme96,from_pause);
> + } else {
> + if (!from_pause) {
> + writel(0, rme96->iobase + RME96_IO_RESET_PLAY_POS);
> + }
> + rme96->wcreg |= RME96_WCR_START;
> + writel(rme96->wcreg, rme96->iobase + RME96_IO_CONTROL_REGISTER);
> + }
> +}
This is hard to maintain because there is duplicated code.
The proper way to write a synchronized start/stop trigger is to collect
the needed register bits first, and then apply them at once to the
register; this works for both single and grouped usage:
trigger_start()
{
unsigned int wc_bits = 0;
snd_pcm_group_for_each_entry(s, substream) {
if (s == playback_substream) {
bits |= RME96_WCR_START;
snd_pcm_trigger_done(s, substream);
} else if (s == capture_substream) {
bits |= RME96_WCR_START_2;
snd_pcm_trigger_done(s, substream);
}
}
rme96->wcreg |= bits;
writel(rme96->wcreg, ...);
}
> -
> +
Are these whitespace changes deliberate?
Regards,
Clemens
next prev parent reply other threads:[~2013-08-05 13:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 12:36 [PATCH] rme96 synchronization support Knut Petersen
2013-08-05 13:18 ` Clemens Ladisch [this message]
2013-08-06 17:42 ` Knut Petersen
2013-08-07 7:08 ` Takashi Iwai
2013-08-08 10:52 ` Knut Petersen
2013-08-13 7:19 ` Takashi Iwai
2013-08-13 10:32 ` Knut Petersen
2013-08-13 10:37 ` Takashi Iwai
2013-08-13 21:12 ` [PATCH] rme96 add stream synchronization and PM support Knut Petersen
2013-08-14 15:06 ` Takashi Iwai
2013-08-15 6:01 ` Knut Petersen
2013-08-15 6:22 ` Takashi Iwai
2013-08-15 7:16 ` Knut Petersen
2013-08-15 8:37 ` Takashi Iwai
2013-08-21 7:44 ` Knut Petersen
2013-08-22 8:53 ` Takashi Iwai
[not found] ` <52160CDE.4070306@t-online.de>
2013-08-22 21:25 ` [PATCH] rme96 Add missing vmalloc.h inclusion 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=51FFA643.7060504@ladisch.de \
--to=clemens@ladisch.de \
--cc=Knut_Petersen@t-online.de \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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.