From: Gregory CLEMENT <gregory.clement@free-electrons•com>
To: Chris Packham <chris.packham@alliedtelesis•co.nz>
Cc: Mark Rutland <mark.rutland@arm•com>, Andrew Lunn <andrew@lunn•ch>,
Jason Cooper <jason@lakedaemon•net>,
devicetree@vger•kernel.org, netdev@vger•kernel.org,
Michael Turquette <mturquette@baylibre•com>,
Stephen Boyd <sboyd@codeaurora•org>,
Russell King <linux@armlinux•org.uk>,
linux-kernel@vger•kernel.org, Rob Herring <robh+dt@kernel•org>,
linux-clk@vger•kernel.org, linux-arm-kernel@lists•infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail•com>
Subject: Re: [PATCH v2 0/6] Updates for Marvell Switch SoCs
Date: Tue, 07 Mar 2017 18:10:12 +0100 [thread overview]
Message-ID: <87bmtdovwr.fsf@free-electrons.com> (raw)
In-Reply-To: <20170216085041.28337-1-chris.packham@alliedtelesis.co.nz> (Chris Packham's message of "Thu, 16 Feb 2017 21:50:34 +1300")
Hi Chris,
On jeu., févr. 16 2017, Chris Packham <chris.packham@alliedtelesis•co.nz> wrote:
> Shortly after I posted my last series I got access to a more recent
> Marvell SDK which had some device tree support for the switch SoCs I'd
> been wanting. It was still based on an older kernel but it was a huge
> improvement over what came before.
>
> Patch 1/6 is a typo I noticed after my initial series was applied.
>
> Patch 2/6 is a bit of a cleanup. I did initially struggle with how to
> access individual parts of the DFX block as well as retaining a handle on
> the entire thing for the switch driver to use.
>
> Patch 3/6 is a re-jig of the dtsi files which is needed by 5/6. This is
> required because I need to use the coreclk label on a different node. It
> also means I don't have to disable nodes for blocks that only exist on
> the Armada-XP.
>
> Patch 4/6, 5/6 are split from the previous versions.
>
> Patch 6/6 is the device tree portion of a change already in clk-next.
I applied patches 2, 3 and 6 on mvebu/dt with the acked-by from Rob when
he gave it.
Patch 1 is already part of 4.11-rc1.
For patch 4 and 5 I understand that either we don't need it or it should
be a updated version so I skipped them.
Thanks,
Gregory
>
> Chris Packham (6):
> ARM: dts: Fix typo in armada-xp-98dx4251
> Changes in v2
> - new
> Changes in v3:
> - none
> ARM: dts: armada-xp-98dx3236: combine dfx server nodes
> Changes in v2:
> - none
> Changes in v3:
> - none
> ARM: dts: Use armada-370-xp as a base for armada-xp-98dx3236
> Changes in v2:
> - Update root compatible strings in armada-xp-98dx3336.dtsi,
> armada-xp-98dx4251.dtsi, armada-xp-db-dxbc2.dts and
> armada-xp-db-xc3-24g4xg.dts
> Changes in v3:
> - none
> ARM: dts: mvebu: Add binding for mv98dx3236-soc-id
> Changes in v3:
> - new, split from driver
> ARM: mvebu: Add driver for mv98dx3236-soc-id
> Changes in v2:
> - none
> Changes in v3:
> - split from dts changes
> ARM: dts: mvebu: Move mv98dx3236 clock bindings
> Changes in v2:
> - New. Split out from "clk: mvebu: Expand mv98dx3236-core-clock support"
> Changes in v3:
> - Clarify why the old location was wrong (but worked).
>
>
> .../bindings/arm/marvell/mv98dx3236-soc-id.txt | 14 ++
> .../devicetree/bindings/clock/mvebu-core-clock.txt | 7 +
> .../bindings/clock/mvebu-gated-clock.txt | 11 ++
> .../devicetree/bindings/net/marvell,prestera.txt | 13 +-
> arch/arm/boot/dts/armada-xp-98dx3236.dtsi | 213 ++++++++++++++++-----
> arch/arm/boot/dts/armada-xp-98dx3336.dtsi | 2 +-
> arch/arm/boot/dts/armada-xp-98dx4251.dtsi | 2 +-
> arch/arm/boot/dts/armada-xp-db-dxbc2.dts | 2 +-
> arch/arm/boot/dts/armada-xp-db-xc3-24g4xg.dts | 2 +-
> arch/arm/mach-mvebu/mvebu-soc-id.c | 43 ++++-
> 10 files changed, 242 insertions(+), 67 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/arm/marvell/mv98dx3236-soc-id.txt
>
> --
> 2.11.0.24.ge6920cf
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2017-03-07 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 8:50 [PATCH v2 0/6] Updates for Marvell Switch SoCs Chris Packham
[not found] ` <20170216085041.28337-1-chris.packham-6g8wRflRTwXFdCa3tKVlE6U/zSkkHjvu@public.gmane.org>
2017-02-16 8:50 ` [PATCH v3 2/6] ARM: dts: armada-xp-98dx3236: combine dfx server nodes Chris Packham
2017-02-27 14:49 ` Rob Herring
2017-03-07 17:10 ` Gregory CLEMENT [this message]
2017-03-07 19:38 ` [PATCH v2 0/6] Updates for Marvell Switch SoCs Chris Packham
-- strict thread matches above, loose matches on Subject: below --
2017-02-07 20:28 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=87bmtdovwr.fsf@free-electrons.com \
--to=gregory.clement@free-electrons$(echo .)com \
--cc=andrew@lunn$(echo .)ch \
--cc=chris.packham@alliedtelesis$(echo .)co.nz \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=jason@lakedaemon$(echo .)net \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-clk@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=mark.rutland@arm$(echo .)com \
--cc=mturquette@baylibre$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=robh+dt@kernel$(echo .)org \
--cc=sboyd@codeaurora$(echo .)org \
--cc=sebastian.hesselbarth@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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