From: Kumar Gala <galak@codeaurora.org> To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> Cc: linux-sh@vger.kernel.org, linux-serial@vger.kernel.org, Bastian Hecht <hechtb+renesas@gmail.com>, Paul Mundt <lethal@linux-sh.org>, devicetree@vger.kernel.org Subject: Re: [PATCH 5/5] serial: sh-sci: Add device tree bindings documentation Date: Thu, 31 Oct 2013 14:42:48 +0000 [thread overview] Message-ID: <9B7DF883-D119-47F5-BD71-11E30BE3DB88@codeaurora.org> (raw) In-Reply-To: <1383042599-25151-6-git-send-email-laurent.pinchart+renesas@ideasonboard.com> On Oct 29, 2013, at 5:29 AM, Laurent Pinchart wrote: > Document the device tree bindings for the sci serial port devices. > > Cc: devicetree@vger.kernel.org > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> > --- > .../bindings/serial/renesas,sci-serial.txt | 51 ++++++++++++++++++++++ > 1 file changed, 51 insertions(+) > create mode 100644 Documentation/devicetree/bindings/serial/renesas,sci-serial.txt > > diff --git a/Documentation/devicetree/bindings/serial/renesas,sci-serial.txt b/Documentation/devicetree/bindings/serial/renesas,sci-serial.txt > new file mode 100644 > index 0000000..5658b4f > --- /dev/null > +++ b/Documentation/devicetree/bindings/serial/renesas,sci-serial.txt > @@ -0,0 +1,51 @@ > +* Renesas SH-Mobile Serial Communication Interface > + > +Required properties: > + > + - compatible: should be one of the following. Being pedantic, but how about saying 'one of the following types (scif, scifa, scifb, or hscif) > + > + - "renesas,scif-r8a7790" for R8A7790 (R-Car H2) SCIF compatible UART. > + - "renesas,scifa-r8a7790" for R8A7790 (R-Car H2) SCIFA compatible UART. > + - "renesas,scifb-r8a7790" for R8A7790 (R-Car H2) SCIFB compatible UART. > + - "renesas,hscif-r8a7790" for R8A7790 (R-Car H2) HSCIF compatible UART. > + - "renesas,scif-generic" for generic SCIF compatible UART. > + - "renesas,scifa-generic" for generic SCIFA compatible UART. > + - "renesas,scifb-generic" for generic SCIFB compatible UART. > + - "renesas,hscif-generic" for generic HSCIF compatible UART. > + > + When compatible with the generic version, nodes must also list the > + SoC-specific version corresponding to the platform. > + > + - reg: Base address and length of the memory resource used by the UART. > + > + - interrupt-parent: Reference to the parent interrupt controller. > + - interrupts: Interrupt number(s). Depending on the SoC SCIx UARTs are tied > + to one or multiple interrupt lines. When using multiple interrupt lines, > + specify the interrupt names as described below. > + > + - clocks: Reference to the SCIx UART interface clock. > + - clock-names: Should be "sci_ick". > + > +Optional properties: > + > + - interrupt-names: When using multiple interrupts, report the interrupt > + names as "eri" (receive error), "rxi" (receive), "txi" (transmit) and > + "bri" (break). When using a single interrupt this property should not be > + present. Hmm, is there a reason not to just have the 4 interrupts always present and in the case they are all wired to the same interrupt, just have the interrupts all be the same? example: interrupts = <0 144 4>, <0 144 4>, <0 144 4>, <0 144 4>; > + > +Note: Each enabled SCIx UART should have an alias correctly numbered in the > +"aliases" node. > + > +Example: > + aliases { > + serial0 = &scifa0; > + }; > + > + scifa0: serial@e6c40000 { > + compatible = "renesas,scifa-r8a7790", "renesas,scifa-generic"; > + reg = <0 0xe6c40000 0 64>; > + interrupt-parent = <&gic>; > + interrupts = <0 144 4>; > + clocks = <&mstp2_clks 4>; > + clock-names = "sci_ick"; > + }; might be nice to have an example with the 4 interrupts. - k -- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: Kumar Gala <galak@codeaurora.org> To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> Cc: linux-sh@vger.kernel.org, linux-serial@vger.kernel.org, Bastian Hecht <hechtb+renesas@gmail.com>, Paul Mundt <lethal@linux-sh.org>, devicetree@vger.kernel.org Subject: Re: [PATCH 5/5] serial: sh-sci: Add device tree bindings documentation Date: Thu, 31 Oct 2013 09:42:48 -0500 [thread overview] Message-ID: <9B7DF883-D119-47F5-BD71-11E30BE3DB88@codeaurora.org> (raw) In-Reply-To: <1383042599-25151-6-git-send-email-laurent.pinchart+renesas@ideasonboard.com> On Oct 29, 2013, at 5:29 AM, Laurent Pinchart wrote: > Document the device tree bindings for the sci serial port devices. > > Cc: devicetree@vger.kernel.org > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> > --- > .../bindings/serial/renesas,sci-serial.txt | 51 ++++++++++++++++++++++ > 1 file changed, 51 insertions(+) > create mode 100644 Documentation/devicetree/bindings/serial/renesas,sci-serial.txt > > diff --git a/Documentation/devicetree/bindings/serial/renesas,sci-serial.txt b/Documentation/devicetree/bindings/serial/renesas,sci-serial.txt > new file mode 100644 > index 0000000..5658b4f > --- /dev/null > +++ b/Documentation/devicetree/bindings/serial/renesas,sci-serial.txt > @@ -0,0 +1,51 @@ > +* Renesas SH-Mobile Serial Communication Interface > + > +Required properties: > + > + - compatible: should be one of the following. Being pedantic, but how about saying 'one of the following types (scif, scifa, scifb, or hscif) > + > + - "renesas,scif-r8a7790" for R8A7790 (R-Car H2) SCIF compatible UART. > + - "renesas,scifa-r8a7790" for R8A7790 (R-Car H2) SCIFA compatible UART. > + - "renesas,scifb-r8a7790" for R8A7790 (R-Car H2) SCIFB compatible UART. > + - "renesas,hscif-r8a7790" for R8A7790 (R-Car H2) HSCIF compatible UART. > + - "renesas,scif-generic" for generic SCIF compatible UART. > + - "renesas,scifa-generic" for generic SCIFA compatible UART. > + - "renesas,scifb-generic" for generic SCIFB compatible UART. > + - "renesas,hscif-generic" for generic HSCIF compatible UART. > + > + When compatible with the generic version, nodes must also list the > + SoC-specific version corresponding to the platform. > + > + - reg: Base address and length of the memory resource used by the UART. > + > + - interrupt-parent: Reference to the parent interrupt controller. > + - interrupts: Interrupt number(s). Depending on the SoC SCIx UARTs are tied > + to one or multiple interrupt lines. When using multiple interrupt lines, > + specify the interrupt names as described below. > + > + - clocks: Reference to the SCIx UART interface clock. > + - clock-names: Should be "sci_ick". > + > +Optional properties: > + > + - interrupt-names: When using multiple interrupts, report the interrupt > + names as "eri" (receive error), "rxi" (receive), "txi" (transmit) and > + "bri" (break). When using a single interrupt this property should not be > + present. Hmm, is there a reason not to just have the 4 interrupts always present and in the case they are all wired to the same interrupt, just have the interrupts all be the same? example: interrupts = <0 144 4>, <0 144 4>, <0 144 4>, <0 144 4>; > + > +Note: Each enabled SCIx UART should have an alias correctly numbered in the > +"aliases" node. > + > +Example: > + aliases { > + serial0 = &scifa0; > + }; > + > + scifa0: serial@e6c40000 { > + compatible = "renesas,scifa-r8a7790", "renesas,scifa-generic"; > + reg = <0 0xe6c40000 0 64>; > + interrupt-parent = <&gic>; > + interrupts = <0 144 4>; > + clocks = <&mstp2_clks 4>; > + clock-names = "sci_ick"; > + }; might be nice to have an example with the 4 interrupts. - k -- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2013-10-31 14:42 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-29 10:29 [PATCH 0/5] Add OF support to the sh-sci serial port driver Laurent Pinchart 2013-10-29 10:29 ` Laurent Pinchart 2013-10-29 10:29 ` [PATCH 1/5] serial: sh-sci: Sort headers alphabetically Laurent Pinchart 2013-10-29 10:29 ` Laurent Pinchart 2013-10-29 10:29 ` [PATCH 2/5] serial: sh-sci: Remove baud rate calculation algorithm 5 Laurent Pinchart 2013-10-29 10:29 ` Laurent Pinchart 2013-10-29 10:29 ` [PATCH 3/5] serial: sh-sci: Simplify baud rate calculation algorithms Laurent Pinchart 2013-10-29 10:29 ` Laurent Pinchart 2013-10-29 10:48 ` Laurent Pinchart 2013-10-29 10:48 ` Laurent Pinchart 2013-10-29 10:29 ` [PATCH 4/5] serial: sh-sci: Add OF support Laurent Pinchart 2013-10-29 10:29 ` Laurent Pinchart 2013-11-01 9:47 ` Bastian Hecht 2013-11-01 9:47 ` Bastian Hecht 2013-11-04 0:58 ` Laurent Pinchart 2013-11-04 0:58 ` Laurent Pinchart 2013-11-06 15:26 ` Bastian Hecht 2013-11-06 15:26 ` Bastian Hecht 2013-10-29 10:29 ` [PATCH 5/5] serial: sh-sci: Add device tree bindings documentation Laurent Pinchart 2013-10-29 10:29 ` Laurent Pinchart 2013-10-31 14:42 ` Kumar Gala [this message] 2013-10-31 14:42 ` Kumar Gala 2013-10-31 14:55 ` Laurent Pinchart 2013-10-31 14:55 ` Laurent Pinchart 2013-10-31 15:00 ` Kumar Gala 2013-10-31 15:00 ` Kumar Gala 2013-11-03 17:09 ` Laurent Pinchart 2013-11-03 17:09 ` Laurent Pinchart 2013-10-31 5:21 ` [PATCH 0/5] Add OF support to the sh-sci serial port driver Simon Horman 2013-10-31 5:21 ` Simon Horman 2013-10-31 12:30 ` Laurent Pinchart 2013-10-31 12:30 ` Laurent Pinchart 2013-11-01 0:17 ` Simon Horman 2013-11-01 0:17 ` Simon Horman
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=9B7DF883-D119-47F5-BD71-11E30BE3DB88@codeaurora.org \ --to=galak@codeaurora.org \ --cc=devicetree@vger.kernel.org \ --cc=hechtb+renesas@gmail.com \ --cc=laurent.pinchart+renesas@ideasonboard.com \ --cc=lethal@linux-sh.org \ --cc=linux-serial@vger.kernel.org \ --cc=linux-sh@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: linkBe 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.