From: Takashi Iwai <tiwai@suse.de>
To: Knut Petersen <Knut_Petersen@t-online.de>
Cc: alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: [PATCH] rme96 synchronization support
Date: Wed, 07 Aug 2013 09:08:42 +0200 [thread overview]
Message-ID: <s5h4nb2asg5.wl%tiwai@suse.de> (raw)
In-Reply-To: <52013579.7020304@t-online.de>
At Tue, 06 Aug 2013 19:42:17 +0200,
Knut Petersen wrote:
>
> On 05.08.2013 15:18, Clemens Ladisch wrote:
> > Knut Petersen wrote:
> >> SNDRV_PCM_INFO_MMAP_VALID |
> >> + SNDRV_PCM_INFO_SYNC_START |
> > Please use tabs like in other similar parts of the file.
>
> ack
>
> >> 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:
>
> Yes, there is duplicated code ... I´ll remove that in a V2 of the patch.
> But I do not think that it is less readable/maintainable if bit masks are
> prepared at the place of use ...
>
> >> -
> >> +
> > Are these whitespace changes deliberate?
>
> No, they are artifacts of inserting/removing debug code at a place
> where originally a line with nothing but a tabulator is present.
>
> Your comments were all about coding style. Have you had a look
> at the content of the code?
Clemens commented on your code: make a single trigger function that
can handle both playback and capture (one or both) streams. It makes
the code more maintainable.
Hint: even for clearing the position register, you can do it in a
single place like below:
if (!from_pause) {
if (bits & RME96_WCR_START)
writel(0, rme96->iobase + RME96_IO_RESET_PLAY_POS);
if (bits & RME96_WCR_START_2)
writel(0, rme96->iobase + RME96_IO_RESET_REC_POS);
}
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2013-08-07 7:07 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
2013-08-06 17:42 ` Knut Petersen
2013-08-07 7:08 ` Takashi Iwai [this message]
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=s5h4nb2asg5.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Knut_Petersen@t-online.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).