From: Chris Brandt <chris.brandt@renesas.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org,
	Simon Horman <horms+renesas@verge.net.au>,
	Chris Brandt <chris.brandt@renesas.com>
Subject: [PATCH v2 0/3] serial: sh-sci: Add support for RZ/A2
Date: Wed, 25 Jul 2018 09:38:47 -0500	[thread overview]
Message-ID: <20180725143850.32985-1-chris.brandt@renesas.com> (raw)
The RZ/A2 uses a modified SCIF that until recently was only used in
Renesas MCU devices (not MPU devices).
So, while it functions mostly the same as a normal SCIF, some things
needed to be shifted around.
In the end, a standard compatible = "renesas,scif" is all that is really
needed (not a SoC specific "renesas,scif-r7s9210").
Becase there is no device tree yet, here is sample of what it would
look like:
	scif0: serial@e8007000 {
		compatible = "renesas,scif-r7s9210", "renesas,scif";
		reg = <0xe8007000 18>;
		interrupts = <GIC_SPI 265 IRQ_TYPE_LEVEL_HIGH>,
			     <GIC_SPI 266 IRQ_TYPE_LEVEL_HIGH>,
			     <GIC_SPI 267 IRQ_TYPE_LEVEL_HIGH>,
			     <GIC_SPI 265 IRQ_TYPE_LEVEL_HIGH>,
			     <GIC_SPI 268 IRQ_TYPE_LEVEL_HIGH>,
			     <GIC_SPI 268 IRQ_TYPE_LEVEL_HIGH>;
		clocks = <&mstp4_clks R7S9210_CLK_SCIF0>;
		clock-names = "fck";
		power-domains = <&cpg_clocks>;
		status = "disabled";
	};
Chris Brandt (3):
  serial: sh-sci: Allow for compressed SCIF address space
  serial: sh-sci: Add support for separate TEI+DRI interrupts
  serial: sh-sci: Document r7s9210 bindings
 .../bindings/serial/renesas,sci-serial.txt         | 17 +++++-
 drivers/tty/serial/sh-sci.c                        | 66 ++++++++++++++++++----
 2 files changed, 70 insertions(+), 13 deletions(-)
-- 
2.16.1
next             reply	other threads:[~2018-07-25 14:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25 14:38 Chris Brandt [this message]
2018-07-25 14:38 ` [PATCH v2 1/3] serial: sh-sci: Allow for compressed SCIF address space Chris Brandt
2018-07-26 11:31   ` Geert Uytterhoeven
2018-07-26 12:14     ` Chris Brandt
2018-07-26 12:41       ` Geert Uytterhoeven
2018-07-25 14:38 ` [PATCH v2 2/3] serial: sh-sci: Add support for separate TEI+DRI interrupts Chris Brandt
2018-07-26 11:39   ` Geert Uytterhoeven
2018-07-26 12:16     ` Chris Brandt
2018-07-25 14:38 ` [PATCH v2 3/3] serial: sh-sci: Document r7s9210 bindings Chris Brandt
2018-07-26 11:41   ` Geert Uytterhoeven
2018-07-26 12:18     ` Chris Brandt
2018-07-30 23:19   ` Rob Herring
2018-07-26 11:43 ` [PATCH v2 0/3] serial: sh-sci: Add support for RZ/A2 Geert Uytterhoeven
2018-07-26 12:25   ` Chris Brandt
2018-07-26 13:01     ` Geert Uytterhoeven
2018-07-26 13:10       ` Chris Brandt
2018-07-28 14:55       ` Greg KH
2018-07-28 15:55         ` Chris Brandt
2018-07-31 10:27           ` Simon Horman
2018-07-28 19:28         ` Geert Uytterhoeven
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=20180725143850.32985-1-chris.brandt@renesas.com \
    --to=chris.brandt@renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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: 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).