From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Olof Johansson <olof@lixom.net>
Cc: Arnd Bergmann <arnd@arndb.de>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [GIT PULL] at91: soc for 3.10 #2
Date: Wed, 3 Apr 2013 09:22:48 +0200 [thread overview]
Message-ID: <515BD8C8.5060701@atmel.com> (raw)
In-Reply-To: <CAOesGMiy7q-xbc0SN78d7cvZmLgywy1PH7_Srw_=pzErSkrt-g@mail.gmail.com>
On 04/03/2013 02:26 AM, Olof Johansson :
> On Wed, Mar 27, 2013 at 12:01 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Wednesday 27 March 2013, Nicolas Ferre wrote:
>>
>>> ----------------------------------------------------------------
>>> Introduction of new Atmel Cortex-A5: SAMA5D3 family.
>>> - Modify AT91 Kconfig to plit ARMv4/5 and ARMv7 arch
>>> - Modify PMC driver (clocks)
>>> - Core SAMA5 support
>>> - Board file, DT files and defconfig
>>
>> Looks really good. Olof said he'd take over merging tomorrow,
>> so I'll leave it for him.
>>
>>> ----------------------------------------------------------------
>>> Ludovic Desroches (6):
>>> ARM: at91: change name template in AT91_SOC_START macro
>>> ARM: at91: add AT91_SAM9_TIME entry to select at91sam926x_time.c compilation
>>> ARM: at91: introduce the core type choice to split ARMv4/5 and ARMv7 arch
>>> ARM: at91: introduce SAMA5 support
>>> ARM: at91: dt: add device tree files for SAMA5D3 family
>>> ARM: at91: add defconfig for SAMA5
>>
>> There is one obvious change that would be nice to include here,
>> can you add this on top (either Nicolas or Olof)?
>>
>> 8<---------
>> Subject: ARM: at91: make ATAGS support conditional on CONFIG_ATAGS
>>
>> We have the global CONFIG_ATAGS symbol that is used to determine
>> whether ATAGS based boot is possible or not. Since we are
>> splitting out the legacy boards from the main Kconfig on at91,
>> we can use that symbol to easily hide the old options.
>>
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>>
>> diff --git a/arch/arm/mach-at91/Kconfig b/arch/arm/mach-at91/Kconfig
>> index 0280238..119a0a4 100644
>> --- a/arch/arm/mach-at91/Kconfig
>> +++ b/arch/arm/mach-at91/Kconfig
>> @@ -137,8 +137,9 @@ config SOC_AT91SAM9N12
>> Select this if you are using Atmel's AT91SAM9N12 SoC.
>>
>> # ----------------------------------------------------------
>> -
>> +if ATAGS
>> source arch/arm/mach-at91/Kconfig.non_dt
>> +endif
>> endif # SOC_SAM_V4_V5
>>
>> comment "Generic Board Type"
>
> Actually, it's not that simple. With this patch, I get:
>
> arch/arm/Kconfig:1841:error: recursive dependency detected!
> arch/arm/Kconfig:1841: symbol USE_OF is selected by MACH_AT91RM9200_DT
> arch/arm/mach-at91/Kconfig:147: symbol MACH_AT91RM9200_DT depends on
> SOC_AT91RM9200
> arch/arm/mach-at91/Kconfig:74: symbol SOC_AT91RM9200 is selected by
> ARCH_AT91RM9200
> arch/arm/mach-at91/Kconfig.non_dt:12: symbol ARCH_AT91RM9200 is part
> of choice <choice>
> arch/arm/mach-at91/Kconfig.non_dt:6: choice <choice> contains symbol <choice>
> arch/arm/mach-at91/Kconfig.non_dt:6: choice <choice> contains symbol ATAGS
> arch/arm/Kconfig:1850: symbol ATAGS depends on USE_OF
>
> Also, USE_OF isn't set at that point (it's controlled by the next
> section), so it can't be used as a replacement.
>
> Also, isn't it a bit backwards in the first place to first set ATAGS
> vs no-ATAGS, and then get to choose what hardware you want to build
> for?
True, I was thinking it was a common pattern.
> I'll take off the last patch from the branch and re-merge it (since I
> hadn't pushed it out yet), the above can be sorted out separately.
Thanks Olof for taking care about this! We will come back on this later
or simply decide that it is not worth it / not logical...
Best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2013-04-03 7:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 8:52 [GIT PULL] at91: soc for 3.10 #2 Nicolas Ferre
2013-03-27 19:01 ` Arnd Bergmann
2013-03-28 8:57 ` Nicolas Ferre
2013-04-03 0:26 ` Olof Johansson
2013-04-03 7:22 ` Nicolas Ferre [this message]
2013-04-03 10:02 ` Arnd Bergmann
2013-03-28 10:38 ` [GIT PULL v2] " Nicolas Ferre
2013-04-02 17:48 ` Olof Johansson
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=515BD8C8.5060701@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=marc.zyngier@arm.com \
--cc=olof@lixom.net \
--cc=plagnioj@jcrosoft.com \
/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