From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Kukjin Kim <kgene.kim@samsung.com>,
Thomas Abraham <thomas.abraham@linaro.org>
Subject: Re: Device tree support for WM8994 and WM9713.
Date: Wed, 23 Nov 2011 10:28:15 +0000 [thread overview]
Message-ID: <20111123102814.GH4332@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1322028233.1516.239.camel@vkoul-udesk3>
On Wed, Nov 23, 2011 at 11:33:53AM +0530, Vinod Koul wrote:
> On Tue, 2011-11-22 at 19:43 +0000, Mark Brown wrote:
> > Looking at those they're going to need the regulator bindings for device
> > tree to do anything useful. I'd expect that to go into 3.3 but it'll be
> > hassle propagating the binding bits.
> I have a question here, how does using DT to a codec (which can be used
> even on a system where there is no DT present) be generic and break the
> assumption that codec does not know anything about the system it
> operates in?
> This should be done for machine or cpu driver which know if system has
> DT or not?
When drivers implement device tree support this should be done in
addition to rather than instead of platform data support so other
platforms should not be affected. A very common way of implementing
this is that the device tree parsing code translates the device tree
into a platform data structure and then the driver runs off a copy of
the platform data structure.
prev parent reply other threads:[~2011-11-23 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 5:58 Device tree support for WM8994 and WM9713 Thomas Abraham
2011-11-22 12:42 ` Mark Brown
2011-11-22 14:39 ` Thomas Abraham
2011-11-22 19:43 ` Mark Brown
2011-11-23 6:03 ` Vinod Koul
2011-11-23 10:28 ` 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=20111123102814.GH4332@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=kgene.kim@samsung.com \
--cc=thomas.abraham@linaro.org \
--cc=vinod.koul@linux.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.