From: Maxime Ripard <maxime@cerno.tech>
To: Ban Tao <fengzheng923@gmail.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
wens@csie.org, jernej.skrabec@gmail.com,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ASoC: sun50i-dmic: dt-bindings: add DT bindings for DMIC controller
Date: Wed, 16 Jun 2021 10:49:20 +0200 [thread overview]
Message-ID: <20210616084920.y6yjic4sau6ungv5@gilmour> (raw)
In-Reply-To: <20210615130737.2098-1-fengzheng923@gmail.com>
Hi,
On Tue, Jun 15, 2021 at 09:07:37PM +0800, Ban Tao wrote:
> The Allwinner SoCs feature an I2S controller across multiple SoC
> generations.
Which SoC generations?
> Signed-off-by: Ban Tao <fengzheng923@gmail.com>
> ---
> .../sound/allwinner,sun50i-h6-dmic.yaml | 66 +++++++++++++++++++
> 1 file changed, 66 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sound/allwinner,sun50i-h6-dmic.yaml
>
> diff --git a/Documentation/devicetree/bindings/sound/allwinner,sun50i-h6-dmic.yaml b/Documentation/devicetree/bindings/sound/allwinner,sun50i-h6-dmic.yaml
> new file mode 100644
> index 000000000000..81d40c374e44
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/allwinner,sun50i-h6-dmic.yaml
> @@ -0,0 +1,66 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/sound/allwinner,sun50i-h6-dmic.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Allwinner H6 DMIC Controller Device Tree Bindings
> +
> +maintainers:
> + - Ban Tao <fengzheng923@gmail.com>
> +
> +properties:
> + "#sound-dai-cells":
> + const: 0
> +
> + compatible:
> + const: allwinner,sun50i-h6-dmic
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: Bus Clock
> + - description: Module Clock
> +
> + clock-names:
> + items:
> + - const: apb
> + - const: dmic
The convention we use is bus and mod
> +
> + dmas:
> + maxItems: 1
> +
> + dma-names:
> + const: rx
> +
> + resets:
> + maxItems: 1
> +
> +required:
> + - "#sound-dai-cells"
> + - compatible
> + - reg
> + - clocks
> + - clock-names
> + - dmas
> + - dma-names
> + - resets
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + spdif: spdif@5095000 {
The label and node name seems wrong?
> + #sound-dai-cells = <0>;
> + compatible = "allwinner,sun50i-h6-dmic";
> + reg = <0x05095000 0x400>;
> + clocks = <&ccu CLK_BUS_DMIC>, <&ccu CLK_DMIC>;
You'll need includes for it to compile
Maxime
next prev parent reply other threads:[~2021-06-16 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 13:07 [PATCH 2/2] ASoC: sun50i-dmic: dt-bindings: add DT bindings for DMIC controller Ban Tao
2021-06-15 22:37 ` Rob Herring
2021-06-16 8:49 ` Maxime Ripard [this message]
2021-06-16 10:56 ` 班涛
2021-06-16 12:38 ` Maxime Ripard
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=20210616084920.y6yjic4sau6ungv5@gilmour \
--to=maxime@cerno.tech \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fengzheng923@gmail.com \
--cc=jernej.skrabec@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).