From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] Binding: atmel-wm8904: add option to choose clock
Date: Thu, 16 Jan 2014 11:03:03 +0000 [thread overview]
Message-ID: <20140116110303.GN15567@sirena.org.uk> (raw)
In-Reply-To: <52D736E0.90207@atmel.com>
On Thu, Jan 16, 2014 at 09:33:20AM +0800, Bo Shen wrote:
> On 01/15/2014 07:54 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >> Optional properties:
> >> - pinctrl-names, pinctrl-0: Please refer to pinctrl-bindings.txt
> >>+ - clk_from_rk_pin: according to hardware design, clk privide on rk pin
> > provide
> > ?? no example?
> If this patch set is acceptable. The sama5 audio will use it (I will
> send patch after this patch set). Do I still need to put the example
> in the binding document?
It doesn't seem terribly worthwhile to have the example include every
boolean property, it's not like people should find it hard to work out
how to use them.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140116/4accd138/attachment.sig>
next prev parent reply other threads:[~2014-01-16 11:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 3:25 [PATCH 0/3] ASoC: atmel_ssc_dai: add option to choose clock Bo Shen
2014-01-14 3:25 ` [PATCH 1/3] ASoC: atmel_ssc_dai: make " Bo Shen
2014-01-14 3:25 ` [PATCH 2/3] ASoC: atmel_wm8904: make it available " Bo Shen
2014-01-14 20:36 ` Mark Brown
2014-01-16 1:31 ` Bo Shen
2014-01-27 20:59 ` Mark Brown
2014-01-15 17:16 ` Nicolas Ferre
2014-01-14 3:25 ` [PATCH 3/3] Binding: atmel-wm8904: add option " Bo Shen
2014-01-15 11:54 ` Jean-Christophe PLAGNIOL-VILLARD
2014-01-16 1:33 ` Bo Shen
2014-01-16 11:03 ` Mark Brown [this message]
2014-01-15 17:17 ` Nicolas Ferre
2014-01-16 1:38 ` Bo Shen
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=20140116110303.GN15567@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).