From: "Jon Smirl" <jonsmirl@gmail.com>
To: "PowerPC dev list" <Linuxppc-dev@ozlabs.org>
Subject: Audio codec device tree entries
Date: Mon, 22 Oct 2007 21:59:00 -0400 [thread overview]
Message-ID: <9e4733910710221859q6ea54810nba58907d5ddd966d@mail.gmail.com> (raw)
Is this what the device tree entries should look like?
First example is ac97 audio:
ac97@2000 { // PSC1
device_type = "sound";
compatible = "mpc5200b-psc-ac97\0mpc5200-psc-ac97";
cell-index = <0>;
reg = <2000 100>;
interrupts = <2 1 0>;
interrupt-parent = <&mpc5200_pic>;
codec-handle = <&codec0>
};
pseudo-sound@0 { // use to trigger loading platform specific fabric driver
device_type = "pseudo-sound"
};
codec0:codec@0 {
device_type = "codec"
compatible = "stac9766\0ac97"
};
Second is i2s/i2c connected:
How do I link this to the i2c bus?
i2s@2000 { // PSC1
device_type = "sound";
compatible = "mpc5200b-psc-i2s\0mpc5200-psc-i2s";
cell-index = <0>;
reg = <2000 100>;
interrupts = <2 1 0>;
interrupt-parent = <&mpc5200_pic>;
codec-handle = <&codec0>
};
i2c@3d00 {
device_type = "i2c";
compatible = "mpc5200b-i2c\0mpc5200-i2c\0fsl-i2c";
cell-index = <0>;
reg = <3d00 40>;
interrupts = <2 f 0>;
interrupt-parent = <&mpc5200_pic>;
fsl5200-clocking;
};
pseudo-sound@0 { // use to trigger loading platform specific fabric driver
device_type = "pseudo-sound"
};
codec0:codec@0 {
device_type = "codec"
compatible = "tas5508"
};
--
Jon Smirl
jonsmirl@gmail.com
next reply other threads:[~2007-10-23 1:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 1:59 Jon Smirl [this message]
2007-10-23 2:57 ` Audio codec device tree entries 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
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=9e4733910710221859q6ea54810nba58907d5ddd966d@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=Linuxppc-dev@ozlabs.org \
/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).