From: Takashi Iwai <tiwai@suse.de>
To: Dave Dillow <dave@thedillows.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] sis7019: support the SiS 7019 Audio Accelerator
Date: Wed, 28 Nov 2007 13:36:21 +0100 [thread overview]
Message-ID: <s5h3auqim2i.wl%tiwai@suse.de> (raw)
In-Reply-To: <1196255015.7017.52.camel@obelisk.thedillows.org>
At Wed, 28 Nov 2007 08:03:35 -0500,
Dave Dillow wrote:
>
> > > +static struct snd_pcm_hardware sis_playback_hw_info = {
> > > + .info = (SNDRV_PCM_INFO_MMAP |
> > > + SNDRV_PCM_INFO_MMAP_VALID |
> > > + SNDRV_PCM_INFO_INTERLEAVED |
> > > + SNDRV_PCM_INFO_BLOCK_TRANSFER |
> > > + SNDRV_PCM_INFO_SYNC_START |
> > > + SNDRV_PCM_INFO_RESUME),
> >
> > SNDRV_PCM_INFO_SYNC_START seems invalid here. It's not implemented in
> > the driver.
>
> Perhaps I'm misunderstanding what SYNC_START is for -- I can start
> multiple playback/capture substreams at once in ->trigger(). If it means
> something else, can you point to a driver that does implement it
> properly so that I can see if can be implemented?
Sorry, looks like I typo'ed when I searched strngs (due to a damn
keyboard scan bug in the recent xorg...)
Please disregard my previous comment.
> > > +static void __sis_map_silence(struct sis7019 *sis)
> >
> > Any reason to use __ prefix?
>
> It requires locks to be held when it is called, making it an internal
> helper function. I'd prefer to keep the prefix, but it could go away, or
> be merged into the one call-site.
OK, then it's fine. But add a proper comment. Otherwise no one else
would understand the difference.
Thanks,
Takashi
next prev parent reply other threads:[~2007-11-28 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 7:19 [PATCH 1/2] sis7019: support the SiS 7019 Audio Accelerator Dave Dillow
2007-11-28 9:56 ` Takashi Iwai
2007-11-28 13:03 ` Dave Dillow
2007-11-28 12:36 ` Takashi Iwai [this message]
2007-11-28 13:22 ` Dave Dillow
2007-11-28 12:50 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2007-12-08 23:54 Dave Dillow
2007-12-09 18:04 ` Dave Dillow
2007-12-13 15:54 ` Takashi Iwai
2007-12-13 17:47 ` Dave Dillow
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=s5h3auqim2i.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=dave@thedillows.org \
/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