From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH/RFC v2 net-next 3/4] ravb: Document binding for r8a7795 SoC
Date: Fri, 11 Sep 2015 08:53:12 +0000 [thread overview]
Message-ID: <20150911085311.GA8547@verge.net.au> (raw)
In-Reply-To: <CAMuHMdUYhUrT9vBtfPOdDWxHDq+ENhKvg9bmsHZsyyDJ=YtcLw@mail.gmail.com>
On Fri, Sep 11, 2015 at 10:41:31AM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Fri, Sep 11, 2015 at 10:14 AM, Simon Horman <horms@verge.net.au> wrote:
> >> > @@ -18,6 +21,9 @@ Required properties:
> >> > Optional properties:
> >> > - interrupt-parent: the phandle for the interrupt controller that services
> >> > interrupts for this device.
> >> > +- interrupt-names: One entry per interrupt named "ch%u".
> >> > + For the R8A7795 SoC this property is mandatory,
> >> > + and "ch0" through "ch24" are mandatory.
> >>
> >> This suggests the single multiplexed interrupt on R-Car Gen2 can be called
> >> "ch0". Is that what you want? I know the driver doesn't care.
> >
> > No, its not what I intended.
> >
> > I think its reasonable to allow the multiplexed interrupt to be named,
> > but to what I wonder. The documentation seems to call the interrupt
> > "EthernetAVB", which isn't very exciting.
>
> Perhaps "mux", like I did for rspi, cfr.
> Documentation/devicetree/bindings/spi/spi-rspi.txt:
>
> - interrupts : A list of interrupt-specifiers, one for each entry in
> interrupt-names.
> If interrupt-names is not present, an interrupt specifier
> for a single muxed interrupt.
> - interrupt-names : A list of interrupt names. Should contain (if present):
> - "error" for SPEI,
> - "rx" for SPRI,
> - "tx" to SPTI,
> - "mux" for a single muxed interrupt.
Thanks for for that example. "mux" sounds good to me.
next prev parent reply other threads:[~2015-09-11 8:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 2:01 [PATCH/RFC v2 net-next 0/4] ravb: Add support for r8a7795 SoC Simon Horman
2015-09-11 2:01 ` [PATCH/RFC v2 net-next 1/4] phylib: Add phy_set_max_speed helper Simon Horman
2015-09-11 4:14 ` Florian Fainelli
2015-09-11 4:30 ` Simon Horman
2015-09-11 13:34 ` Sergei Shtylyov
2015-09-11 2:01 ` [PATCH/RFC v2 net-next 2/4] ravb: Provide dev parameter to DMA API Simon Horman
2015-09-11 2:01 ` [PATCH/RFC v2 net-next 3/4] ravb: Document binding for r8a7795 SoC Simon Horman
2015-09-11 7:12 ` Geert Uytterhoeven
2015-09-11 8:14 ` Simon Horman
2015-09-11 8:41 ` Geert Uytterhoeven
2015-09-11 8:53 ` Simon Horman [this message]
2015-09-11 14:25 ` Sergei Shtylyov
2015-09-14 0:42 ` Simon Horman
2015-09-30 18:26 ` Sergei Shtylyov
2015-09-11 2:01 ` [PATCH/RFC v2 net-next 4/4] ravb: Add support " 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=20150911085311.GA8547@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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).