From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 04/14] ARM: OMAP5: Add minimal support for OMAP5430 SOC
Date: Thu, 5 Jul 2012 07:33:34 -0700 [thread overview]
Message-ID: <20120705143333.GE1122@atomide.com> (raw)
In-Reply-To: <1341490136-25901-7-git-send-email-santosh.shilimkar@ti.com>
* Santosh Shilimkar <santosh.shilimkar@ti.com> [120705 05:13]:
> --- a/arch/arm/plat-omap/Makefile
> +++ b/arch/arm/plat-omap/Makefile
> @@ -10,9 +10,7 @@ obj-n :=
> obj- :=
>
> # omap_device support (OMAP2+ only at the moment)
> -obj-$(CONFIG_ARCH_OMAP2) += omap_device.o
> -obj-$(CONFIG_ARCH_OMAP3) += omap_device.o
> -obj-$(CONFIG_ARCH_OMAP4) += omap_device.o
> +obj-$(CONFIG_ARCH_OMAP2PLUS) += omap_device.o
>
> obj-$(CONFIG_OMAP_DM_TIMER) += dmtimer.o
> obj-$(CONFIG_OMAP_DEBUG_DEVICES) += debug-devices.o
FYI, this we already have as commit b4cb410d in devel-am33xx-part2.
I can merge first few patches in devel-am33xx-part2 branch into
cleanup-part2 so this part can be just left out.
Regards,
Tony
next prev parent reply other threads:[~2012-07-05 14:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 12:08 [PATCH v1 00/14] ARM: OMAP5: Add minimal OMAP5 SOC support Santosh Shilimkar
2012-07-05 12:08 ` [PATCH v1 01/14] ARM: OMAP2+: Move stubbed secure_sram_reserve function to a common.c and call it __weak Santosh Shilimkar
2012-07-05 12:08 ` [PATCH 2/5] ARM: OMAP5: board-generic: Add device tree support Santosh Shilimkar
2012-07-05 12:08 ` [PATCH v1 02/14] ARM: OMAP: counter-32k: Select the CR register offset using the IP scheme Santosh Shilimkar
2012-07-05 12:08 ` [PATCH 3/5] arm/dts: OMAP5: Add omap5 dts files Santosh Shilimkar
2012-07-05 12:08 ` [PATCH v1 03/14] ARM: OMAP5: id: Add cpu id for ES versions Santosh Shilimkar
2012-07-05 14:26 ` Tony Lindgren
2012-07-05 14:29 ` Shilimkar, Santosh
2012-07-05 12:08 ` [PATCH v1 04/14] ARM: OMAP5: Add minimal support for OMAP5430 SOC Santosh Shilimkar
2012-07-05 14:33 ` Tony Lindgren [this message]
2012-07-05 14:36 ` Shilimkar, Santosh
2012-07-05 16:02 ` Tony Lindgren
2012-07-05 12:08 ` [PATCH 4/5] ARM: OMAP5: Add the build support Santosh Shilimkar
2012-07-05 12:08 ` [PATCH 5/5] ARM: Kconfig update to support additional GPIOs in OMAP5 Santosh Shilimkar
2012-07-05 12:08 ` [PATCH v1 05/14] ARM: OMAP5: timer: Add clocksource, clockevent support Santosh Shilimkar
2012-07-05 12:08 ` [PATCH v1 06/14] ARM: OMAP5: gpmc: Update gpmc_init() Santosh Shilimkar
2012-07-05 12:08 ` [PATCH v1 07/14] ARM: OMAP5: l3: Add l3 error handler support for omap5 Santosh Shilimkar
2012-07-05 12:08 ` [PATCH v1 08/14] ARM: OMAP5: Add the WakeupGen IP updates Santosh Shilimkar
2012-07-05 12:08 ` [PATCH v1 09/14] ARM: OMAP5: Add SMP support Santosh Shilimkar
2012-07-05 12:08 ` [PATCH v1 10/14] ARM: omap2+: board-generic: clean up the irq data from board file Santosh Shilimkar
2012-07-05 12:08 ` [PATCH v1 11/14] ARM: OMAP5: board-generic: Add device tree support Santosh Shilimkar
2012-07-05 12:08 ` [PATCH v1 12/14] arm/dts: OMAP5: Add omap5 dts files Santosh Shilimkar
2012-07-05 12:08 ` [PATCH v1 13/14] ARM: OMAP5: Add the build support Santosh Shilimkar
2012-07-05 12:08 ` [PATCH v1 14/14] ARM: Kconfig update to support additional GPIOs in OMAP5 Santosh Shilimkar
2012-07-05 12:22 ` [PATCH v1 00/14] ARM: OMAP5: Add minimal OMAP5 SOC support Shilimkar, Santosh
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=20120705143333.GE1122@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).