From: Jon Hunter <jon-hunter@ti.com>
To: Tony Lindgren <tony@atomide.com>, Benoit Cousson <b-cousson@ti.com>
Cc: device-tree <devicetree-discuss@lists.ozlabs.org>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
Jon Hunter <jon-hunter@ti.com>
Subject: [PATCH V2 0/8] ARM: dts: Various OMAP2+ device-tree updates
Date: Fri, 15 Mar 2013 08:57:33 -0500 [thread overview]
Message-ID: <1363355861-11773-1-git-send-email-jon-hunter@ti.com> (raw)
Various OMAP device-tree updates for PMU, DMA, GPIO, GPMC and boards.
The DMA, PMU and OMAP3430 SDP board changes have been sent before
individually but re-sending here as a complete series for v3.10.
This is based upon Benoit's for_3.10/dts branch [1]. Branch available
here [2].
V2 changes:
- Rebased on Benoit's for_3.10/dts branch
- Squashed patches adding support for OMAP3430 SDP board and patch
to add flash support for OMAP3430 SDP board.
[1] http://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git/log/?h=for_3.10/dts
[2] git://github.com/jonhunter/linux.git omap-dt-for-v3.10
Jon Hunter (8):
ARM: OMAP2+: Prepare for device-tree PMU support
ARM: dts: OMAP2+: Add PMU nodes
ARM: dts: OMAP2+: Add SDMA controller bindings and nodes
ARM: dts: Add GPMC node for OMAP2, OMAP4 and OMAP5
ARM: dts: Add OMAP2 gpio bindings
ARM: dts: OMAP3+: Correct gpio #interrupts-cells property
ARM: dts: OMAP3: Add reg and interrupt properties for gpio
ARM: dts: OMAP3: Add support for OMAP3430 SDP board
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/omap2.dtsi | 17 ++++
arch/arm/boot/dts/omap2420.dtsi | 55 +++++++++++++
arch/arm/boot/dts/omap2430.dtsi | 66 ++++++++++++++++
arch/arm/boot/dts/omap3.dtsi | 70 +++++++++++++++--
arch/arm/boot/dts/omap3430-sdp.dts | 141 ++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/omap4-panda-es.dts | 2 +
arch/arm/boot/dts/omap4.dtsi | 64 +++++++++++++--
arch/arm/boot/dts/omap4460.dtsi | 18 +++++
arch/arm/boot/dts/omap5.dtsi | 68 ++++++++++++++--
arch/arm/mach-omap2/pmu.c | 14 +++-
11 files changed, 493 insertions(+), 23 deletions(-)
create mode 100644 arch/arm/boot/dts/omap3430-sdp.dts
create mode 100644 arch/arm/boot/dts/omap4460.dtsi
--
1.7.10.4
next reply other threads:[~2013-03-15 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 13:57 Jon Hunter [this message]
2013-03-15 13:57 ` [PATCH V2 1/8] ARM: OMAP2+: Prepare for device-tree PMU support Jon Hunter
2013-03-15 13:57 ` [PATCH V2 2/8] ARM: dts: OMAP2+: Add PMU nodes Jon Hunter
2013-03-15 13:57 ` [PATCH V2 3/8] ARM: dts: OMAP2+: Add SDMA controller bindings and nodes Jon Hunter
2013-03-15 13:57 ` [PATCH V2 4/8] ARM: dts: Add GPMC node for OMAP2, OMAP4 and OMAP5 Jon Hunter
2013-03-15 13:57 ` [PATCH V2 5/8] ARM: dts: Add OMAP2 gpio bindings Jon Hunter
2013-03-15 13:57 ` [PATCH V2 6/8] ARM: dts: OMAP3+: Correct gpio #interrupts-cells property Jon Hunter
2013-03-15 13:57 ` [PATCH V2 7/8] ARM: dts: OMAP3: Add reg and interrupt properties for gpio Jon Hunter
2013-03-15 13:57 ` [PATCH V2 8/8] ARM: dts: OMAP3: Add support for OMAP3430 SDP board Jon Hunter
2013-03-15 14:30 ` [PATCH V2 0/8] ARM: dts: Various OMAP2+ device-tree updates Benoit Cousson
2013-03-17 9:35 ` Anil Kumar
2013-03-18 10:14 ` Benoit Cousson
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=1363355861-11773-1-git-send-email-jon-hunter@ti.com \
--to=jon-hunter@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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