From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/9] DRA7xx core support
Date: Mon, 12 Aug 2013 13:57:13 +0530 [thread overview]
Message-ID: <52089C61.20001@ti.com> (raw)
In-Reply-To: <20130812082431.GI7656@atomide.com>
On Monday 12 August 2013 01:54 PM, Tony Lindgren wrote:
> * Rajendra Nayak <rnayak@ti.com> [130811 23:47]:
>> On Sunday 04 August 2013 09:57 PM, Rajendra Nayak wrote:
>>> Changes in v3:
>>> -1- Dropped some clock/dpll framework builds for dra7
>>> -2- Added all instances of IPs in dtsi file
>>> -3- dtsi does a 'disabled' by default and dts enables as needed
>>> -4- soc_is_dra7xx() based on DT compatible instead of using ID code
>>>
>>> Changes in v2:
>>> -1- Fixed minor changelog details
>>> -2- Dropped the SRAM support patch since we need to move to drivers/misc/sram.c
>>> -3- Added DTS update patches to this series which were earlier posted as
>>> part of the data series (Since they don't have much objections as against the
>>> other in-kernel data files)
>>> -4- Updated the EVM dts file with pin config details for uart/mcspi and i2c
>>>
>>> DRA7xx based SoCs' are high-performance, infotainment application devices,
>>> based on enhanced OMAP architecture integrated on a 28nm
>>> technology.
>>>
>>> The DRA7xx family is composed of DRA75x and DRA74x devices.
>>> The current device for which the patches add support is the
>>> DRA752 SoC.
>>>
>>> Most of the core IPs are similar to those found on the OMAP5
>>> devices, including the dual cortex-A15 based MPU subsystem,
>>> which has helped quite some reuse from existing OMAP5 support.
>>>
>>> This series contains only core support patches and none of
>>> the PRCM and hwmod data needed for the device to boot.
>>
>> Tony, any chance of this series making it to 3.12?
>
> Looks OK to me, want to do a pull request against -rc5 for me?
Sure, will do. Thanks.
>
> Regards,
>
> Tony
>
prev parent reply other threads:[~2013-08-12 8:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-04 16:27 [PATCH v3 0/9] DRA7xx core support Rajendra Nayak
2013-08-04 16:27 ` [PATCH v3 1/9] ARM: DRA7: Reuse all of PRCM and MPUSS SMP infra Rajendra Nayak
2013-08-04 16:27 ` [PATCH v3 2/9] ARM: DRA7: Reuse io tables and add a new .init_early Rajendra Nayak
2013-08-04 16:27 ` [PATCH v3 3/9] ARM: DRA7: Resue the clocksource, clockevent support Rajendra Nayak
2013-08-04 16:27 ` [PATCH v3 4/9] ARM: DRA7: board-generic: Add basic DT support Rajendra Nayak
2013-08-04 16:27 ` [PATCH v3 5/9] ARM: DRA7: Kconfig: Make ARCH_NR_GPIO default to 512 Rajendra Nayak
2013-08-04 16:27 ` [PATCH v3 6/9] ARM: DRA7: dts: Add the dts files for dra7 SoC and dra7-evm board Rajendra Nayak
2013-08-04 16:27 ` [PATCH v3 7/9] ARM: DRA7: id: Add cpu detection support for DRA7xx based SoCs' Rajendra Nayak
2013-08-05 11:44 ` Grygorii Strashko
2013-08-06 8:11 ` Rajendra Nayak
2013-08-06 11:59 ` Grygorii Strashko
2013-08-04 16:27 ` [PATCH v3 8/9] ARM: DRA7: hwmod: Reuse the soc_ops used for OMAP4/5 Rajendra Nayak
2013-08-04 16:27 ` [PATCH v3 9/9] ARM: DRA7: Add the build support in omap2plus Rajendra Nayak
2013-08-12 6:40 ` [PATCH v3 0/9] DRA7xx core support Rajendra Nayak
2013-08-12 8:24 ` Tony Lindgren
2013-08-12 8:27 ` Rajendra Nayak [this message]
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=52089C61.20001@ti.com \
--to=rnayak@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).