From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Codrin Ciubotariu <codrin.ciubotariu@microchip.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: lars@metafoo.de, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, robh+dt@kernel.org, nicolas.ferre@microchip.com
Subject: Re: [PATCH v2 2/6] ASoC: dt-bindings: Document Microchip's PDMC
Date: Mon, 7 Mar 2022 12:18:24 +0100 [thread overview]
Message-ID: <73c49f2b-ef2e-5ed8-f3d5-aa696f9af9e6@canonical.com> (raw)
In-Reply-To: <20220307100428.2227511-3-codrin.ciubotariu@microchip.com>
On 07/03/2022 11:04, Codrin Ciubotariu wrote:
> Add DT bindings for the new Microchip PDMC embedded in sama7g5 SoCs.
>
> Signed-off-by: Codrin Ciubotariu <codrin.ciubotariu@microchip.com>
> ---
>
> Changes in v2:
> - renamed patch from 'ASoC: add DT bindings for Microchip PDMC' to
> 'ASoC: dt-bindings: Document Microchip's PDMC';
> - renamed yaml file from 'mchp,pdmc.yaml' to 'microchip,pdmc.yaml';
> - used imperative mode in commit description;
> - renamed mchp,pdmc.h to microchip,pdmc.h;
> - fixed 'title' to represent HW;
> - made 'compatible' first property;
> - s/microhpone/microphone;
> - none name in example set to 'sound';
>
> .../bindings/sound/microchip,pdmc.yaml | 99 +++++++++++++++++++
> include/dt-bindings/sound/microchip,pdmc.h | 13 +++
> 2 files changed, 112 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sound/microchip,pdmc.yaml
> create mode 100644 include/dt-bindings/sound/microchip,pdmc.h
>
> diff --git a/Documentation/devicetree/bindings/sound/microchip,pdmc.yaml b/Documentation/devicetree/bindings/sound/microchip,pdmc.yaml
> new file mode 100644
> index 000000000000..edfa3cbd318e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/microchip,pdmc.yaml
> @@ -0,0 +1,99 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/sound/microchip,pdmc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Microchip Pulse Density Microphone Controller
> +
> +maintainers:
> + - Codrin Ciubotariu <codrin.ciubotariu@microchip.com>
> +
> +description:
> + The Microchip Pulse Density Microphone Controller (PDMC) interfaces up to 4 digital microphones
> + having Pulse Density Modulated (PDM) outputs.
This exceeds 80 characters.
> +
> +properties:
> + compatible:
> + const: microchip,sama7g5-pdmc
> +
> + "#sound-dai-cells":
> + const: 0
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: Peripheral Bus Clock
> + - description: Generic Clock
> +
> + clock-names:
> + items:
> + - const: pclk
> + - const: gclk
> +
> + dmas:
> + description: RX DMA Channel
> + maxItems: 1
> +
> + dma-names:
> + const: rx
> +
> + microchip,mic-pos:
> + description: |
> + Position of PDM microphones on the DS line and the sampling edge (rising or falling) of the
> + CLK line. A microphone is represented as a pair of DS line and the sampling edge. The first
> + microphone is mapped to channel 0, the second to channel 1, etc.
This is also too long, wrap at 80.
> + $ref: /schemas/types.yaml#/definitions/uint32-matrix
> + items:
> + items:
> + - description: value for DS line
> + - description: value for sampling edge
> + anyOf:
> + - enum:
> + - [0, 0]
> + - [0, 1]
> + - [1, 0]
> + - [1, 1]
> + minItems: 1
> + maxItems: 4
> + uniqueItems: true
> +
> +required:
> + - compatible
> + - "#sound-dai-cells"
> + - reg
> + - interrupts
> + - clocks
> + - clock-names
> + - dmas
> + - dma-names
> + - microchip,mic-pos
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/at91.h>
> + #include <dt-bindings/dma/at91.h>
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/sound/microchip,pdmc.h>
> +
> + pdmc: sound@e1608000 {
> + compatible = "microchip,sama7g5-pdmc";
> + #sound-dai-cells = <0>;
> + reg = <0xe1608000 0x4000>;
In DTS sources: compatible then reg. I mentioned it in previous version.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-03-07 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 10:04 [PATCH v2 0/6] Add driver for SAMA7G5's PDMC Codrin Ciubotariu
2022-03-07 10:04 ` [PATCH v2 1/6] ASoC: dmaengine: do not use a NULL prepare_slave_config() callback Codrin Ciubotariu
2022-03-07 10:04 ` [PATCH v2 2/6] ASoC: dt-bindings: Document Microchip's PDMC Codrin Ciubotariu
2022-03-07 11:18 ` Krzysztof Kozlowski [this message]
2022-03-07 11:34 ` Codrin.Ciubotariu
2022-03-07 11:44 ` Krzysztof Kozlowski
2022-03-07 10:04 ` [PATCH v2 3/6] ASoC: atmel: mchp-pdmc: add PDMC driver Codrin Ciubotariu
2022-03-07 10:04 ` [PATCH v2 4/6] ARM: dts: at91: sama7g5: add nodes for PDMC Codrin Ciubotariu
2022-03-07 10:04 ` [PATCH v2 5/6] ARM: dts: at91: sama7g5ek: add node for PDMC0 Codrin Ciubotariu
2022-03-07 10:04 ` [PATCH v2 6/6] ARM: configs: at91: sama7_defconfig: add MCHP PDMC and DMIC drivers Codrin Ciubotariu
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=73c49f2b-ef2e-5ed8-f3d5-aa696f9af9e6@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=codrin.ciubotariu@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®