From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: Olof Johansson <olof@lixom.net>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Erik Gilling (konkers@google.com)" <konkers@google.com>,
"Colin Cross (ccross@android.com)" <ccross@android.com>
Subject: Re: Tegra ASoC, multiple boards, platform data, and conditionals in machine driver
Date: Mon, 11 Apr 2011 13:30:44 -0700 [thread overview]
Message-ID: <20110411203044.GF29405@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF0493EB3B8D@HQMAIL01.nvidia.com>
On Mon, Apr 11, 2011 at 08:27:51AM -0700, Stephen Warren wrote:
> Mark Brown wrote at Sunday, April 10, 2011 7:58 PM:
> > you pass the full thing through platform datra or do you just pass the
> > machine type.
> Well, I was thinking of eliminating platform data completely; the
> selection of the correct ASoC machine driver would be based on the
Right, the machine type is essentially platform data.
> name of the platform device, and the machine driver would use
> machine_is_*() to determine any machine-specific actions/data. So yes,
> at run-time, but not using runtime-determined data *tables* at all.
There'd be data of some kind in the machine driver, even if they
happened to be coded as if statements.
prev parent reply other threads:[~2011-04-11 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 19:43 Tegra ASoC, multiple boards, platform data, and conditionals in machine driver Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF0493EB3A50-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-04-09 2:30 ` Mark Brown
[not found] ` <20110409023057.GA3792-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2011-04-10 2:52 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF0493EB3B5B-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-04-10 18:18 ` Olof Johansson
[not found] ` <BANLkTikQhe1+ufvZWFKU1DT+XCS9=xE0Xw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-11 1:58 ` [alsa-devel] " Mark Brown
[not found] ` <20110411015809.GA23214-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2011-04-11 15:27 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF0493EB3B8D-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-04-11 17:57 ` Olof Johansson
2011-04-11 20:30 ` 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=20110411203044.GF29405@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ccross@android.com \
--cc=konkers@google.com \
--cc=linux-tegra@vger.kernel.org \
--cc=olof@lixom.net \
--cc=swarren@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox