From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/6] at91: get rid of long standing work around CONFIG_AT91_LEGACY
Date: Wed, 30 Oct 2013 15:18:16 +0100 [thread overview]
Message-ID: <1383142702-9782-1-git-send-email-andreas.devel@googlemail.com> (raw)
This series cleans up the CONFIG_AT91_LEGACY mess. It was introduced for
transition to C struct SoC peripheral access. The transision is almost done
but introduced another CONFIG_ATMEL_LEGACY define for some GPIO cleanup which
was never finished.
There are currently just two users of the CONFIG_AT91_LEGACY left, while they
doesn't need to define it cause in fact they just need the CONFIG_ATMEL_LEGACY
define.
Therefore remove first the not longer needed CONFIG_AT91_LEGACY define now and
in a second step also the CONFIG_ATMEL_LEGACY.
The CONFIG_ATMEL_LEGACY is mostly GPIO related. There is currently a dicussion
about new API for the at91 (g)pio accessors at in [1]. Please comment there.
[1] http://article.gmane.org/gmane.comp.boot-loaders.u-boot/172727
Andreas Bie?mann (6):
video: remove AT91 legacy API from bus_vcxk
i2c: switch from AT91 legacy to ATMEL legacy
at91sam9m10g45ek: remove unused CONFIG_AT91_LEGACY
snapper9260: remove unused AT91_LEGACY
net: remove unused CONFIG_AT91_LEGACY
at91: remove all occourances of CONFIG_AT91_LEGACY
arch/arm/include/asm/arch-at91/at91_pio.h | 33 ------------
arch/arm/include/asm/arch-at91/at91_pit.h | 16 ------
arch/arm/include/asm/arch-at91/at91_pmc.h | 51 ++----------------
arch/arm/include/asm/arch-at91/at91_spi.h | 2 +-
arch/arm/include/asm/arch-at91/at91_wdt.h | 21 --------
arch/arm/include/asm/arch-at91/at91cap9.h | 69 -------------------------
arch/arm/include/asm/arch-at91/at91sam9_smc.h | 60 ---------------------
doc/README.at91-soc | 7 +++
drivers/i2c/soft_i2c.c | 2 +-
drivers/net/at91_emac.c | 9 ----
drivers/video/bus_vcxk.c | 15 ------
include/configs/at91sam9m10g45ek.h | 1 -
include/configs/snapper9260.h | 1 -
include/i2c.h | 2 +-
14 files changed, 15 insertions(+), 274 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-10-30 14:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 14:18 Andreas Bießmann [this message]
2013-10-30 14:18 ` [U-Boot] [PATCH 1/6] video: remove AT91 legacy API from bus_vcxk Andreas Bießmann
2013-11-04 15:12 ` Jens Scharsig
2013-11-04 15:21 ` Anatolij Gustschin
2013-11-13 21:21 ` [U-Boot] [U-Boot,1/6] " Andreas Bießmann
2013-10-30 14:18 ` [U-Boot] [PATCH 2/6] i2c: switch from AT91 legacy to ATMEL legacy Andreas Bießmann
2013-10-31 5:08 ` Heiko Schocher
2013-11-13 21:21 ` [U-Boot] [U-Boot,2/6] " Andreas Bießmann
2013-10-30 14:18 ` [U-Boot] [PATCH 3/6] at91sam9m10g45ek: remove unused CONFIG_AT91_LEGACY Andreas Bießmann
2013-10-31 3:18 ` Bo Shen
2013-11-13 21:22 ` [U-Boot] [U-Boot,3/6] " Andreas Bießmann
2013-10-30 14:18 ` [U-Boot] [PATCH 4/6] snapper9260: remove unused AT91_LEGACY Andreas Bießmann
2013-11-13 21:22 ` [U-Boot] [U-Boot,4/6] " Andreas Bießmann
2013-10-30 14:18 ` [U-Boot] [PATCH 5/6] net: remove unused CONFIG_AT91_LEGACY Andreas Bießmann
2013-11-13 21:22 ` [U-Boot] [U-Boot,5/6] " Andreas Bießmann
2013-10-30 14:18 ` [U-Boot] [PATCH 6/6] at91: remove all occourances of CONFIG_AT91_LEGACY Andreas Bießmann
2013-11-13 21:22 ` [U-Boot] [U-Boot,6/6] " Andreas Bießmann
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=1383142702-9782-1-git-send-email-andreas.devel@googlemail.com \
--to=andreas.devel@googlemail.com \
--cc=u-boot@lists.denx.de \
/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