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 09:09:56 +0000 [thread overview]
Message-ID: <20150828090955.GA10143@verge.net.au> (raw)
In-Reply-To: <1440667450-3513-5-git-send-email-horms+renesas@verge.net.au>
On Fri, Aug 28, 2015 at 10:35:56AM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> Thanks for the update!
>
> On Fri, Aug 28, 2015 at 10:27 AM, Simon Horman <horms@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: interrupt specifiers.
> > + One data and one emac interrupt for the R8A7795 SoC;
> > + these interrupts must be named.
> > + One named or unnamed data interrupt otherwise.
> > - phy-mode: see ethernet.txt file in the same directory.
> > - phy-handle: see ethernet.txt file in the same directory.
> > - #address-cells: number of address cells for the MDIO bus, must be equal to 1.
> > @@ -18,6 +22,12 @@ Required properties:
> > Optional properties:
> > - interrupt-parent: the phandle for the interrupt controller that services
> > interrupts for this device.
> > +- interrupt-names: Names of named interrupts.
> > + If the property is present "data" is required.
> > + "emac" is also required for the R8A7795 SoC;
> > + it is prohibited otherwise.
> > + This property is mandatory for the R8A7795 SoC;
> > + optional otherwise.
> > - pinctrl-names: pin configuration state name ("default").
> > - renesas,no-ether-link: boolean, specify when a board does not provide a proper
> > AVB_LINK signal.
>
> What about the 25 channel interrupts?
> "data" and "emac" seem to use ch22 resp. ch 24 on Gen3.
>
> I'm afraid this will bite us one day.
Yes, I worry about that too. But perhaps we can disallow the use of
"data" and "emac" if all (any of) the chXX interrupts are named.
next prev parent reply other threads:[~2015-08-28 9:09 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
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 [this message]
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=20150828090955.GA10143@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 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.