From: David Gibson <david@gibson.dropbear.id.au>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: PowerPC dev list <Linuxppc-dev@ozlabs.org>,
Timur Tabi <timur@freescale.com>
Subject: Re: Audio codec device tree entries
Date: Thu, 25 Oct 2007 09:52:14 +1000 [thread overview]
Message-ID: <20071024235214.GA23694@localhost.localdomain> (raw)
In-Reply-To: <fa686aa40710240828p532e8e4axf1f9b9ad4cd324f8@mail.gmail.com>
On Wed, Oct 24, 2007 at 09:28:42AM -0600, Grant Likely wrote:
> On 10/24/07, Timur Tabi <timur@freescale.com> wrote:
> > Jon Smirl wrote:
[snip]
> > My vote is for this version. In fact, I think it *has* to be this way. If
> > you're using a CS4270 codec (as I am), the I2C interface is *optional*. So I
> > want the I2S node to point to the I2C node if it exists.
>
> It doesn't have to be this way. If the codec does not have a control
> interface, then it can happily be a child of the i2s node. But if it
> *does*; don't break convention by separating it from it's control
> interface.
>
> I strongly recommend following the lead of ethernet phys and mdio
> busses here.
Yes. Devices should appear on the bus from which they're addressable,
that is from the control interface in this case. Sometimes different
things need to be done for bus-bridges which are configured from a
different bus than the one they bridge, but this is not such a
situation.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-10-24 23:52 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 1:59 Audio codec device tree entries Jon Smirl
2007-10-23 2:57 ` David Gibson
2007-10-23 3:57 ` Grant Likely
2007-10-23 8:06 ` Segher Boessenkool
2007-10-23 15:27 ` Timur Tabi
2007-10-23 16:56 ` Segher Boessenkool
2007-10-23 22:29 ` Jon Smirl
2007-10-24 14:13 ` Timur Tabi
2007-10-24 15:00 ` Jon Smirl
2007-10-24 15:07 ` Timur Tabi
2007-10-24 15:28 ` Grant Likely
2007-10-24 23:52 ` David Gibson [this message]
2007-10-24 15:16 ` Grant Likely
2007-10-24 15:20 ` Grant Likely
2007-10-24 15:28 ` Jon Smirl
2007-10-24 15:43 ` Grant Likely
2007-10-24 15:54 ` Jon Smirl
2007-10-24 16:01 ` Timur Tabi
2007-10-24 16:39 ` Grant Likely
2007-10-24 16:41 ` Timur Tabi
2007-10-24 16:47 ` Grant Likely
2007-10-24 16:38 ` Grant Likely
2007-10-24 16:41 ` Timur Tabi
2007-10-24 16:52 ` Grant Likely
2007-10-24 17:01 ` Jon Smirl
2007-10-24 17:13 ` Grant Likely
2007-10-24 17:13 ` Timur Tabi
2007-10-24 19:31 ` Jon Smirl
2007-10-24 19:41 ` Timur Tabi
2007-10-24 19:56 ` Jon Smirl
2007-10-25 0:04 ` David Gibson
2007-10-25 0:17 ` Jon Smirl
2007-10-25 0:38 ` David Gibson
2007-10-25 3:11 ` Jon Smirl
2007-10-25 16:14 ` Timur Tabi
2007-10-24 23:55 ` David Gibson
2007-10-24 15:23 ` Jon Smirl
2007-10-24 15:40 ` Timur Tabi
2007-10-24 15:54 ` Grant Likely
2007-10-24 15:08 ` Grant Likely
2007-10-24 15:19 ` Jon Smirl
2007-10-25 0:01 ` David Gibson
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=20071024235214.GA23694@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=Linuxppc-dev@ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=timur@freescale.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;
as well as URLs for NNTP newsgroup(s).