linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: pl2x0/pl310: Refactor Kconfig to be more maintainable
Date: Mon, 12 Dec 2011 09:31:52 -0600	[thread overview]
Message-ID: <4EE61E68.9050807@gmail.com> (raw)
In-Reply-To: <20111212151404.GC2296@linaro.org>

On 12/12/2011 09:14 AM, Dave Martin wrote:
> On Tue, Nov 29, 2011 at 01:25:55PM -0600, Rob Herring wrote:
>> On 11/29/2011 10:32 AM, Dave Martin wrote:

[snip]

>>>  config CACHE_L2X0
>>>  	bool "Enable the L2x0 outer cache controller"
>>> -	depends on REALVIEW_EB_ARM11MP || MACH_REALVIEW_PB11MP || MACH_REALVIEW_PB1176 || \
>>> -		   REALVIEW_EB_A9MP || ARCH_IMX_V6_V7 || MACH_REALVIEW_PBX || \
>>> -		   ARCH_NOMADIK || ARCH_OMAP4 || ARCH_EXYNOS4 || ARCH_TEGRA || \
>>> -		   ARCH_U8500 || ARCH_VEXPRESS_CA9X4 || ARCH_SHMOBILE || \
>>> -		   ARCH_PRIMA2 || ARCH_ZYNQ || ARCH_CNS3XXX || ARCH_HIGHBANK
>>> +	depends on HAVE_L2X0_L2CC
>>
>> For platforms that run in non-secure mode, this shouldn't really be a
>> user selectable option. Perhaps those should just select CACHE_L2X0
>> directly. I'm not sure which one's those are other than Highbank and OMAP4.
> 
> Highbank doesn't currently have this.  Should I add this, or should we
> leave that for a separate patch?
> 
> Arguably, a refactoring patch shouldn't change the Kconfig behaviour --
> possibly anything which is currently broken should stay broken (but can
> be fixed later).

I thinking highbank wouldn't need HAVE_L2X0_L2CC, but it does to satisfy
dependencies. So you're right, it should probably be separate.

Rob

  reply	other threads:[~2011-12-12 15:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 16:32 [PATCH] ARM: pl2x0/pl310: Refactor Kconfig to be more maintainable Dave Martin
2011-11-29 19:25 ` Rob Herring
2011-11-29 22:18   ` Russell King - ARM Linux
2011-12-06 16:26   ` Dave Martin
2011-12-06 16:51     ` Rob Herring
2011-12-06 17:20       ` Dave Martin
2011-12-12 15:14   ` Dave Martin
2011-12-12 15:31     ` Rob Herring [this message]
2011-11-30 14:01 ` Shawn Guo
2011-11-30 14:03   ` Dave Martin
2011-11-30 14:26     ` Shawn Guo
2011-11-30 14:45       ` Dave Martin
2011-12-12 15:47 ` Uwe Kleine-König
2011-12-13 10:50   ` Dave Martin

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=4EE61E68.9050807@gmail.com \
    --to=robherring2@gmail.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).