From: Rob Herring <robh@kernel.org>
To: "József Horváth" <info@ministro.hu>
Cc: 'Greg Kroah-Hartman' <gregkh@linuxfoundation.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@driverdev.osuosl.org
Subject: Re: [PATCH v1 2/2] Staging: silabs si4455 serial driver: docs device tree binding
Date: Thu, 10 Dec 2020 21:01:01 -0600 [thread overview]
Message-ID: <20201211030101.GA3530369@robh.at.kernel.org> (raw)
In-Reply-To: <20201210122154.GA31799@dincontrollerdev>
On Thu, Dec 10, 2020 at 12:21:56PM +0000, József Horváth wrote:
> add: device tree binding schema
For the subject, follow conventions of the directory. Something like:
dt-bindings: serial: Add SiLabs SI4455 schema
> Signed-off-by: József Horváth <info@ministro.hu>
> ---
> .../bindings/serial/silabs,si4455.yaml | 53 +++++++++++++++++++
> MAINTAINERS | 2 +-
> 2 files changed, 54 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/serial/silabs,si4455.yaml
>
> diff --git a/Documentation/devicetree/bindings/serial/silabs,si4455.yaml b/Documentation/devicetree/bindings/serial/silabs,si4455.yaml
> new file mode 100644
> index 000000000000..80a73a61755b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/serial/silabs,si4455.yaml
> @@ -0,0 +1,53 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/serial/silabs,si4455.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Silicon Labs Si4455 device tree bindings
Add 'description' with some info on this h/w and possibly a link to
datasheet if available.
> +
> +maintainers:
> + - József Horváth <info@ministro.hu>
> +
> +allOf:
> + - $ref: "/schemas/serial.yaml#"
> +
> +properties:
> + compatible:
> + const: silabs,si4455
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + spi-max-frequency:
> + description: maximum clock frequency on SPI port
> + maximum: 500000
> +
> + shutdown-gpios:
> + description: gpio pin for SDN
> + maxItems: 1
> +
> +required:
> + - reg
> + - interrupts
> + - spi-max-frequency
> + - shutdown-gpios
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + &spi0 {
> + serial0: si4455@0 {
> + compatible = "silabs,si4455";
> + reg = <0>;
> + interrupt-parent = <&gpio>;
> + interrupts = <7 IRQ_TYPE_LEVEL_LOW>;
> + shutdown-gpios = <&gpio 26 1>;
> + spi-max-frequency = <300000>;
> + };
> + };
> +...
> diff --git a/MAINTAINERS b/MAINTAINERS
> index a29bc17d446d..16cc96971ac2 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15937,7 +15937,7 @@ F: drivers/platform/x86/touchscreen_dmi.c
> SILICON LABS SI4455 SERIAL DRIVER
> M: József Horváth <info@ministro.hu>
> S: Maintained
> -F: Documentation/devicetree/bindings/staging/serial/silabs,si4455.txt
This is a new file, right?
> +F: Documentation/devicetree/bindings/serial/silabs,si4455.yaml
> F: drivers/tty/serial/si4455.c
> F: drivers/tty/serial/si4455_api.h
>
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-12-11 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 12:21 [PATCH v1 2/2] Staging: silabs si4455 serial driver: docs device tree binding József Horváth
2020-12-11 3:01 ` Rob Herring [this message]
2020-12-11 3:02 ` 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=20201211030101.GA3530369@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=info@ministro.hu \
--cc=linux-kernel@vger.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).