All of lore.kernel.org
 help / color / mirror / Atom feed
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 3/4] ASoC SST: add mid machine driver
Date: Tue, 28 Dec 2010 14:57:58 +0000	[thread overview]
Message-ID: <20101228145757.GE31883@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1293538287-31918-1-git-send-email-vinod.koul@intel.com>

On Tue, Dec 28, 2010 at 05:41:27PM +0530,  Koul, Vinod wrote:
> From: Vinod Koul <vinod.koul@intel.com>
> 
> This patch adds the mic machine driver
> The mid machine driver glues the msic and mid_platfrom driver to form the asoc sound driver

A machine driver should be for a particular machine, describing how the
various components have been connected on that particular machine.  This
looks like you're trying to do a single machine driver for all systems.

Probably this should have some sort of name indicating that it's for use
with systems that are trying to do something using the BIOS scheme
you've got for these systems; I'd expect that if the systems get much
traction in the market you'll also end up with systems implementing
regular ASoC machine drivers too.

> +#define MONO 1
> +#define STEREO 2
> +#define MAX_CAP 5
> +#define DRIVER_NAME_MFLD "msic_audio"
> +#define DRIVER_NAME_MRST "pmic_audio"
> +#define CPU_CHIP_LINCROFT       1 /* System running lincroft */
> +#define CPU_CHIP_PENWELL        2 /* System running penwell */
> +#define MSIC_CODEC		3

Here and through most of the rest of the driver you need to namespace
stuff more.

  reply	other threads:[~2010-12-28 14:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28 12:11 [RFC 3/4] ASoC SST: add mid machine driver  Koul, Vinod
2010-12-28 14:57 ` Mark Brown [this message]
2010-12-28 15:43   ` Koul, Vinod

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=20101228145757.GE31883@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.