From: rric@kernel.org (Robert Richter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] arm64, thunder: Enable Cavium Thunder SoC Family
Date: Thu, 2 Oct 2014 09:29:38 +0200 [thread overview]
Message-ID: <20141002072938.GM20170@rric.localhost> (raw)
In-Reply-To: <20140923141429.GH20170@rric.localhost>
On 23.09.14 16:14:29, Robert Richter wrote:
> On 23.09.14 12:21:05, Catalin Marinas wrote:
> > On Tue, Sep 23, 2014 at 11:46:41AM +0100, Will Deacon wrote:
> > > On Tue, Sep 23, 2014 at 11:41:22AM +0100, Robert Richter wrote:
> > > > On 12.09.14 19:49:43, Robert Richter wrote:
> > > > > From: Robert Richter <rrichter@cavium.com>
> > > > >
> > > > > This initial patches enable Cavium Thunder SoC Family. The patches add
> > > > > devicetree and Kconfig support and then add Thunder to the defconfig.
> > > > >
> > > > > The Thunder system needs more enablement patches for subsystems and
> > > > > devices, this includes network, ahci, gicv3/gicv3-its, pci, smmu, kvm.
> > > > > We will send separate patch sets for these. All of them base on this
> > > > > initial patches.
> > > > >
> > > > > I sent a separate patch set independently that introduces support for
> > > > > dts vendor subdirs. After both patch sets have been applied I will
> > > > > send a patch in addition that moves the dts file into a subdirectory.
> > > > >
> > > > > I sent another separate patch that sets NR_CPUS to 64 per default.
> > > > >
> > > > > The first patch introduces dts files without having a Kconfig option
> > > > > for the soc (ARCH_THUNDER). However, this is introduced in patch 3 and
> > > > > added to defconfig in patch 4 as this is my preferred solution. If
> > > > > there is still resistance having an ARCH_THUNDER option, just drop
> > > > > them.
> > > > >
> > > > > Patches are available here:
> > > > >
> > > > > git://git.kernel.org/pub/scm/linux/kernel/git/rric/linux.git thunder/init
> > > >
> > > > it would be good if these patches could be applied.
> > >
> > > Catalin's handling the 3.18 merge window, but this looks like arm-soc
> > > material anyway and should go via Olof/Arnd.
> >
> > Yes. Olof said he's cherry-picking arm64 SoC patches (or Robert could
> > send him a pull request).
>
> just in case you want to pull, please pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rric/linux.git tags/for-arm-soc-v3.18
Olof, Arnd,
please pull or apply.
Thanks,
-Robert
next prev parent reply other threads:[~2014-10-02 7:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 17:49 [PATCH v3 0/4] arm64, thunder: Enable Cavium Thunder SoC Family Robert Richter
2014-09-12 17:49 ` [PATCH v3 1/4] arm64, thunder: Add initial dts for Cavium Thunder SoC Robert Richter
2014-09-12 17:49 ` [PATCH v3 2/4] arm64, thunder: Document devicetree bindings " Robert Richter
2014-09-12 17:49 ` [PATCH v3 3/4] arm64, thunder: Add Kconfig option for Cavium Thunder SoC Family Robert Richter
2014-09-12 17:49 ` [PATCH v3 4/4] arm64, defconfig: Enable Cavium Thunder SoC in defconfig Robert Richter
2014-09-23 10:41 ` [PATCH v3 0/4] arm64, thunder: Enable Cavium Thunder SoC Family Robert Richter
2014-09-23 10:46 ` Will Deacon
2014-09-23 11:21 ` Catalin Marinas
2014-09-23 14:14 ` Robert Richter
2014-10-02 7:29 ` Robert Richter [this message]
2014-10-02 14:44 ` [GIT PULL] " Robert Richter
2014-10-02 15:44 ` Arnd Bergmann
2014-10-06 8:32 ` Robert Richter
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=20141002072938.GM20170@rric.localhost \
--to=rric@kernel.org \
--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).