From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
Linus Walleij <linus.walleij@linaro.org>,
"linux\@armlinux.org.uk" <linux@armlinux.org.uk>,
"linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Brand <chris.brand@broadcom.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"Arnd Bergmann" <arnd@arndb.de>,
Thierry Reding <treding@nvidia.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Juri Lelli <juri.lelli@arm.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Kalyan Kinthada <Kalyan.Kinthada@alliedtelesis.co.nz>,
"devicetree\@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-clk\@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-gpio\@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCHv5 0/5] Support for Marvell switches with integrated CPUs
Date: Mon, 30 Jan 2017 15:40:31 +0100 [thread overview]
Message-ID: <87o9yotxuo.fsf@free-electrons.com> (raw)
In-Reply-To: <f8f6e8db585147d3adb025bed29694ab@svr-chch-ex1.atlnz.lc> (Chris Packham's message of "Sun, 29 Jan 2017 20:30:34 +0000")
Hi Chris,
On dim., janv. 29 2017, Chris Packham <Chris.Packham@alliedtelesis.co.nz> wrote:
> On 28/01/17 07:47, Stephen Boyd wrote:
>> On 01/27, Gregory CLEMENT wrote:
>>> Hi all,
>>>
>>> On ven., janv. 27 2017, Chris Packham <chris.packham@alliedtelesis.co.nz> wrote:
>>>
>>>> The 98DX3236, 98DX3336 and 98DX4251 are a set of switch ASICs with
>>>> integrated CPUs. They CPU block is common within these product lines and
>>>> (as far as I can tell/have been told) is based on the Armada XP. There
>>>> are a few differences due to the fact they have to squeeze the CPU into
>>>> the same package as the switch.
>>>>
>>>> I've rebased this series against linux-pinctrl/devel to get access to
>>>> mvebu_mmio_mpp_ctrl. Everything else still applies cleanly to
>>>> v4.10.0-rc5.
>>>
>>> Just to let you know that I plan to apply the 3 arm patch once Chris
>>> will have sent the new series with the minor fixes I asked on patch 3.
>>>
>>> I already applied them in the for-next branch to benefit of some build
>>> test coverage.
>>>
>>> Stephen,
>>>
>>> you gave your Acked-by on the first patch, but don't you plan to apply
>>> it on the clk branch?
>>
>> It must have not been clear if I should apply it, hence the ack.
>> I'll apply it now.
>>
>
> Sorry my bad. I need all 5 together in one place to actually test the
> series.
The 5 patches should be available soon (if it is not already the case),
in the linux-next branch.
The clk patch is already there, the 3 arm patch have been merged in my
mvebu/for-next branch, and the pinctrl patch is about to be merged in
the pinctrl/for-next branch.
Gregory
>
> I wasn't sure whether the series should go through mvebu with Acks from
> clk and pinctrl or if things should go to the separate maintainers and
> come together when they hit the main linux repo. Up until the latest
> pinctrl change either approach would have worked.
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2017-01-30 14:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 3:25 [PATCHv5 0/5] Support for Marvell switches with integrated CPUs Chris Packham
2017-01-27 3:25 ` [PATCHv5 1/5] clk: mvebu: support for 98DX3236 SoC Chris Packham
2017-01-27 18:48 ` Stephen Boyd
2017-01-27 3:25 ` [PATCHv5 2/5] arm: mvebu: support for SMP on 98DX3336 SoC Chris Packham
2017-01-27 14:06 ` Gregory CLEMENT
2017-01-27 3:25 ` [PATCHv5 3/5] pinctrl: mvebu: pinctrl driver for 98DX3236 SoC Chris Packham
2017-01-27 3:25 ` [PATCHv5 4/5] arm: mvebu: Add device tree for 98DX3236 SoCs Chris Packham
2017-01-27 3:25 ` [PATCHv5 5/5] arm: mvebu: Add device tree for db-dxbc2 and db-xc3-24g4xg boards Chris Packham
2017-01-27 16:48 ` Gregory CLEMENT
2017-01-27 16:39 ` [PATCHv5 0/5] Support for Marvell switches with integrated CPUs Gregory CLEMENT
2017-01-27 16:49 ` Gregory CLEMENT
2017-01-27 18:47 ` Stephen Boyd
2017-01-29 20:30 ` Chris Packham
2017-01-30 14:40 ` Gregory CLEMENT [this message]
2017-01-30 20:27 ` Chris Packham
2017-01-29 23:20 Chris Packham
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=87o9yotxuo.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=Kalyan.Kinthada@alliedtelesis.co.nz \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=chris.brand@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=geert+renesas@glider.be \
--cc=jason@lakedaemon.net \
--cc=juri.lelli@arm.com \
--cc=ldewangan@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=sudeep.holla@arm.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=treding@nvidia.com \
/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).