From: Timur Tabi <timur@freescale.com>
To: Timur Tabi <timur@freescale.com>, Jon Smirl <jonsmirl@gmail.com>,
ALSA-devel <alsa-devel@alsa-project.org>
Subject: Re: Thoughts on ASOC v2 driver architecture
Date: Mon, 16 Jun 2008 12:10:36 -0500 [thread overview]
Message-ID: <48569E8C.3030708@freescale.com> (raw)
In-Reply-To: <20080616170325.GD8544@sirena.org.uk>
Mark Brown wrote:
> Right, but you could not then idiomatically have a device tree entry
> saying something to the effect of "This board has a Frobnitz 2000 with
> control line 1 connected to GPIO4 and control line 2 connected to GPIO5"
Yes.
> which would register the presence of this other device (in the same way
> as you have an entry for an I2C device)?
I'm still not sure I understand. I2C devices are represented by complete nodes
under the I2C adapter node. The file fsl_soc.c scans each I2C adapter node, and
enumerates every child node under the adapter node. It creates I2C platform
devices this way.
I'm not sure how we could use this model for ASoC. There is no "ASoC adapter
node" in the device tree, because there is no ASoC adapter.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-06-16 17:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 18:10 Thoughts on ASOC v2 driver architecture Jon Smirl
2008-06-16 10:39 ` Liam Girdwood
2008-06-16 13:26 ` Jon Smirl
2008-06-16 14:23 ` Timur Tabi
2008-06-16 14:32 ` Jon Smirl
2008-06-16 15:03 ` Mark Brown
2008-06-16 15:36 ` Timur Tabi
2008-06-16 15:45 ` Mark Brown
2008-06-16 15:49 ` Timur Tabi
2008-06-16 17:03 ` Mark Brown
2008-06-16 17:10 ` Timur Tabi [this message]
2008-06-16 15:53 ` Jon Smirl
2008-06-16 16:01 ` Timur Tabi
2008-06-16 16:23 ` Jon Smirl
2008-06-16 16:24 ` Timur Tabi
2008-06-17 0:58 ` Jon Smirl
2008-06-17 14:55 ` Timur Tabi
2008-06-16 16:11 ` Jon Smirl
2008-06-16 16:58 ` Mark Brown
2008-06-16 17:00 ` Timur Tabi
2008-06-16 16:24 ` Mark Brown
2008-06-16 15:34 ` Timur Tabi
2008-06-16 13:47 ` Jon Smirl
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=48569E8C.3030708@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=jonsmirl@gmail.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.