From: Rob Herring <robh@kernel.org>
To: Viktor Prutyanov <viktor.prutyanov@phystech.edu>
Cc: sean@mess.org, mchehab@kernel.org, khilman@baylibre.com,
narmstrong@baylibre.com, jbrunet@baylibre.com,
martin.blumenstingl@googlemail.com, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, rockosov@gmail.com
Subject: Re: [PATCH v3 1/2] media: rc: meson-irblaster: document device tree bindings
Date: Wed, 14 Jul 2021 17:23:03 -0600 [thread overview]
Message-ID: <20210714232303.GA3730974@robh.at.kernel.org> (raw)
In-Reply-To: <20210709165753.29353-2-viktor.prutyanov@phystech.edu>
On Fri, Jul 09, 2021 at 07:57:52PM +0300, Viktor Prutyanov wrote:
> This patch adds binding documentation for the IR transmitter
> available in Amlogic Meson SoCs.
>
> Signed-off-by: Viktor Prutyanov <viktor.prutyanov@phystech.edu>
> ---
> changes in v2:
> - compatible = "amlogic,meson-g12a-irblaster" added
> - clocks, clock-names and mod-clock updated
> changes in v3:
> - mod-clock removed
> - max-fifo-level added
>
> .../media/amlogic,meson-irblaster.yaml | 65 +++++++++++++++++++
> 1 file changed, 65 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/amlogic,meson-irblaster.yaml
>
> diff --git a/Documentation/devicetree/bindings/media/amlogic,meson-irblaster.yaml b/Documentation/devicetree/bindings/media/amlogic,meson-irblaster.yaml
> new file mode 100644
> index 000000000000..1e10aa0d3a94
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/amlogic,meson-irblaster.yaml
> @@ -0,0 +1,65 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/media/amlogic,meson-irblaster.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Amlogic Meson IR blaster
> +
> +maintainers:
> + - Viktor Prutyanov <viktor.prutyanov@phystech.edu>
> +
> +description: |
> + Some Amlogic SoCs such as A311D and T950D4 have IR transmitter
> + (blaster) controller onboard. It is capable of sending IR signals
> + with arbitrary carrier frequency and duty cycle.
> +
> +properties:
> + compatible:
> + oneOf:
> + - const: amlogic,meson-irblaster
> + - items:
> + - const: amlogic,meson-g12a-irblaster
> + - const: amlogic,meson-irblaster
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 2
> +
> + clock-names:
> + items:
> + - const: sysclk
> + - const: xtal
> +
> + max-fifo-level:
> + maxItems: 1
An array?
Needs a vendor prefix, type reference and constraints on allowed values.
> + description:
> + Maximum IR blaster FIFO fill level
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> + - clock-names
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> + #include <dt-bindings/clock/g12a-clkc.h>
> +
> + irblaster@ff80014c {
> + compatible = "amlogic,meson-g12a-irblaster", "amlogic,meson-irblaster";
> + reg = <0xff80014c 0x10>;
> + interrupts = <0 198 IRQ_TYPE_EDGE_RISING>;
> + clocks = <&clkc CLKID_CLK81>, <&xtal>;
> + clock-names = "sysclk", "xtal";
> + };
> --
> 2.21.0
>
>
next prev parent reply other threads:[~2021-07-14 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 16:57 [PATCH v3 0/2] media: rc: add support for Amlogic Meson IR blaster Viktor Prutyanov
2021-07-09 16:57 ` [PATCH v3 1/2] media: rc: meson-irblaster: document device tree bindings Viktor Prutyanov
2021-07-14 23:23 ` Rob Herring [this message]
2021-07-09 16:57 ` [PATCH v3 2/2] media: rc: introduce Meson IR blaster driver Viktor Prutyanov
2021-07-09 21:32 ` kernel test robot
2021-07-09 22:11 ` Sean Young
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=20210714232303.GA3730974@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mchehab@kernel.org \
--cc=narmstrong@baylibre.com \
--cc=rockosov@gmail.com \
--cc=sean@mess.org \
--cc=viktor.prutyanov@phystech.edu \
/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).