From: Jens Scharsig <esw@bus-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/6] video: remove AT91 legacy API from bus_vcxk
Date: Mon, 4 Nov 2013 16:12:11 +0100 [thread overview]
Message-ID: <5277B94B.5010202@bus-elektronik.de> (raw)
In-Reply-To: <1383142702-9782-2-git-send-email-andreas.devel@googlemail.com>
Am 2013-10-30 15:18, schrieb Andreas Bie?mann:
> Signed-off-by: Andreas Bie?mann <andreas.devel@googlemail.com>
> ---
> drivers/video/bus_vcxk.c | 15 ---------------
> 1 file changed, 15 deletions(-)
>
> diff --git a/drivers/video/bus_vcxk.c b/drivers/video/bus_vcxk.c
> index 0138bca..60a5cc5 100644
> --- a/drivers/video/bus_vcxk.c
> +++ b/drivers/video/bus_vcxk.c
> @@ -20,7 +20,6 @@ vu_long *vcxk_bws_long = ((vu_long *) (CONFIG_SYS_VCXK_BASE));
> #ifndef VCBITMASK
> #define VCBITMASK(bitno) (0x0001 << (bitno % 16))
> #endif
> -#ifndef CONFIG_AT91_LEGACY
> at91_pio_t *pio = (at91_pio_t *) AT91_PIO_BASE;
> #define VCXK_INIT_PIN(PORT, PIN, DDR, I0O1) \
> do { \
> @@ -37,20 +36,6 @@ at91_pio_t *pio = (at91_pio_t *) AT91_PIO_BASE;
> #define VCXK_ACKNOWLEDGE \
> (!(readl(&pio->CONFIG_SYS_VCXK_ACKNOWLEDGE_PORT.pdsr) & \
> CONFIG_SYS_VCXK_ACKNOWLEDGE_PIN))
> -#else
> - #define VCXK_INIT_PIN(PORT, PIN, DDR, I0O1) \
> - ((AT91PS_PIO) PORT)->PIO_PER = PIN; \
> - ((AT91PS_PIO) PORT)->DDR = PIN; \
> - ((AT91PS_PIO) PORT)->PIO_MDDR = PIN; \
> - if (!I0O1) ((AT91PS_PIO) PORT)->PIO_PPUER = PIN;
> -
> - #define VCXK_SET_PIN(PORT, PIN) ((AT91PS_PIO) PORT)->PIO_SODR = PIN;
> - #define VCXK_CLR_PIN(PORT, PIN) ((AT91PS_PIO) PORT)->PIO_CODR = PIN;
> -
> - #define VCXK_ACKNOWLEDGE \
> - (!(((AT91PS_PIO) CONFIG_SYS_VCXK_ACKNOWLEDGE_PORT)->\
> - PIO_PDSR & CONFIG_SYS_VCXK_ACKNOWLEDGE_PIN))
> -#endif
> #elif defined(CONFIG_MCF52x2)
> #include <asm/m5282.h>
> #ifndef VCBITMASK
>
Acked-by: Jens Scharsig (BuS Elektronik) <esw@bus-elektronik.de>
next prev parent reply other threads:[~2013-11-04 15:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 14:18 [U-Boot] [PATCH 0/6] at91: get rid of long standing work around CONFIG_AT91_LEGACY Andreas Bießmann
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 [this message]
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=5277B94B.5010202@bus-elektronik.de \
--to=esw@bus-elektronik.de \
--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