From: Timur Tabi <timur@freescale.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: PowerPC dev list <Linuxppc-dev@ozlabs.org>
Subject: Re: Device trees and audio codecs
Date: Mon, 22 Oct 2007 10:40:17 -0500 [thread overview]
Message-ID: <471CC461.1080207@freescale.com> (raw)
In-Reply-To: <9e4733910710211729k2f2a065cm56670d1b0f90a1af@mail.gmail.com>
Jon Smirl wrote:
> I meant an ac97 bus. ac97 is conceptually the same as i2s with the
> control signals also routed over it. ac97 and i2s are handled in the
> same PSC on the 5200.
>
> I have received conflicting opinions as to whether a codec hooked to
> an ac97 bus should get a chip specific codec entry in the device tree.
I think it should. For one thing, ASoC requires a pointer to a structure in the
codec device driver so that it knows which functions to call to change volume.
What if you have multiple i2s/ac97 devices and multiple codecs? You'll need to
know which i2s device is connected to which codec. The only way to distinguish
that is by having a node for the codec under the i2s node.
next prev parent reply other threads:[~2007-10-22 15:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 15:33 Device trees and audio codecs Jon Smirl
2007-10-21 13:33 ` Timur Tabi
2007-10-21 14:01 ` Jon Smirl
2007-10-22 13:07 ` Timur Tabi
2007-10-23 19:12 ` Scott Wood
2007-10-21 19:14 ` Segher Boessenkool
2007-10-21 21:33 ` Jon Smirl
2007-10-21 22:06 ` Benjamin Herrenschmidt
2007-10-21 22:12 ` Jon Smirl
2007-10-21 22:19 ` Benjamin Herrenschmidt
2007-10-21 23:33 ` Segher Boessenkool
2007-10-22 0:29 ` Jon Smirl
2007-10-22 15:40 ` Timur Tabi [this message]
2007-10-22 18:43 ` Segher Boessenkool
2007-10-23 3:24 ` Grant Likely
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=471CC461.1080207@freescale.com \
--to=timur@freescale.com \
--cc=Linuxppc-dev@ozlabs.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.