From: "Jon Smirl" <jonsmirl@gmail.com>
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: Wed, 24 Oct 2007 11:28:27 -0400 [thread overview]
Message-ID: <9e4733910710240828x412f598dy7fc4a75faa76358d@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40710240820l62d5a50ewcd7707fed8f9176f@mail.gmail.com>
On 10/24/07, Grant Likely <grant.likely@secretlab.ca> wrote:
> > Two valid methods have been proposed
> > 1. a codec-
>
> oops
>
> 1. a codec-handle property in the i2s node
> 2. an i2s-handle property in the codec node
>
> Either are reasonable. I prefer putting the handle in the i2s node;
> but I'm looking at it from the way that ethernet phys are being
> described currently. The other is also perfectly valid.
>
> I suppose it depends on what point of view you see the system from; either:
> a. the codec is supported by the i2s bus, in which case use the
> i2s-handle property
> b. the i2s bus is supported by the codec; in which case use the
> codec-handle property.
Do you want to pick one and add it to the device tree documentation
with an example for i2s and ac97? I'll use which ever one is picked.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-10-24 15:28 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
2007-10-24 15:16 ` Grant Likely
2007-10-24 15:20 ` Grant Likely
2007-10-24 15:28 ` Jon Smirl [this message]
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=9e4733910710240828x412f598dy7fc4a75faa76358d@mail.gmail.com \
--to=jonsmirl@gmail.com \
--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).