From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH/RFC net-next v3 3/4] ravb: Document binding for r8a7795 SoC
Date: Mon, 21 Sep 2015 09:27:54 +0900 [thread overview]
Message-ID: <20150921002751.GA24857@verge.net.au> (raw)
In-Reply-To: <CAMuHMdUFMq1szvY=8twhzcM36zyBjDF1fnkNd2kw+s=qxXYVmg@mail.gmail.com>
On Fri, Sep 18, 2015 at 09:27:11AM +0200, Geert Uytterhoeven wrote:
> On Fri, Sep 18, 2015 at 8:03 AM, Simon Horman
> <horms+renesas@verge.net.au> wrote:
> > From: Kazuya Mizuguchi <kazuya.mizuguchi.ks@renesas.com>
> >
> > This patch updates the ravb binding to support the r8a7795 SoC by:
> > - Adding a compat string for the new hardware
> > - Adding 25 named interrupts to binding for the new SoC;
> > older SoCs continue to use a single multiplexed interrupt
> >
> > The example is also updated to reflect the r8a7795 as this is the
> > more complex case.
> >
> > Based on work by Kazuya Mizuguchi and others.
> >
> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
>
> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> Modulo the minor nit below...
>
> > --- a/Documentation/devicetree/bindings/net/renesas,ravb.txt
> > +++ b/Documentation/devicetree/bindings/net/renesas,ravb.txt
>
> > @@ -18,6 +22,12 @@ Required properties:
> > Optional properties:
> > - interrupt-parent: the phandle for the interrupt controller that services
> > interrupts for this device.
> > +- interrupt-names: A list of interrupt names.
> > + For the R8A7795 SoC this property is mandatory;
> > + it should include one entry per channel, named "ch%u",
> > + where %u is the channel number ranging from 0 to 24.
> > + For other SoCs this property is optional; if present
> > + is should contain "mux" for a single muxed interrupt.
>
> it
Thanks, I will fix that.
next prev parent reply other threads:[~2015-09-21 0:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 6:03 [PATCH/RFC net-next v3 0/4] ravb: Add support for r8a7795 SoC Simon Horman
2015-09-18 6:03 ` [PATCH/RFC net-next v3 1/4] phylib: Add phy_set_max_speed helper Simon Horman
2015-09-18 6:03 ` [PATCH/RFC net-next v3 2/4] ravb: Provide dev parameter to DMA API Simon Horman
2015-09-18 6:03 ` [PATCH/RFC net-next v3 3/4] ravb: Document binding for r8a7795 SoC Simon Horman
2015-09-18 7:27 ` Geert Uytterhoeven
2015-09-21 0:27 ` Simon Horman [this message]
2015-09-18 6:03 ` [PATCH/RFC net-next v3 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=20150921002751.GA24857@verge.net.au \
--to=horms@verge.net.au \
--cc=f.fainelli@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@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).