From: plagnioj@jcrosoft•com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists•infradead.org
Subject: ARM: at-91: ARCH_AT91SAM9X5 went missing
Date: Wed, 13 Mar 2013 13:26:05 +0100 [thread overview]
Message-ID: <20130313122605.GE2001@game.jcrosoft.org> (raw)
In-Reply-To: <1363173747.3137.202.camel@x61.thuisdomein>
On 12:22 Wed 13 Mar , Paul Bolle wrote:
> On Wed, 2013-03-13 at 12:12 +0100, Nicolas Ferre wrote:
> > These ARCH_AT91xxx variables are not used anymore for pure Device Tree
> > SoCs (I mean: at91sam9x5, at91sam9n12, sama5d3 families). They are used
> > for non-DT SoCs and for chips that support both legacy board files and DT.
> > The old ARCH_AT91xxx symbols are selecting the corresponding SOC_AT91xxx
> > symbol.
> >
> > ARCH_AT91xxx in Kconfig that are specific to a particular SoC are going
> > to disappear as we tend to allow the compilation of a particular driver
> > for a wider range of configurations.
>
> So setting one of the SOC_* symbols will not generate the corresponding
> ARCH_* symbol, will it? To be specific, for the people entering the
> configuration from the new SOC_* side none of this is relevant anymore
> (this is all the stuff outside of arch/arm):
yes it's as when I prepare the at91 for dt support I split the code in two
world. The old style (one soc at a time) and the st multi soc
the ARCH_AT91xxx are still here as part of the code are still depending on
old style platform data and not converted to DT
but the ARCH_AT91SAM9x5 never exist at the mainline
and all the old style as now mark as deprecated and for removal
Best Regards,
J.
>
> drivers/misc/Kconfig:87: prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
> drivers/pcmcia/Kconfig:291: depends on PCMCIA && ARCH_AT91RM9200
> drivers/rtc/Kconfig:977: depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
> drivers/tty/serial/atmel_serial.c:268:#ifdef CONFIG_ARCH_AT91RM9200
> drivers/watchdog/Kconfig:127: depends on ARCH_AT91 && !ARCH_AT91RM9200
> drivers/misc/Kconfig:87: prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
> drivers/video/Kconfig:1026: depends on FB_ATMEL && ARCH_AT91SAM9261
> drivers/net/can/Kconfig:68: depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9X5
> drivers/rtc/Kconfig:991: prompt "RTT module Number" if ARCH_AT91SAM9263
> drivers/rtc/Kconfig:1000: range 0 3 if !ARCH_AT91SAM9263
> drivers/rtc/Kconfig:1001: range 0 15 if ARCH_AT91SAM9263
> drivers/usb/gadget/Kconfig:157: depends on AVR32 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
> drivers/usb/gadget/atmel_usba_udc.c:329:#if defined(CONFIG_ARCH_AT91SAM9RL)
> drivers/usb/gadget/atmel_usba_udc.c:349:#endif /* CONFIG_ARCH_AT91SAM9RL */
> drivers/mmc/host/Kconfig:305: depends on MMC_ATMELMCI && (AVR32 || ARCH_AT91SAM9G45) && DMA_ENGINE
> drivers/usb/gadget/Kconfig:157: depends on AVR32 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
> drivers/net/can/Kconfig:68: depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9X5
>
>
> Paul Bolle
>
next prev parent reply other threads:[~2013-03-13 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 10:48 ARM: at-91: ARCH_AT91SAM9X5 went missing Paul Bolle
2013-03-13 11:12 ` Nicolas Ferre
2013-03-13 11:22 ` Paul Bolle
2013-03-13 12:26 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2013-03-14 8:17 ` Paul Bolle
2013-03-14 8:30 ` Nicolas Ferre
2013-03-14 8:52 ` Paul Bolle
2013-03-13 12:30 ` Nicolas Ferre
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=20130313122605.GE2001@game.jcrosoft.org \
--to=plagnioj@jcrosoft$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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