From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Kirkwood: Add DT description of QNAP 419
Date: Tue, 14 Jan 2014 10:15:43 +0100 [thread overview]
Message-ID: <20140114091543.GC334@lunn.ch> (raw)
In-Reply-To: <20140114004833.GI19878@titan.lakedaemon.net>
On Mon, Jan 13, 2014 at 07:48:33PM -0500, Jason Cooper wrote:
> On Mon, Jan 06, 2014 at 11:49:17PM +0100, Andrew Lunn wrote:
> > Re-implement the Marvell Kirkwood ts41x-setup.c in DT.
> >
> > As with the QNAP 119, there are two variants, depending on which SoC
> > has been used. They differ on Ethernet PHY addresses and number of
> > PCIe busses.
> >
> > Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> > ---
> > arch/arm/boot/dts/Makefile | 4 +-
> > arch/arm/boot/dts/kirkwood-ts419-6281.dts | 20 ++++++++
> > arch/arm/boot/dts/kirkwood-ts419-6282.dts | 32 ++++++++++++
> > arch/arm/boot/dts/kirkwood-ts419.dtsi | 75 +++++++++++++++++++++++++++++
> > 4 files changed, 130 insertions(+), 1 deletion(-)
> > create mode 100644 arch/arm/boot/dts/kirkwood-ts419-6281.dts
> > create mode 100644 arch/arm/boot/dts/kirkwood-ts419-6282.dts
> > create mode 100644 arch/arm/boot/dts/kirkwood-ts419.dtsi
>
> Applied to mvebu/dt with Ian's Tested-by
Hi Jason
Thanks, but please could you hold onto it for a while. I would like to
see how the discussion about unstable /dev/input/by-path discussion
plays out. That is if anybody actually replies to my question...
Thanks
Andrew
next prev parent reply other threads:[~2014-01-14 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 22:49 [PATCH] ARM: Kirkwood: Add DT description of QNAP 419 Andrew Lunn
2014-01-08 9:48 ` Ian Campbell
2014-01-08 15:59 ` Andrew Lunn
2014-01-11 21:04 ` Andrew Lunn
2014-01-15 16:36 ` Arnd Bergmann
2014-01-15 17:45 ` Andrew Lunn
2014-01-15 18:20 ` Arnd Bergmann
2014-01-14 0:39 ` Jason Cooper
2014-01-14 8:15 ` Ian Campbell
2014-01-14 0:48 ` Jason Cooper
2014-01-14 9:15 ` Andrew Lunn [this message]
2014-01-14 13:00 ` Jason Cooper
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=20140114091543.GC334@lunn.ch \
--to=andrew@lunn.ch \
--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).