linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/6] [RFC] Documentation: dt: Add Renesas RSPI/QSPI bindings
Date: Fri, 27 Dec 2013 16:18:07 +0000	[thread overview]
Message-ID: <2590710.91Xybr4TsD@avalon> (raw)
In-Reply-To: <1387886210-3634-5-git-send-email-geert+renesas@linux-m68k.org>

Hi Geert,

Thank you for the patch. It's nice to see DT support for the RSPI driver.

On Tuesday 24 December 2013 12:56:48 Geert Uytterhoeven wrote:
> Signed-off-by: Geert Uytterhoeven <geert+renesas@linux-m68k.org>
> Cc: devicetree@vger.kernel.org
> ---
>  Documentation/devicetree/bindings/spi/spi-rspi.txt |   27 +++++++++++++++++
>  1 file changed, 27 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/spi/spi-rspi.txt
> 
> diff --git a/Documentation/devicetree/bindings/spi/spi-rspi.txt
> b/Documentation/devicetree/bindings/spi/spi-rspi.txt new file mode 100644
> index 000000000000..06ec17fce4c6
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/spi/spi-rspi.txt
> @@ -0,0 +1,27 @@
> +Device tree configuration for Renesas RSPI/QSPI driver
> +
> +Required properties:
> +- compatible      : "renesas,rspi-<soctype>". "renesas,rspi-rz" as
> fallback,
> +                    or
> +                    "renesas,qspi-<soctype>", "renesas,qspi-rcar" as
> fallback.

I think you need to be a bit more verbose here and explain when to use rspi 
and when to use qspi. I'm also wondering where we need the -rz and -rcar 
suffixes for the generic compatible strings.

> +- reg             : address start and address range size of device
> +- interrupts      : 3 interrupts for RSPI (SPEI, SPRI, SPTI),
> +                    1 interrupt for QSPI
> +- num-cs	  : Number of chip selects
> +- #address-cells  : should be <1>
> +- #size-cells     : should be <0>

I would say "must" instead of "should".

> +
> +Pinctrl properties might be needed, too. See there.
> +
> +Example:
> +
> +	spi0: spi@e800c800 {
> +		compatible = "renesas,rspi-r7s72100", "renesas,rspi-rz";
> +		reg = <0xe800c800 0x24>;
> +		interrupts = <0 238 IRQ_TYPE_LEVEL_HIGH>,
> +			     <0 239 IRQ_TYPE_LEVEL_HIGH>,
> +			     <0 240 IRQ_TYPE_LEVEL_HIGH>;

You're missing the interrupt-parent property.

Now that we have two ways to specify interrupts (interrupt-parent + interrupts 
or interrupts-extended) we should probably decide on a common wording for 
interrupt properties in individual DT bindings, but that's out of scope of 
this patch.

> +		num-cs = <1>;
> +		#address-cells = <1>;
> +		#size-cells = <0>;
> +	};

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2013-12-27 16:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-24 11:56 [PATCH 0/6] Preliminary SoC and board integration for RSPI on RZ/A1H Geert Uytterhoeven
2013-12-24 11:56 ` [PATCH 1/6] pinctrl: sh-pfc: r7s72100: Add RSPI support Geert Uytterhoeven
2014-01-07 19:03   ` Linus Walleij
2014-01-07 19:07     ` Geert Uytterhoeven
2013-12-24 11:56 ` [PATCH 2/6] ARM: shmobile: r7s72100: Add RSPI clocks Geert Uytterhoeven
2013-12-25  0:51   ` Kuninori Morimoto
2013-12-24 11:56 ` [PATCH 3/6] ARM: shmobile: r7s72100: Add RSPI resources Geert Uytterhoeven
2013-12-24 15:41   ` Sergei Shtylyov
2013-12-24 11:56 ` [PATCH 4/6] [RFC] Documentation: dt: Add Renesas RSPI/QSPI bindings Geert Uytterhoeven
2013-12-27 16:18   ` Laurent Pinchart [this message]
2013-12-27 19:01     ` Geert Uytterhoeven
2013-12-29 23:22       ` Laurent Pinchart
2013-12-30  9:37         ` Geert Uytterhoeven
2013-12-30 15:18           ` Laurent Pinchart
2013-12-30 17:20             ` Geert Uytterhoeven
2013-12-24 11:56 ` [PATCH 5/6] [RFC] ARM: shmobile: r7s72100 dtsi: Add RSPI nodes Geert Uytterhoeven
2013-12-24 11:56 ` [PATCH 6/6] [RFC] arm: shmobile: genmai reference: " Geert Uytterhoeven
2013-12-24 15:45   ` Sergei Shtylyov
2013-12-24 19:46     ` Geert Uytterhoeven
2013-12-27 16:20   ` Laurent Pinchart
2013-12-27 19:08     ` Geert Uytterhoeven
2013-12-28 11:48       ` Laurent Pinchart

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=2590710.91Xybr4TsD@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.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).