From: Daniel Mack <daniel@zonque.org>
To: Bard Liao <bardliao@realtek.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Mark Brown (broonie@linaro.org)" <broonie@linaro.org>
Subject: Re: Use more than 1 .c file for a single codec driver
Date: Fri, 8 Nov 2013 12:37:46 +0100 [thread overview]
Message-ID: <20131108113746.GA6684@tamtam.fritz.box> (raw)
In-Reply-To: <1121E117AD4ECE49880A389A396215BB935CA227EA@rtitmbs7.realtek.com.tw>
On Fri, Nov 08, 2013 at 01:32:55PM +0800, Bard Liao wrote:
> Can we use more than one .c file for a codec driver?
> There are some codecs with DSP function.
> I want to know if I can separate the DSP part from other functions.
> For example, rt5670.c/.h rt5670-dsp.c/.h for RT5670 codec driver.
Have a look at adau1701.c and sigmadsp.c, and at the Makefile of course.
Daniel
prev parent reply other threads:[~2013-11-08 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 5:32 Use more than 1 .c file for a single codec driver Bard Liao
2013-11-08 11:37 ` Daniel Mack [this message]
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=20131108113746.GA6684@tamtam.fritz.box \
--to=daniel@zonque.org \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@linaro.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;
as well as URLs for NNTP newsgroup(s).