From: Rob Herring <robh@kernel.org>
To: jassisinghbrar@gmail.com
Cc: balbi@kernel.org, gregkh@linuxfoundation.org,
mark.rutland@arm.com, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Jassi Brar <jaswinder.singh@linaro.org>
Subject: Re: [PATCHv1 1/2] dt-bindings: max3421-udc: add dt bindings for MAX3420 UDC
Date: Thu, 19 Dec 2019 13:40:00 -0600 [thread overview]
Message-ID: <20191219194000.GA23698@bogus> (raw)
In-Reply-To: <20191210003124.32376-1-jassisinghbrar@gmail.com>
On Mon, Dec 09, 2019 at 06:31:24PM -0600, jassisinghbrar@gmail.com wrote:
> From: Jassi Brar <jaswinder.singh@linaro.org>
>
> Add YAML dt bindings for Maxim MAX3420 UDC controller.
>
> Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
> ---
> .../bindings/usb/maxim,max3420-udc.yaml | 60 +++++++++++++++++++
> 1 file changed, 60 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/usb/maxim,max3420-udc.yaml
>
> diff --git a/Documentation/devicetree/bindings/usb/maxim,max3420-udc.yaml b/Documentation/devicetree/bindings/usb/maxim,max3420-udc.yaml
> new file mode 100644
> index 000000000000..cf4eec8a618e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/maxim,max3420-udc.yaml
> @@ -0,0 +1,60 @@
> +# SPDX-License-Identifier: GPL-2.0-only
Dual license new bindings please:
(GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/usb/maxim,max3420-udc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MAXIM MAX3420/1 USB Peripheral Controller
> +
> +maintainers:
> + - Jassi Brar <jaswinder.singh@linaro.org>
> +
> +description: |
> + The controller provices USB2.0 compliant FullSpeed peripheral
> + implementation over the SPI interface.
space ^
> +
> + Specifications about the part can be found at:
> + http://datasheets.maximintegrated.com/en/ds/MAX3420E.pdf
> +
> +properties:
> + compatible:
> + enum:
> + - maxim,max3420-udc
> + - maxim,max3421-udc
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + minItems: 1
> + maxItems: 2
> + items:
> + - const: udc
> + - const: vbus
interrupts are integers, not strings. Should be interrupt-names?
> +
> + spi-max-frequency:
> + maximum: 26000000
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - interrupt-names
Add:
additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> + spi0 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + udc@0 {
> + compatible = "maxim,max3420-udc";
> + reg = <0>;
> + interrupt-parent = <&gpio>;
> + interrupts = <0 IRQ_TYPE_EDGE_FALLING>, <10 IRQ_TYPE_EDGE_BOTH>;
> + interrupt-names = "udc", "vbus";
> + spi-max-frequency = <12500000>;
> + };
> + };
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-12-19 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 0:31 [PATCHv1 1/2] dt-bindings: max3421-udc: add dt bindings for MAX3420 UDC jassisinghbrar
2019-12-19 19:40 ` Rob Herring [this message]
2019-12-23 21:44 ` Jassi Brar
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=20191219194000.GA23698@bogus \
--to=robh@kernel.org \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jassisinghbrar@gmail.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.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;
as well as URLs for NNTP newsgroup(s).