public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
	devicetree@vger.kernel.org, f.fainelli@gmail.com,
	jogo@openwrt.org, cernekee@gmail.com
Subject: Re: [PATCH v3 2/2] bmips: add device tree example for BCM6358
Date: Mon, 4 Apr 2016 00:16:15 -0500	[thread overview]
Message-ID: <20160404051615.GL17806@rob-hp-laptop> (raw)
In-Reply-To: <1459677376-10449-2-git-send-email-noltari@gmail.com>

On Sun, Apr 03, 2016 at 11:56:16AM +0200, Álvaro Fernández Rojas wrote:
> This adds a device tree example for SFR Neufbox4 (Sercomm version), which
> also serves as a real example for brcm,bcm6358-leds.
> 
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> ---
>  v3: Device tree fixes
>   - Use interrupt-controller instead of periph_intc.
>   - Use led@# instead of naming the LEDs.
>  v2: Remove led0 alias and use stdout-path only
> 
>  .../devicetree/bindings/mips/brcm/soc.txt          |   2 +-
>  arch/mips/bmips/Kconfig                            |   4 +
>  arch/mips/boot/dts/brcm/Makefile                   |   2 +
>  arch/mips/boot/dts/brcm/bcm6358.dtsi               | 111 +++++++++++++++++++++
>  arch/mips/boot/dts/brcm/bcm96358nb4ser.dts         |  46 +++++++++
>  5 files changed, 164 insertions(+), 1 deletion(-)
>  create mode 100644 arch/mips/boot/dts/brcm/bcm6358.dtsi
>  create mode 100644 arch/mips/boot/dts/brcm/bcm96358nb4ser.dts

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2016-04-04  5:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-21 11:41 [PATCH v2 1/2] bmips: add BCM6358 support Álvaro Fernández Rojas
     [not found] ` <1456054881-26787-1-git-send-email-noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-03 20:09   ` Florian Fainelli
2016-04-03  9:56   ` [PATCH v3 " Álvaro Fernández Rojas
     [not found]     ` <1459677376-10449-1-git-send-email-noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-03  9:56       ` [PATCH v3 2/2] bmips: add device tree example for BCM6358 Álvaro Fernández Rojas
2016-04-04  5:16         ` Rob Herring [this message]
2016-04-04  8:09     ` [PATCH v4 1/2] bmips: add BCM6358 support Álvaro Fernández Rojas
     [not found]       ` <1459757353-14683-1-git-send-email-noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-04  8:09         ` [PATCH v4 2/2] bmips: add device tree example for BCM6358 Álvaro Fernández Rojas
     [not found]           ` <1459757353-14683-2-git-send-email-noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-07 17:57             ` Rob Herring
2016-04-09 10:56         ` [PATCH 1/2] bmips: add BCM6358 support Álvaro Fernández Rojas
2016-04-09 10:56           ` [PATCH 2/2] bmips: add device tree example for BCM6358 Álvaro Fernández Rojas
     [not found]             ` <1460199408-18738-2-git-send-email-noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-11 19:33               ` Rob Herring

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=20160404051615.GL17806@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=cernekee@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=jogo@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    --cc=noltari@gmail.com \
    --cc=ralf@linux-mips.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