From: s-anna@ti.com (Suman Anna)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/9]
Date: Tue, 24 Jun 2014 20:09:39 -0500 [thread overview]
Message-ID: <53AA2153.1010906@ti.com> (raw)
In-Reply-To: <1403658065-54614-1-git-send-email-s-anna@ti.com>
On 06/24/2014 08:00 PM, Suman Anna wrote:
> Hi Tony, Paul,
Please ignore this, resent the same message and the series with the
proper subject.
regards
Suman
>
> This patch series adds the minimal mailbox DT nodes for the SoCs that are
> currently missing them (OMAP4, AM335x, DRA7). It also limits the legacy
> mailbox platform device creation only for non-DT boot, and cleans up the
> legacy hwmod addresses and attributes used for creating the sub-mailbox
> devices. The sub-mailboxes in DT boot are not created until the OMAP
> mailbox DT adoption series, and is not an issue since some of the other
> required hwmod data for using legacy-mode devices have already been
> cleaned up.
>
> The patches are based on 3.16-rc2. The series do not have any order
> dependencies with the OMAP mailbox cleanup series [1], and can be applied
> in any order. The following shows the boot logs on various OMAP platforms
> with just these patches on top of 3.16-rc2:
> OMAP2 (SDP2430) : http://slexy.org/view/s21gGdJxXP
> OMAP3 (BeagleXM) : http://slexy.org/view/s2n8Pc83Rp
> OMAP4 (PandaBoard) : http://slexy.org/view/s21StNWKPz
> OMAP5 (OMAP5 uEVM) : http://slexy.org/view/s2y3t6HZtk
> DRA7 (DRA7 EVM) : http://slexy.org/view/s2qY23Mt97
> AM33xx (BeagleBone Black) : http://slexy.org/view/s2ce8jj35O
> AM43xx (AM437x GP EVM) : http://slexy.org/view/s2nttmOLSq
>
> [1] http://marc.info/?l=linux-omap&m=140365705821115&w=2
>
> Suman Anna (9):
> ARM: dts: OMAP4: Add mailbox node
> ARM: dts: AM33xx: Add mailbox node
> ARM: dts: AM4372: Correct mailbox node data
> ARM: dts: DRA7: Add mailbox nodes
> ARM: DRA7: hwmod_data: Add mailbox hwmod data
> ARM: OMAP2+: Avoid mailbox legacy device creation for DT-boot
> ARM: OMAP2: hwmod_data: Remove legacy mailbox data and addrs
> ARM: OMAP4: hwmod_data: Remove legacy mailbox addrs
> ARM: AM33xx: hwmod_data: Remove legacy mailbox addrs
>
> arch/arm/boot/dts/am33xx.dtsi | 7 +
> arch/arm/boot/dts/am4372.dtsi | 7 +-
> arch/arm/boot/dts/dra7.dtsi | 91 ++++++
> arch/arm/boot/dts/omap4.dtsi | 7 +
> arch/arm/mach-omap2/devices.c | 2 +-
> arch/arm/mach-omap2/omap_hwmod_2420_data.c | 14 -
> arch/arm/mach-omap2/omap_hwmod_2430_data.c | 13 -
> .../omap_hwmod_2xxx_3xxx_interconnect_data.c | 9 -
> .../omap_hwmod_33xx_43xx_interconnect_data.c | 10 -
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 10 -
> arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 305 +++++++++++++++++++++
> arch/arm/mach-omap2/omap_hwmod_common_data.h | 1 -
> 12 files changed, 412 insertions(+), 64 deletions(-)
>
next prev parent reply other threads:[~2014-06-25 1:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 1:00 [PATCH 0/9] Suman Anna
2014-06-25 1:09 ` Suman Anna [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-17 13:06 [RFC PATCH v3] Consolidate SRAM support Nori, Sekhar
2011-05-17 21:41 ` [PATCH 0/9] Ben Gardiner
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=53AA2153.1010906@ti.com \
--to=s-anna@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).