From: Aaro Koskinen <aaro.koskinen-X3B1VOXEql0@public.gmane.org>
To: Ralf Baechle <ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>,
linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Aaro Koskinen <aaro.koskinen-X3B1VOXEql0@public.gmane.org>
Subject: [PATCH v2 0/3] MIPS: OCTEON: Add support for D-Link DSR-500N router
Date: Mon, 12 Sep 2016 23:39:07 +0300 [thread overview]
Message-ID: <20160912203910.1164-1-aaro.koskinen@iki.fi> (raw)
Hi,
D-Link DSR-500N is close to 1000N and with small changes we
can support both.
v2: Delete redudant led labels from dlink_dsr-500n.dts.
A.
Aaro Koskinen (3):
MIPS: OCTEON: split dlink_dsr-1000n.dts
MIPS: OCTEON: add DTS for D-Link DSR-500N
MIPS: OCTEON: fix PCI interrupt routing on D-Link DSR-500N
.../boot/dts/cavium-octeon/dlink_dsr-1000n.dts | 45 +----------------
.../dts/cavium-octeon/dlink_dsr-500n-1000n.dtsi | 58 ++++++++++++++++++++++
.../mips/boot/dts/cavium-octeon/dlink_dsr-500n.dts | 40 +++++++++++++++
arch/mips/pci/pci-octeon.c | 2 +
4 files changed, 101 insertions(+), 44 deletions(-)
create mode 100644 arch/mips/boot/dts/cavium-octeon/dlink_dsr-500n-1000n.dtsi
create mode 100644 arch/mips/boot/dts/cavium-octeon/dlink_dsr-500n.dts
--
2.9.2
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-09-12 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 20:39 Aaro Koskinen [this message]
2016-09-12 20:39 ` [PATCH v2 1/3] MIPS: OCTEON: split dlink_dsr-1000n.dts Aaro Koskinen
[not found] ` <20160912203910.1164-1-aaro.koskinen-X3B1VOXEql0@public.gmane.org>
2016-09-12 20:39 ` [PATCH v2 2/3] MIPS: OCTEON: add DTS for D-Link DSR-500N Aaro Koskinen
2016-09-12 20:39 ` [PATCH v2 3/3] MIPS: OCTEON: fix PCI interrupt routing on " Aaro Koskinen
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=20160912203910.1164-1-aaro.koskinen@iki.fi \
--to=aaro.koskinen-x3b1voxeql0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org \
--cc=ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.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).