From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
Harsha Priya <priya.harsha@intel.com>,
lrg@slimlogic.co.uk
Subject: Re: [RFC 2/4] ASoC SST: Add mid platfrom driver
Date: Tue, 28 Dec 2010 14:52:20 +0000 [thread overview]
Message-ID: <20101228145219.GD31883@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1293538258-31885-1-git-send-email-vinod.koul@intel.com>
On Tue, Dec 28, 2010 at 05:40:58PM +0530, Koul, Vinod wrote:
> + /*.suspend = intelmid_platform_suspend,
> + .resume = intelmid_platform_resume,*/
Remove the commented out code until it's implemeneted.
> +MODULE_DESCRIPTION("ASoC Intel(R) PLATFORM driver");
> +MODULE_AUTHOR("Harsha Priya");
> +MODULE_LICENSE("GPL v2");
MODULE_ALIAS() too.
> +#define MIN_RATE 8000
> +#define MAX_RATE 48000
> +#define MIN_CHANNEL 1
> +#define MAX_CHANNEL_AMIC 2
> +#define MAX_CHANNEL_DMIC 5
> +#define MAX_BUFFER (800*1024)
> +#define MIN_BUFFER (800*1024)
> +#define MIN_PERIOD_BYTES 32
> +#define MAX_PERIOD_BYTES MAX_BUFFER
> +#define MIN_PERIODS 2
> +#define MAX_PERIODS (1024*2)
> +#define FIFO_SIZE 0
> +#define MSIC_VENDOR_ID 0x3
> +#define SST_CARD_NAMES "intel_mid_card"
These pretty much all need namespacing; given that they're only used in
one place for the most part it'd seem as well to just not bother having
defines for them in the first place.
> +enum mid_drv_status {
> + INIT = 1,
> + STARTED,
> + RUNNING,
> + PAUSED,
> + DROPPED,
> +};
> +
> +/* device */
> +enum SND_INPUT_DEVICE {
> + AMIC,
> + DMIC,
> + HS_MIC,
> + IN_UNDEFINED
> +};
Namespacing here too; it seems very odd that the CPU would care what's
connected to it.
> +void period_elapsed(void *mad_substream)
> +{
Staticise this or namespace it if it's used externally.
prev parent reply other threads:[~2010-12-28 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 12:10 [RFC 2/4] ASoC SST: Add mid platfrom driver Koul, Vinod
2010-12-28 14:52 ` Mark Brown [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=20101228145219.GD31883@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=priya.harsha@intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.com \
/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.