From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 2/2] ASoC: SAMSUNG: Add DT support for i2s
Date: Wed, 19 Dec 2012 13:24:14 +0000 [thread overview]
Message-ID: <20121219132414.2CF653E0AD7@localhost> (raw)
In-Reply-To: <1355395373-22058-3-git-send-email-padma.v@samsung.com>
On Thu, 13 Dec 2012 16:12:53 +0530, Padmavathi Venna <padma.v@samsung.com> wrote:
> Add support for device based discovery.
>
> Signed-off-by: Padmavathi Venna <padma.v@samsung.com>
> ---
> .../devicetree/bindings/sound/samsung-i2s.txt | 75 +++++++
> sound/soc/samsung/dma.c | 1 +
> sound/soc/samsung/dma.h | 1 +
> sound/soc/samsung/i2s.c | 233 ++++++++++++++++----
> 4 files changed, 269 insertions(+), 41 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/sound/samsung-i2s.txt
>
> diff --git a/Documentation/devicetree/bindings/sound/samsung-i2s.txt b/Documentation/devicetree/bindings/sound/samsung-i2s.txt
> new file mode 100644
> index 0000000..bff47b4
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/samsung-i2s.txt
> @@ -0,0 +1,75 @@
> +* Samsung I2S controller
> +
> +Required SoC Specific Properties:
> +
> +- compatible : "samsung,samsung-i2s"
Isn't that kind of redundant? :-)
The format of the compatible strings should be "<vendor>,<part-number>-i2s".
Please be specific about the part number that you're doing the binding
for. For example; use "samsung,exynos4210-i2s" instead of "samsung,exynos-i2s".
> +- reg: physical base address of the controller and length of memory mapped
> + region.
> +
> +[PRELIMINARY: the dma channel allocation will change once there are
> +official DMA bindings]
> +
> +- tx-dma-channel-secondary: The dma channel specifier for secondary tx
> + operations. The format of the dma specifier depends on the dma
> + controller.
> +- tx-dma-channel: The dma channel specifier for tx operations. The format of
> + the dma specifier depends on the dma controller.
> +- rx-dma-channel: The dma channel specifier for rx operations. The format of
> + the dma specifier depends on the dma controller.
> +
> +Optional SoC Specific Properties:
> +
> +- samsung,supports-6ch: If the I2S Primary sound source has 5.1 Channel
> + support, this flag is enabled.
> +- samsung,supports-rstclr: This flag should be set if I2S software reset bit
> + control is required. When this flag is set I2S software reset bit will be
> + enabled or disabled based on need.
> +- samsung,supports-secdai:If I2S block has a secondary FIFO and internal DMA,
> + then this flag is enabled.
> +- samsung,idma-addr: Internal DMA register base address of the audio
> + sub system(used in secondary sound source).
> +
> +Required Board Specific Properties:
> +
> +- gpios: The gpio specifier for data out,data in, LRCLK, CDCLK and SCLK
> + interface lines. The format of the gpio specifier depends on the gpio
> + controller.
> + The syntax of samsung gpio specifier is
> + <[phandle of the gpio controller node]
> + [pin number within the gpio controller]
> + [mux function]
> + [flags and pull up/down]
> + [drive strength]>
> +
> +Aliases:
> +
> +- All the I2S controller nodes are represented in the aliases node using
> + the following format 'i2s{n}' where n is a unique number for the alias.
Are the aliases actually being used now? If not, then drop this section.
I don't see any references in this patch.
Otherwise the binding looks good to me.
g.
next prev parent reply other threads:[~2012-12-19 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 10:42 [PATCH V5 0/2] Add DT support for i2s Padmavathi Venna
2012-12-13 10:42 ` [PATCH V5 1/2] ASoC: Samsung: Rename samsung i2s secondary device name Padmavathi Venna
2012-12-13 10:42 ` [PATCH V5 2/2] ASoC: SAMSUNG: Add DT support for i2s Padmavathi Venna
2012-12-19 13:24 ` Grant Likely [this message]
2012-12-19 17:09 ` Mark Brown
2012-12-19 17:37 ` Kukjin Kim
2012-12-21 11:36 ` Padma Venkat
2012-12-21 19:02 ` Kukjin Kim
2012-12-24 4:03 ` Padma Venkat
2012-12-26 10:51 ` Padma Venkat
2012-12-27 16:48 ` Mark Brown
2012-12-23 23:13 ` Kukjin Kim
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=20121219132414.2CF653E0AD7@localhost \
--to=grant.likely@secretlab.ca \
--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).