From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: ext David Brownell <david-b@pacbell.net>
Cc: steve@sakoman.com, Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org
Subject: Re: [patch 2.6.27-rc6-omap] ASOC: quieter boot for non-Overo boards
Date: Fri, 26 Sep 2008 10:37:32 +0300 [thread overview]
Message-ID: <20080926103732.382cfb5b.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <200809251041.48997.david-b@pacbell.net>
On Thu, 25 Sep 2008 10:41:48 -0700
"ext David Brownell" <david-b@pacbell.net> wrote:
> > Putting the board specific bits in the
> > arch/arm/mach-omap2/board-XYZ.c file has been discussed a number of
> > times on alsa-devel and the folks there insist that for now (i.e.
> > ASoC V1) this is the proper way to do things.
>
> Hmm, I'm not sure I follow. They want the SOC devices
> in the wrong place in the driver model tree, potentially
> impacting power management?
>
> I don't want to fight that fight, but ... that seems unwise.
>
Yep. Now in ASoC v1, the machine, platform/CPU and codec are tied
together during compile time and I think it has been easier to
review/manage by keeping them under one sound/soc directory.
I suppose that when ASoC v2 is in place and devices can be individually
probed, we might see that machine drivers will start moving out from
there.
Jarkko
prev parent reply other threads:[~2008-09-26 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 21:14 [patch 2.6.27-rc6-omap] ASOC: quieter boot for non-Overo boards David Brownell
2008-09-25 12:49 ` Tony Lindgren
2008-09-25 16:50 ` David Brownell
2008-09-25 17:07 ` Steve Sakoman
2008-09-25 17:41 ` David Brownell
2008-09-26 7:37 ` Jarkko Nikula [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=20080926103732.382cfb5b.jarkko.nikula@nokia.com \
--to=jarkko.nikula@nokia.com \
--cc=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=steve@sakoman.com \
--cc=tony@atomide.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