From: Timur Tabi <timur@freescale.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"patches@opensource.wolfsonmicro.com"
<patches@opensource.wolfsonmicro.com>, Liam Girdwood <lrg@ti.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH 1/3] ASoC: Add device tree binding for WM8770
Date: Tue, 30 Aug 2011 13:15:07 -0500 [thread overview]
Message-ID: <4E5D28AB.7040206@freescale.com> (raw)
In-Reply-To: <20110830181222.GP2061@opensource.wolfsonmicro.com>
Mark Brown wrote:
> I did say this before; personally I find having binding documentation at
> all for the basic I2C/SPI bus binding of a device to be a complete waste
> of time and would rather just not bother unless we have properties.
I'm okay with that, but it's not my decision. :-)
The codec node bindings that my audio driver expects are documented in ssi.txt.
Note that I require a clock-frequency property to indicate the input clock
frequency on the codec itself.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-08-30 18:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 13:27 [PATCH 1/3] ASoC: Add device tree binding for WM8770 Mark Brown
2011-08-29 13:27 ` [PATCH 2/3] ASoC: Add device tree binding for WM8776 Mark Brown
2011-08-29 13:27 ` [PATCH 3/3] ASoC: Add device tree binding for WM8804 Mark Brown
2011-08-30 15:48 ` [PATCH 1/3] ASoC: Add device tree binding for WM8770 Tabi Timur-B04825
[not found] ` <CAOZdJXUQpyvxOVgS9mPnMwJM1TNF-X+zOVkOsDqJM_oBNQih0Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-08-30 18:12 ` Mark Brown
2011-08-30 18:15 ` Timur Tabi [this message]
[not found] ` <4E5D28AB.7040206-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-08-30 18:18 ` Mark Brown
[not found] ` <1314624471-15381-1-git-send-email-broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2011-08-30 16:13 ` Grant Likely
2011-08-31 10:30 ` Liam Girdwood
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=4E5D28AB.7040206@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=lrg@ti.com \
--cc=patches@opensource.wolfsonmicro.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.