From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Julien Panis <jpanis@baylibre.com>,
jic23@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org
Cc: lars@metafoo.de, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
mranostay@ti.com
Subject: Re: [PATCH v1 2/2] dt-binding: iio: time: add capture-tiecap.yaml
Date: Tue, 26 Jul 2022 11:29:18 +0200 [thread overview]
Message-ID: <c4e8b285-1e77-492e-31d7-8c79328b95dd@linaro.org> (raw)
In-Reply-To: <20220726072553.5136-3-jpanis@baylibre.com>
On 26/07/2022 09:25, Julien Panis wrote:
> This commit adds a YAML binding for TI ECAP used in capture operating mode.
>
> Signed-off-by: Julien Panis <jpanis@baylibre.com>
> ---
> .../bindings/iio/time/capture-tiecap.yaml | 53 +++++++++++++++++++
> 1 file changed, 53 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/time/capture-tiecap.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/time/capture-tiecap.yaml b/Documentation/devicetree/bindings/iio/time/capture-tiecap.yaml
> new file mode 100644
> index 000000000000..4f08e49a8506
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/time/capture-tiecap.yaml
Use filename based on compatible, so:
ti,am62-ecap-capture.yaml
> @@ -0,0 +1,53 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/capture-tiecap.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Texas Instruments Enhanced Capture (eCAP) Module
> +
> +maintainers:
> + - Julien Panis <jpanis@baylibre.com>
> +
> +description: |
> + The eCAP module resources can be used to capture timestamps
> + on input signal events (falling/rising edges).
> +
> +properties:
> + compatible:
> + const: ti,am62-ecap-capture
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + clock-names:
> + const: fck
> +
> + power-domains:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> + - clock-names
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + ecap0: capture@23100000 { /* eCAP in capture mode on am62x */
> + compatible = "ti,am62-ecap-capture";
> + reg = <0x00 0x23100000 0x00 0x100>;
> + interrupts = <GIC_SPI 113 IRQ_TYPE_EDGE_RISING>;
> + power-domains = <&k3_pds 51 TI_SCI_PD_EXCLUSIVE>;
Does not look like you tested the bindings. Please run `make
dt_binding_check` (see
Documentation/devicetree/bindings/writing-schema.rst for instructions).
> + clocks = <&k3_clks 51 0>;
> + clock-names = "fck";
> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-07-26 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 7:25 [PATCH v1 0/2] ECAP support on TI AM62x SoC Julien Panis
2022-07-26 7:25 ` [PATCH v1 1/2] iio: time: capture-tiecap: capture driver support for ECAP Julien Panis
2022-07-26 7:25 ` [PATCH v1 2/2] dt-binding: iio: time: add capture-tiecap.yaml Julien Panis
2022-07-26 9:29 ` Krzysztof Kozlowski [this message]
2022-07-26 9:42 ` Julien Panis
2022-07-26 13:51 ` Rob Herring
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=c4e8b285-1e77-492e-31d7-8c79328b95dd@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=jpanis@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mranostay@ti.com \
--cc=robh+dt@kernel.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).