From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
linux-mips@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
Steen.Hegelund@microchip.com
Subject: Re: [PATCH v2 0/9] MIPS: Add support for more mscc SoCs: Luton, Serval and Jaguar2
Date: Thu, 12 Nov 2020 23:38:05 +0100 [thread overview]
Message-ID: <20201112223805.GA19695@alpha.franken.de> (raw)
In-Reply-To: <20201110114508.1197652-1-gregory.clement@bootlin.com>
On Tue, Nov 10, 2020 at 12:44:59PM +0100, Gregory CLEMENT wrote:
> Hello,
>
> Ocelot SoC belongs to a larger family of SoCs called VCoreIII. Luton,
> Serval and Jaguar2 are part of this family and are added with this
> series.
>
> This the second version with a few changes in device tree.
>
> To be able to run a linux kernel the irqchip support and the pinctrl
> support are needed. Two series of patches adding this support has been
> posted to their subsystem. However there is no build dependency
> between them.
>
> Changelog:
> v1 -> v2
> - Moved the changes in binding documentation from patch 8 to 2
> - Fixed i2c devices node name in jaguar2 device tree files
> - Added Acked-by from Rob Herring
> - Fixes few more devices tree nodes, now there is no more warning when
> running "make W=1 dtbs"
>
> Gregory
>
> Gregory CLEMENT (9):
> dt-bindings: mips: Add Luton
> dt-bindings: mips: Add Serval and Jaguar2
> MIPS: mscc: Prepare configuration to handle more SoCs
> MIPS: mscc: Fix configuration name for ocelot legacy boards
> MIPS: mscc: Add luton dtsi
> MIPS: mscc: Add luton PC0B91 device tree
> MIPS: mscc: build FIT image for Luton
> MIPS: mscc: Add jaguar2 support
> MIPS: mscc: Add serval support
>
> .../devicetree/bindings/mips/mscc.txt | 2 +-
> arch/mips/boot/dts/Makefile | 2 +-
> arch/mips/boot/dts/mscc/Makefile | 11 +-
> arch/mips/boot/dts/mscc/jaguar2.dtsi | 167 +++++++++++
> arch/mips/boot/dts/mscc/jaguar2_common.dtsi | 25 ++
> arch/mips/boot/dts/mscc/jaguar2_pcb110.dts | 267 ++++++++++++++++++
> arch/mips/boot/dts/mscc/jaguar2_pcb111.dts | 107 +++++++
> arch/mips/boot/dts/mscc/jaguar2_pcb118.dts | 57 ++++
> arch/mips/boot/dts/mscc/luton.dtsi | 116 ++++++++
> arch/mips/boot/dts/mscc/luton_pcb091.dts | 30 ++
> arch/mips/boot/dts/mscc/serval.dtsi | 153 ++++++++++
> arch/mips/boot/dts/mscc/serval_common.dtsi | 127 +++++++++
> arch/mips/boot/dts/mscc/serval_pcb105.dts | 17 ++
> arch/mips/boot/dts/mscc/serval_pcb106.dts | 17 ++
> arch/mips/generic/Kconfig | 37 ++-
> arch/mips/generic/Platform | 3 +
> arch/mips/generic/board-jaguar2.its.S | 40 +++
> arch/mips/generic/board-luton.its.S | 23 ++
> arch/mips/generic/board-serval.its.S | 24 ++
> 19 files changed, 1218 insertions(+), 7 deletions(-)
> create mode 100644 arch/mips/boot/dts/mscc/jaguar2.dtsi
> create mode 100644 arch/mips/boot/dts/mscc/jaguar2_common.dtsi
> create mode 100644 arch/mips/boot/dts/mscc/jaguar2_pcb110.dts
> create mode 100644 arch/mips/boot/dts/mscc/jaguar2_pcb111.dts
> create mode 100644 arch/mips/boot/dts/mscc/jaguar2_pcb118.dts
> create mode 100644 arch/mips/boot/dts/mscc/luton.dtsi
> create mode 100644 arch/mips/boot/dts/mscc/luton_pcb091.dts
> create mode 100644 arch/mips/boot/dts/mscc/serval.dtsi
> create mode 100644 arch/mips/boot/dts/mscc/serval_common.dtsi
> create mode 100644 arch/mips/boot/dts/mscc/serval_pcb105.dts
> create mode 100644 arch/mips/boot/dts/mscc/serval_pcb106.dts
> create mode 100644 arch/mips/generic/board-jaguar2.its.S
> create mode 100644 arch/mips/generic/board-luton.its.S
> create mode 100644 arch/mips/generic/board-serval.its.S
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-11-12 22:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 11:44 [PATCH v2 0/9] MIPS: Add support for more mscc SoCs: Luton, Serval and Jaguar2 Gregory CLEMENT
2020-11-10 11:45 ` [PATCH v2 1/9] dt-bindings: mips: Add Luton Gregory CLEMENT
2020-11-10 12:29 ` Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 2/9] dt-bindings: mips: Add Serval and Jaguar2 Gregory CLEMENT
2020-11-10 12:30 ` Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 3/9] MIPS: mscc: Prepare configuration to handle more SoCs Gregory CLEMENT
2020-11-10 12:30 ` Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 4/9] MIPS: mscc: Fix configuration name for ocelot legacy boards Gregory CLEMENT
2020-11-10 12:30 ` Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 5/9] MIPS: mscc: Add luton dtsi Gregory CLEMENT
2020-11-10 12:31 ` Alexandre Belloni
2020-11-10 12:32 ` Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 6/9] MIPS: mscc: Add luton PC0B91 device tree Gregory CLEMENT
2020-11-10 12:33 ` Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 7/9] MIPS: mscc: build FIT image for Luton Gregory CLEMENT
2020-11-10 12:33 ` Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 8/9] MIPS: mscc: Add jaguar2 support Gregory CLEMENT
2020-11-10 12:33 ` Alexandre Belloni
2020-11-10 11:45 ` [PATCH v2 9/9] MIPS: mscc: Add serval support Gregory CLEMENT
2020-11-10 12:34 ` Alexandre Belloni
2020-11-12 22:38 ` Thomas Bogendoerfer [this message]
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=20201112223805.GA19695@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=lars.povlsen@microchip.com \
--cc=linux-mips@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.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).