From: Rajendra Nayak <rnayak@ti.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org
Cc: tony@atomide.com, bcousson@baylibre.com, nm@ti.com,
arnd@arndb.de, s-anna@ti.com, Rajendra Nayak <rnayak@ti.com>
Subject: [PATCH v4 0/5] ARM: DRA7: Add support for DRA72x devices
Date: Tue, 29 Apr 2014 16:35:08 +0530 [thread overview]
Message-ID: <1398769513-8736-1-git-send-email-rnayak@ti.com> (raw)
changes in v4:
-1- used full SoC names in compatibles eg "ti,dra742" and "ti,dra722"
-2- Created a seperate patch for replacing __initdata with __initconst
changes in v3:
Removed wildcards from compatible strings and duplicates from
.dt_compat strings as suggested by Arnd
DRA72x devices are single core Cortex A15 devices belonging to the
DRA7 family (Similar to the DRA74x devices which are dual core Cortex
A15 based)
The patches (based off 3.15-rc3) add minimal DT/kernel modifications to add
boot support on DRA722 device reusing all the kernel data for DRA742 device.
Rajendra Nayak (5):
ARM: dts: dra7-evm: Remove the wrong and undocumented compatible
ARM: dts: Add support for DRA72x family of devices
ARM: OMAP2+: Replace all __initdata with __initconst for const init
ARM: OMAP2+: Add machine entry for dra72x devices
ARM: DRA7: Add support for soc_is_dra74x() and soc_is_dra72x()
varients
.../devicetree/bindings/arm/omap/omap.txt | 12 ++++--
arch/arm/boot/dts/Makefile | 3 +-
arch/arm/boot/dts/dra7-evm.dts | 6 +--
arch/arm/boot/dts/dra7.dtsi | 27 ------------
arch/arm/boot/dts/dra72-evm.dts | 24 +++++++++++
arch/arm/boot/dts/dra72x.dtsi | 25 +++++++++++
arch/arm/boot/dts/dra74x.dtsi | 41 ++++++++++++++++++
arch/arm/mach-omap2/board-generic.c | 45 ++++++++++++++------
arch/arm/mach-omap2/soc.h | 7 +++
9 files changed, 142 insertions(+), 48 deletions(-)
create mode 100644 arch/arm/boot/dts/dra72-evm.dts
create mode 100644 arch/arm/boot/dts/dra72x.dtsi
create mode 100644 arch/arm/boot/dts/dra74x.dtsi
--
1.7.9.5
next reply other threads:[~2014-04-29 11:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 11:05 Rajendra Nayak [this message]
2014-04-29 11:05 ` [PATCH v4 1/5] ARM: dts: dra7-evm: Remove the wrong and undocumented compatible Rajendra Nayak
2014-04-29 11:05 ` [PATCH v4 2/5] ARM: dts: Add support for DRA72x family of devices Rajendra Nayak
2014-04-29 11:16 ` Arnd Bergmann
2014-04-29 11:05 ` [PATCH v4 3/5] ARM: OMAP2+: Replace all __initdata with __initconst for const init Rajendra Nayak
[not found] ` <1398769513-8736-1-git-send-email-rnayak-l0cyMroinI0@public.gmane.org>
2014-04-29 11:05 ` [PATCH v4 4/5] ARM: OMAP2+: Add machine entry for dra72x devices Rajendra Nayak
[not found] ` <1398769513-8736-5-git-send-email-rnayak-l0cyMroinI0@public.gmane.org>
2014-04-29 11:16 ` Arnd Bergmann
2014-04-29 11:05 ` [PATCH v4 5/5] ARM: DRA7: Add support for soc_is_dra74x() and soc_is_dra72x() varients Rajendra Nayak
2014-04-29 11:18 ` Arnd Bergmann
2014-04-29 11:19 ` Rajendra Nayak
2014-05-06 16:28 ` Tony Lindgren
2014-05-07 4:38 ` Rajendra Nayak
2014-05-06 5:45 ` [PATCH v4 0/5] ARM: DRA7: Add support for DRA72x devices Rajendra Nayak
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=1398769513-8736-1-git-send-email-rnayak@ti.com \
--to=rnayak@ti.com \
--cc=arnd@arndb.de \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=s-anna@ti.com \
--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;
as well as URLs for NNTP newsgroup(s).