From: Stefan Agner <stefan@agner.ch>
To: shawn.guo@freescale.com, kernel@pengutronix.de, arnd@arndb.de
Cc: b35083@freescale.com, bpringlemeir@nbsps.com,
mark.rutland@arm.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stefan@agner.ch
Subject: [PATCH v2 0/4] ARM: vf610: restructure device trees
Date: Wed, 22 Oct 2014 18:27:53 +0200 [thread overview]
Message-ID: <1413995277-2844-1-git-send-email-stefan@agner.ch> (raw)
This patchset is v2 of "ARM: dts: vf500/vf610: support VF500 SoC",
and grew by some patches. It now also solves some issues uncovered
by the "ARM: vf610m4: Add Vybrid Cortex-M4 support" patchset. The
next Cortex-M4 patchset will then base on this patchset.
I could again not use the -M/-B parameter to generate smaller and
better readable patches. Those patches ended up not apply-able.
Changes in v2:
- Assign fixed input clocks to clock controller module to ensure correct
initialization order
- Get rid of "clocks"-node and move fixed clocks to the root level
- Move peripherals to vfxxx.dtsi to allow share the nodes for Cortex-A5
and Cortex-M4 SoC device trees.
Stefan Agner (4):
ARM: dts: vf610: assign oscillator to clock module
ARM: imx: clk-vf610: get input clocks from assigned clocks
ARM: dts: vf610: create generic base device trees
ARM: dts: vf500-colibri: add Colibri VF50 support
.../devicetree/bindings/clock/vf610-clock.txt | 15 +
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/vf-colibri-eval-v3.dtsi | 54 +++
arch/arm/boot/dts/vf-colibri.dtsi | 142 ++++++
arch/arm/boot/dts/vf500-colibri-eval-v3.dts | 17 +
arch/arm/boot/dts/vf500-colibri.dtsi | 20 +
arch/arm/boot/dts/vf500.dtsi | 171 +++++++
arch/arm/boot/dts/vf610-colibri-eval-v3.dts | 47 +-
arch/arm/boot/dts/vf610-colibri.dtsi | 137 +-----
arch/arm/boot/dts/vf610-cosmic.dts | 14 +-
arch/arm/boot/dts/vf610-twr.dts | 37 +-
arch/arm/boot/dts/vf610.dtsi | 507 +--------------------
arch/arm/boot/dts/vfxxx.dtsi | 436 ++++++++++++++++++
arch/arm/mach-imx/clk-vf610.c | 20 +-
14 files changed, 920 insertions(+), 698 deletions(-)
create mode 100644 arch/arm/boot/dts/vf-colibri-eval-v3.dtsi
create mode 100644 arch/arm/boot/dts/vf-colibri.dtsi
create mode 100644 arch/arm/boot/dts/vf500-colibri-eval-v3.dts
create mode 100644 arch/arm/boot/dts/vf500-colibri.dtsi
create mode 100644 arch/arm/boot/dts/vf500.dtsi
create mode 100644 arch/arm/boot/dts/vfxxx.dtsi
--
2.1.2
next reply other threads:[~2014-10-22 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 16:27 Stefan Agner [this message]
2014-10-22 16:27 ` [PATCH v2 1/4] ARM: dts: vf610: assign oscillator to clock module Stefan Agner
2014-10-22 16:27 ` [PATCH v2 2/4] ARM: imx: clk-vf610: get input clocks from assigned clocks Stefan Agner
2014-10-22 16:27 ` [PATCH v2 3/4] ARM: dts: vf610: create generic base device trees Stefan Agner
2014-10-22 16:27 ` [PATCH v2 4/4] ARM: dts: vf500-colibri: add Colibri VF50 support Stefan Agner
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=1413995277-2844-1-git-send-email-stefan@agner.ch \
--to=stefan@agner.ch \
--cc=arnd@arndb.de \
--cc=b35083@freescale.com \
--cc=bpringlemeir@nbsps.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=shawn.guo@freescale.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
all inboxes | Powered by JetHome®