From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
Cc: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org"
<alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org>,
"Erik Gilling (konkers-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org)"
<konkers-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
"Colin Cross (ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org)"
<ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [alsa-devel] Tegra ASoC, multiple boards, platform data, and conditionals in machine driver
Date: Mon, 11 Apr 2011 02:58:09 +0100 [thread overview]
Message-ID: <20110411015809.GA23214@sirena.org.uk> (raw)
In-Reply-To: <BANLkTikQhe1+ufvZWFKU1DT+XCS9=xE0Xw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Sun, Apr 10, 2011 at 11:18:17AM -0700, Olof Johansson wrote:
> built. It also makes it harder to maintain a multiplatform kernel if
> configuration data is pulled in at build time instead of runtime (i.e.
> headers vs platform_data or similar).
Note that whatever option is chosen the configuration should be pulled
in at runtime, it's purely a question of where the data table goes - do
you pass the full thing through platform datra or do you just pass the
machine type.
> In other words, I would prefer option (b) above.
Another thing to bear in mind is that it's only feasable to try to
combine the Tegra/WM8903 combinations - trying to combine machine
drivers for multiple unrelated CODECs isn't going to work well.
next prev parent reply other threads:[~2011-04-11 1:58 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 ` Mark Brown [this message]
[not found] ` <20110411015809.GA23214-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2011-04-11 15:27 ` [alsa-devel] " Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF0493EB3B8D-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-04-11 17:57 ` Olof Johansson
2011-04-11 20:30 ` Mark Brown
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=20110411015809.GA23214@sirena.org.uk \
--to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
--cc=konkers-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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