All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Brandt <Chris.Brandt@renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS 
	<devicetree@vger.kernel.org>,
	Linux-Renesas" <linux-renesas-soc@vger.kernel.org>,
	Simon Horman <horms+renesas@verge.net.au>
Subject: RE: [PATCH 2/2] serial: sh-sci: Document r7s9210 bindings
Date: Wed, 18 Jul 2018 22:23:26 +0000	[thread overview]
Message-ID: <TY1PR01MB1562B58322D08B16123BB1CA8A530@TY1PR01MB1562.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdWdOoEbwPOzOfEAHH0MXNr-Wf_-37i8Qj6WdphgyKLe7g@mail.gmail.com>

Hi Geert,

On Tuesday, July 17, 2018, Geert Uytterhoeven wrote:
> On Fri, Jul 13, 2018 at 5:50 PM Geert Uytterhoeven <geert@linux-m68k.org>
> wrote:
> > On Wed, Jul 11, 2018 at 4:42 PM Chris Brandt <chris.brandt@renesas.com>
> wrote:
> > > Add R7S9210 (RZ/A2) support
> > >
> > > Signed-off-by: Chris Brandt <chris.brandt@renesas.com>
> >
> > Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> 
> Sorry, I spoke too soon.
> It seems the bindings were never updated for the use of multiple
> interrupts
> on RZ/A1.  As RZ/A2 adds one new interrupt, can you please document which
> interrupts are required?
> Thanks!

The issue that I ran into was the device driver assumed some signals 
were muxed together (TXI and DRI), and that other signals were individual.

The existing driver wanted interrupts to be specified in this order:
  1. Error
  2. RX
  3. TX (assumes DRI)
  4. Break

However, for the SCIF that is present in the RZ/A2M, Error and Break are
muxed together, and then DRI is not muxed with TX. This is different 
than any other SCIF supported by the driver.

My solution was to list the Error/Break twice, and then add a new 
interrupt for DRI.

As reference, here is what the DT node would look like:

	scif0: serial@e8007000 {
		compatible = "renesas,scif-r7s9210", "renesas,scif";
		reg = <0xe8007000 18>;
		interrupts = <GIC_SPI 265 IRQ_TYPE_LEVEL_HIGH>, /* ERI0/BRI0 */
			     <GIC_SPI 266 IRQ_TYPE_LEVEL_HIGH>,   /* RXI0 */
			     <GIC_SPI 267 IRQ_TYPE_LEVEL_HIGH>,   /* TXI0 */
			     <GIC_SPI 265 IRQ_TYPE_LEVEL_HIGH>,   /* ERI0/BRI0 */
			     <GIC_SPI 268 IRQ_TYPE_LEVEL_HIGH>;   /* TEI/DRI0 */
		clocks = <&mstp4_clks R7S9210_CLK_SCIF0>;
		clock-names = "fck";
		power-domains = <&cpg_clocks>;
		status = "disabled";
	};

Of course I have no problem documenting all this, but I first I just 
wanted to make sure I was not going to get push back when I submit a DT 
later that lists the same interrupt twice.

Thanks,
Chris




  parent reply	other threads:[~2018-07-18 22:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11 14:41 [PATCH 0/2] serial: sh-sci: Add support for RZ/A2 Chris Brandt
2018-07-11 14:41 ` [PATCH 1/2] serial: sh-sci: Add support for R7S9210 Chris Brandt
2018-07-20  8:09   ` Geert Uytterhoeven
2018-07-11 14:41 ` [PATCH 2/2] serial: sh-sci: Document r7s9210 bindings Chris Brandt
2018-07-13 15:50   ` Geert Uytterhoeven
2018-07-17  8:35     ` Geert Uytterhoeven
2018-07-17 13:43       ` Chris Brandt
2018-07-17 13:43         ` Chris Brandt
2018-07-18 22:19       ` Chris Brandt
2018-07-18 22:19         ` Chris Brandt
2018-07-19  8:13         ` Geert Uytterhoeven
2018-07-19 12:58           ` Chris Brandt
2018-07-19 12:58             ` Chris Brandt
2018-07-20  8:16             ` Geert Uytterhoeven
2018-07-25  1:37           ` Chris Brandt
2018-07-25  1:37             ` Chris Brandt
2018-07-25  7:06             ` Geert Uytterhoeven
2018-07-25 12:04               ` Chris Brandt
2018-07-25 12:04                 ` Chris Brandt
2018-07-25 12:34                 ` Geert Uytterhoeven
2018-07-18 22:23       ` Chris Brandt [this message]
2018-07-18 22:23         ` Chris Brandt

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=TY1PR01MB1562B58322D08B16123BB1CA8A530@TY1PR01MB1562.jpnprd01.prod.outlook.com \
    --to=chris.brandt@renesas.com \
    --cc=geert@linux-m68k.org \
    --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 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.