linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH/RFC 04/10] ravb: Add support for r8a7795 SoC
Date: Fri, 28 Aug 2015 01:42:37 +0000	[thread overview]
Message-ID: <20150828014231.GC7357@verge.net.au> (raw)
In-Reply-To: <1440667450-3513-5-git-send-email-horms+renesas@verge.net.au>

On Thu, Aug 27, 2015 at 01:01:50PM +0200, Geert Uytterhoeven wrote:
> On Thu, Aug 27, 2015 at 11:24 AM, Simon Horman
> <horms+renesas@verge.net.au> wrote:
> > --- a/Documentation/devicetree/bindings/net/renesas,ravb.txt
> > +++ b/Documentation/devicetree/bindings/net/renesas,ravb.txt
> > @@ -6,8 +6,12 @@ interface contains.
> >  Required properties:
> >  - compatible: "renesas,etheravb-r8a7790" if the device is a part of R8A7790 SoC.
> >               "renesas,etheravb-r8a7794" if the device is a part of R8A7794 SoC.
> > +             "renesas,etheravb-r8a7795" if the device is a part of R8A7795 SoC.
> >  - reg: offset and length of (1) the register block and (2) the stream buffer.
> > -- interrupts: interrupt specifier for the sole interrupt.
> > +- interrupts: if the device is a part of R8A7790/R8A7794 SoC
> > +              interrupt specifier for the sole interrupt.
> > +              if the device is a part of R8A7795 SoC
> > +              interrupt specifier for the two interrupts.
> 
> If there are multiple interrupts, you best make them named interrupts,
> i.e. requiring "interrupt-names", too.

Thanks, I will look into that.

> Why are there only 2 interrupts? The datasheet mentions 25, for ch0-ch24.

Thanks for bringing that up. I think it has also come up elsewhere in this
thread. I'd like to focus on addressing it here rather than spreading the
discussion around any further.

My understanding is that on the R-Car Gen3 r8a7795 SoC
the EthernetAVB hardware may function in one of two modes.

1. A mode which is "mostly" compatible with R-Car Gen2
   (e.g. r8a7790, r8a7790).

   In this mode only ch22 and ch24 are used.

   I note that the emac interrupt also appears to be documented for Gen-2.
   Its not clear to me at this time why it isn't appropriate to use it
   on those SoCs.

2. A mode which is new in Gen 3.

   In this mode ch0 - ch24 are used.
   I believe that in this mode there are per DMA queue interrupts.



  parent reply	other threads:[~2015-08-28  1:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27  9:24 [PATCH/RFC 04/10] ravb: Add support for r8a7795 SoC Simon Horman
2015-08-27 11:01 ` Geert Uytterhoeven
2015-08-27 11:03 ` Sergei Shtylyov
2015-08-28  1:42 ` Simon Horman [this message]
2015-08-28  2:01 ` Simon Horman
2015-08-28  2:13 ` Simon Horman
2015-08-28  8:27 ` Simon Horman
2015-08-28  8:35 ` Geert Uytterhoeven
2015-08-28  9:09 ` Simon Horman
2015-08-28 10:20 ` Sergei Shtylyov
2015-08-28 10:30 ` Sergei Shtylyov
2015-08-28 10:51 ` Sergei Shtylyov
2015-08-28 11:46 ` Sergei Shtylyov
2015-08-28 12:05 ` Simon Horman
2015-08-28 12:42 ` Sergei Shtylyov
2015-08-28 13:21 ` Sergei Shtylyov
2015-09-02  2:13 ` Simon Horman
2015-09-02  2:13 ` Simon Horman
2015-09-02  2:14 ` Simon Horman
2015-09-02  7:26 ` Geert Uytterhoeven
2015-09-02  7:43 ` Simon Horman
2015-09-07 23:06 ` Sergei Shtylyov
2015-09-08 20:52 ` Sergei Shtylyov
2015-09-09  1:45 ` 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=20150828014231.GC7357@verge.net.au \
    --to=horms@verge.net.au \
    --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: 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).