From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP2+: DRA72x/DRA74x basic support
Date: Thu, 28 Aug 2014 10:02:58 -0700 [thread overview]
Message-ID: <20140828170258.GH16006@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1408280617360.21985@utopia.booyaka.com>
Arnd & Olof,
Can you please pick this one up for the -rc cycle so the TI guys
can boot test dra7 with mainline properly?
Regards,
Tony
* Paul Walmsley <paul@pwsan.com> [140827 23:18]:
> Hi Tony,
>
> The following changes since commit 52addcf9d6669fa439387610bc65c92fa0980cef:
>
> Linux 3.17-rc2 (2014-08-25 15:36:20 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/for-v3.17-rc/omap-dra72x-d74x-support-a
>
> for you to fetch changes up to f7f7a29bf0cf25af23f37e5b5bf1368b85705286:
>
> ARM: DRA7: hwmod: Add dra74x and dra72x specific ocp interface lists (2014-08-27 19:38:23 -0600)
>
> ----------------------------------------------------------------
> Add basic subarchitecture support for the DRA72x and DRA74x. These
> are OMAP2+ derivative SoCs. This should be low-risk to existing OMAP
> platforms.
>
> Basic build, boot, and PM test logs are available here:
>
> http://www.pwsan.com/omap/testlogs/hwmod-a-early-v3.17-rc/20140827194314/
>
> ----------------------------------------------------------------
> Rajendra Nayak (2):
> ARM: DRA7: Add support for soc_is_dra74x() and soc_is_dra72x() variants
> ARM: DRA7: hwmod: Add dra74x and dra72x specific ocp interface lists
>
> arch/arm/mach-omap2/omap_hwmod.c | 3 +++
> arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 22 ++++++++++++++++++++--
> arch/arm/mach-omap2/soc.h | 6 ++++++
> 3 files changed, 29 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2014-08-28 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 6:18 [GIT PULL] ARM: OMAP2+: DRA72x/DRA74x basic support Paul Walmsley
2014-08-28 17:02 ` Tony Lindgren [this message]
2014-08-31 17:19 ` Olof Johansson
2014-09-05 18:03 ` Paul Walmsley
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=20140828170258.GH16006@atomide.com \
--to=tony@atomide.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).