From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, robh+dt@kernel.org,
jassisinghbrar@gmail.com, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org
Subject: Re: [RFCv2 1/9] dt-bindings: mailbox: meson-mhu: convert to yaml
Date: Wed, 7 Aug 2019 16:34:31 +0200 [thread overview]
Message-ID: <20190807143431.6w6dg44mjiwtffi2@flea> (raw)
In-Reply-To: <20190805120320.32282-2-narmstrong@baylibre.com>
Hi,
On Mon, Aug 05, 2019 at 02:03:12PM +0200, Neil Armstrong wrote:
> Now that we have the DT validation in place, let's convert the device tree
> bindings for the Amlogic MHU controller over to a YAML schemas.
>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
> ---
> .../mailbox/amlogic,meson-gxbb-mhu.yaml | 53 +++++++++++++++++++
> .../devicetree/bindings/mailbox/meson-mhu.txt | 34 ------------
> 2 files changed, 53 insertions(+), 34 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/mailbox/amlogic,meson-gxbb-mhu.yaml
> delete mode 100644 Documentation/devicetree/bindings/mailbox/meson-mhu.txt
>
> diff --git a/Documentation/devicetree/bindings/mailbox/amlogic,meson-gxbb-mhu.yaml b/Documentation/devicetree/bindings/mailbox/amlogic,meson-gxbb-mhu.yaml
> new file mode 100644
> index 000000000000..2536a0082cff
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mailbox/amlogic,meson-gxbb-mhu.yaml
> @@ -0,0 +1,53 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +# Copyright 2019 BayLibre, SAS
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/mailbox/amlogic,meson-gxbb-mhu.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Amlogic Meson Message-Handling-Unit Controller
> +
> +maintainers:
> + - Neil Armstrong <narmstrong@baylibre.com>
> +
> +description: |
> + The Amlogic's Meson SoCs Message-Handling-Unit (MHU) is a mailbox controller
> + that has 3 independent channels/links to communicate with remote processor(s).
> + MHU links are hardwired on a platform. A link raises interrupt for any
> + received data. However, there is no specified way of knowing if the sent
> + data has been read by the remote. This driver assumes the sender polls
> + STAT register and the remote clears it after having read the data.
> +
> +properties:
> + compatible:
> + enum:
> + - amlogic,meson-gxbb-mhu
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + minItems: 3
> + maxItems: 3
You don't need to specify both here. If one is missing, the tools will
fill it automatically with the other's value.
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-07 14:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 12:03 [RFCv2 0/9] dt-bindings: first tentative of conversion to yaml format Neil Armstrong
2019-08-05 12:03 ` [RFCv2 1/9] dt-bindings: mailbox: meson-mhu: convert to yaml Neil Armstrong
2019-08-07 14:34 ` Maxime Ripard [this message]
2019-08-05 12:03 ` [RFCv2 2/9] dt-bindings: rng: amlogic,meson-rng: " Neil Armstrong
2019-08-06 19:19 ` Martin Blumenstingl
2019-08-05 12:03 ` [RFCv2 3/9] dt-bindings: spi: meson: " Neil Armstrong
2019-08-05 21:45 ` Rob Herring
2019-08-05 12:03 ` [RFCv2 4/9] dt-bindings: reset: amlogic,meson-reset: " Neil Armstrong
2019-08-06 7:41 ` Philipp Zabel
2019-08-06 19:12 ` [RFCv2 4/9] dt-bindings: reset: amlogic, meson-reset: " Martin Blumenstingl
2019-08-05 12:03 ` [RFCv2 5/9] dt-bindings: arm: amlogic: amlogic, meson-gx-ao-secure: " Neil Armstrong
2019-08-05 12:03 ` [RFCv2 6/9] dt-bindings: phy: meson-g12a-usb2-phy: " Neil Armstrong
2019-08-06 19:21 ` Martin Blumenstingl
2019-08-05 12:03 ` [RFCv2 7/9] dt-bindings: phy: meson-g12a-usb3-pcie-phy: " Neil Armstrong
2019-08-05 12:03 ` [RFCv2 8/9] dt-bindings: serial: meson-uart: " Neil Armstrong
2019-08-06 19:18 ` Martin Blumenstingl
2019-08-05 12:03 ` [RFCv2 9/9] dt-bindings: watchdog: meson-gxbb-wdt: " Neil Armstrong
2019-08-07 17:59 ` Guenter Roeck
2019-08-05 21:51 ` [RFCv2 0/9] dt-bindings: first tentative of conversion to yaml format Rob Herring
2019-08-06 7:42 ` Neil Armstrong
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=20190807143431.6w6dg44mjiwtffi2@flea \
--to=maxime.ripard@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=narmstrong@baylibre.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).