All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: shubhrajyoti.datta@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
	arnd@arndb.de, michal.simek@xilinx.com,
	Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: misc: Add dt bindings for traffic generator
Date: Wed, 18 Dec 2019 17:55:41 -0600	[thread overview]
Message-ID: <20191218235541.GA31319@bogus> (raw)
In-Reply-To: <8b3a446fc60cdd7d085203ce00c3f6bfba642437.1575871828.git.shubhrajyoti.datta@xilinx.com>

On Mon, Dec 09, 2019 at 11:41:26AM +0530, shubhrajyoti.datta@gmail.com wrote:
> From: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>
> 
> Add dt bindings for xilinx traffic generator IP.
> 
> Signed-off-by: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>
> ---
>  .../bindings/misc/xlnx,axi-traffic-gen.txt         | 25 ++++++++++++++++++++++
>  1 file changed, 25 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/misc/xlnx,axi-traffic-gen.txt

Please convert to a DT schema.

> 
> diff --git a/Documentation/devicetree/bindings/misc/xlnx,axi-traffic-gen.txt b/Documentation/devicetree/bindings/misc/xlnx,axi-traffic-gen.txt
> new file mode 100644
> index 0000000..6edb8f6
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/misc/xlnx,axi-traffic-gen.txt
> @@ -0,0 +1,25 @@
> +* Xilinx AXI Traffic generator IP
> +
> +Required properties:
> +- compatible: "xlnx,axi-traffic-gen"
> +- interrupts: Should contain AXI Traffic Generator interrupts.

How many and what are they.

> +- interrupt-parent: Must be core interrupt controller.

Drop this. It could be in a parent node.

> +- reg: Should contain AXI Traffic Generator registers location and length.
> +- interrupt-names: Should contain both the intr names of device - error
> +		   and completion.

Needs exact strings.

> +- xlnx,device-id: Device instance Id.
> +
> +Optional properties:
> +- clocks: Input clock specifier. Refer to common clock bindings.
> +
> +Example:
> +++++++++
> +axi_traffic_gen_1: axi-traffic-gen@76000000 {
> +	compatible = "xlnx,axi-traffic-gen-1.0", "xlnx,axi-traffic-gen";

Doesn't match the above. I'd drop the 2nd string.

> +	clocks = <&clkc 15>;
> +	interrupts = <0 2 2 2>;
> +	interrupt-parent = <&axi_intc_1>;
> +	interrupt-names = "err-out", "irq-out";
> +	reg = <0x76000000 0x800000>;
> +	xlnx,device-id = <0x0>;
> +} ;
> -- 
> 2.1.1
> 

      parent reply	other threads:[~2019-12-18 23:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09  6:11 [PATCH v2 1/3] dt-bindings: misc: Add dt bindings for traffic generator shubhrajyoti.datta
2019-12-09  6:11 ` [PATCH v2 2/3] trafgen: xilinx: add axi traffic generator driver shubhrajyoti.datta
2019-12-09  8:06   ` Greg KH
2019-12-09  6:11 ` [PATCH v2 3/3] trafgen: Document sysfs entries shubhrajyoti.datta
2019-12-09  8:07 ` [PATCH v2 1/3] dt-bindings: misc: Add dt bindings for traffic generator Greg KH
2019-12-18 23:55 ` Rob Herring [this message]

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=20191218235541.GA31319@bogus \
    --to=robh@kernel.org \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=shubhrajyoti.datta@gmail.com \
    --cc=shubhrajyoti.datta@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.