From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Timur Tabi <timur-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: "alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org"
<alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org>,
"patches-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org"
<patches-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>,
Liam Girdwood <lrg-l0cyMroinI0@public.gmane.org>,
"devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: [PATCH 1/3] ASoC: Add device tree binding for WM8770
Date: Tue, 30 Aug 2011 19:18:09 +0100 [thread overview]
Message-ID: <20110830181809.GQ2061@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4E5D28AB.7040206-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
On Tue, Aug 30, 2011 at 01:15:07PM -0500, Timur Tabi wrote:
> Note that I require a clock-frequency property to indicate the input clock
> frequency on the codec itself.
It's listed as optional in the binding (and would in general need to
be).
next prev parent reply other threads:[~2011-08-30 18:18 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
[not found] ` <4E5D28AB.7040206-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-08-30 18:18 ` Mark Brown [this message]
[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=20110830181809.GQ2061@opensource.wolfsonmicro.com \
--to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=lrg-l0cyMroinI0@public.gmane.org \
--cc=patches-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org \
--cc=timur-KZfg59tc24xl57MIdRCFDg@public.gmane.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).