From: Michal Simek <michal.simek@xilinx.com>
To: Piyush Mehta <piyush.mehta@xilinx.com>,
<linus.walleij@linaro.org>, <bgolaszewski@baylibre.com>,
<robh+dt@kernel.org>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>, <git@xilinx.com>,
<sgoud@xilinx.com>, <michal.simek@xilinx.com>
Subject: Re: [PATCH 1/2] dt-bindings: gpio: Add binding documentation for modepin
Date: Tue, 15 Jun 2021 12:28:06 +0200 [thread overview]
Message-ID: <d41f65d5-cb5d-4854-fb51-2808865d042c@xilinx.com> (raw)
In-Reply-To: <20210615080553.2021061-2-piyush.mehta@xilinx.com>
On 6/15/21 10:05 AM, Piyush Mehta wrote:
> Add DT binding document for modepin GPIO controller.
>
> Signed-off-by: Piyush Mehta <piyush.mehta@xilinx.com>
> State: pending
note: this shouldn't be the part of commit message.
But please wait when dt guys review this file and then send v2.
M
> ---
> .../bindings/gpio/xlnx,zynqmp-gpio-modepin.yaml | 41 ++++++++++++++++++++++
> 1 file changed, 41 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/gpio/xlnx,zynqmp-gpio-modepin.yaml
>
> diff --git a/Documentation/devicetree/bindings/gpio/xlnx,zynqmp-gpio-modepin.yaml b/Documentation/devicetree/bindings/gpio/xlnx,zynqmp-gpio-modepin.yaml
> new file mode 100644
> index 0000000..39d78f8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/gpio/xlnx,zynqmp-gpio-modepin.yaml
> @@ -0,0 +1,41 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/gpio/xlnx,zynqmp-gpio-modepin.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: ZynqMP Mode Pin GPIO controller
> +
> +description:
> + PS_MODE is 4-bits boot mode pins sampled on POR deassertion. Mode Pin
> + GPIO controller with configurable from numbers of pins (from 0 to 3 per
> + PS_MODE). Every pin can be configured as input/output.
> +
> +maintainers:
> + - Piyush Mehta <piyush.mehta@xilinx.com>
> +
> +properties:
> + compatible:
> + const: xlnx,zynqmp-gpio-modepin
> +
> + gpio-controller: true
> +
> + "#gpio-cells":
> + const: 2
> +
> +required:
> + - compatible
> + - gpio-controller
> + - "#gpio-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + modepin_gpio: gpio {
> + compatible = "xlnx,zynqmp-gpio-modepin";
> + gpio-controller;
> + #gpio-cells = <2>;
> + };
> +
> +...
>
next prev parent reply other threads:[~2021-06-15 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 8:05 [PATCH 0/2] gpio: modepin: Add driver support for modepin GPIO controller Piyush Mehta
2021-06-15 8:05 ` [PATCH 1/2] dt-bindings: gpio: Add binding documentation for modepin Piyush Mehta
2021-06-15 10:28 ` Michal Simek [this message]
2021-06-24 20:50 ` Rob Herring
2021-06-15 8:05 ` [PATCH 2/2] gpio: modepin: Add driver support for modepin GPIO controller Piyush Mehta
2021-06-18 9:43 ` Linus Walleij
2021-06-21 17:09 ` Piyush Mehta
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=d41f65d5-cb5d-4854-fb51-2808865d042c@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piyush.mehta@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=sgoud@xilinx.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®