linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] ARM: OMAP2+: CLEANUP: Remove unnecessary ifdef around __omap2_set_globals
Date: Tue, 8 May 2012 09:11:15 -0700	[thread overview]
Message-ID: <20120508161114.GW5088@atomide.com> (raw)
In-Reply-To: <1336489364-19200-4-git-send-email-hvaibhav@ti.com>

* Vaibhav Hiremath <hvaibhav@ti.com> [120508 08:10]:
> --- a/arch/arm/mach-omap2/Kconfig
> +++ b/arch/arm/mach-omap2/Kconfig
> @@ -20,12 +20,16 @@ config ARCH_OMAP2PLUS_TYPICAL
>  	help
>  	  Compile a kernel suitable for booting most boards
>  
> +config SOC_HAS_SDRC
> +	bool "SDRAM Controller support"
> +
>  config ARCH_OMAP2
>  	bool "TI OMAP2"
>  	depends on ARCH_OMAP2PLUS
>  	default y
>  	select CPU_V6
>  	select MULTI_IRQ_HANDLER
> +	select SOC_HAS_SDRC
>  
>  config ARCH_OMAP3
>  	bool "TI OMAP3"

These still need to have OMAP in them, and ideally the type
of the block. Something like SOC_HAS_OMAP2_SDRC?

Regards,

Tony

  reply	other threads:[~2012-05-08 16:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 15:02 [PATCH 0/4] ARM: OMAP2+: Cleanup series in order to remove ARCH_OMAPx dependency Vaibhav Hiremath
2012-05-08 15:02 ` [PATCH 1/4] ARM: OMAP2+: CLEANUP: All OMAP2PLUS uses omap-device.o target so add one entry Vaibhav Hiremath
2012-05-08 15:02 ` [PATCH 2/4] ARM: OMAP2+: CLEANUP: Move omap3 dpll ops to dpll3xxx.c Vaibhav Hiremath
2012-05-08 15:02 ` [PATCH 3/4] ARM: OMAP2+: CLEANUP: Remove unnecessary ifdef around __omap2_set_globals Vaibhav Hiremath
2012-05-08 16:11   ` Tony Lindgren [this message]
2012-05-08 15:02 ` [RFC PATCH 4/4] ARM: OMAP2+: CLEANUP: Add new config option for different DPLL features Vaibhav Hiremath
2012-05-08 16:12   ` Tony Lindgren
2012-05-08 17:24     ` Hiremath, Vaibhav
2012-05-08 17:26       ` Tony Lindgren

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=20120508161114.GW5088@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).