From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 14/17] mtd: onenand: remove s5pc100 related onenand codes
Date: Sat, 12 Jul 2014 00:12:34 -0700 [thread overview]
Message-ID: <20140712071234.GF23883@brian-ubuntu> (raw)
In-Reply-To: <1404163947-3105-15-git-send-email-kgene.kim@samsung.com>
+ linux-mtd (please CC for anything driver/mtd/*; see MAINTAINERS)
On Tue, Jul 01, 2014 at 06:32:24AM +0900, Kukjin Kim wrote:
> This patch removes s5pc100 related onenand codes because of no more
> support for S5PC100 SoC in mainline.
>
> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
> Cc: Kyungmin Park <kyungmin.park@samsung.com>
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Brian Norris <computersforpeace@gmail.com>
> ---
> drivers/mtd/onenand/Kconfig | 4 ++--
> drivers/mtd/onenand/samsung.c | 25 +------------------------
> 2 files changed, 3 insertions(+), 26 deletions(-)
>
> diff --git a/drivers/mtd/onenand/Kconfig b/drivers/mtd/onenand/Kconfig
> index ab26072..dcae2f6 100644
> --- a/drivers/mtd/onenand/Kconfig
> +++ b/drivers/mtd/onenand/Kconfig
> @@ -32,10 +32,10 @@ config MTD_ONENAND_OMAP2
>
> config MTD_ONENAND_SAMSUNG
> tristate "OneNAND on Samsung SOC controller support"
> - depends on ARCH_S3C64XX || ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS4
> + depends on ARCH_S3C64XX || ARCH_S5PV210 || ARCH_EXYNOS4
> help
> Support for a OneNAND flash device connected to an Samsung SOC.
> - S3C64XX/S5PC100 use command mapping method.
> + S3C64XX uses command mapping method.
> S5PC110/S5PC210 use generic OneNAND method.
>
> config MTD_ONENAND_OTP
> diff --git a/drivers/mtd/onenand/samsung.c b/drivers/mtd/onenand/samsung.c
> index efb819c..19cfb97 100644
> --- a/drivers/mtd/onenand/samsung.c
> +++ b/drivers/mtd/onenand/samsung.c
> @@ -10,7 +10,7 @@
> * published by the Free Software Foundation.
> *
> * Implementation:
> - * S3C64XX and S5PC100: emulate the pseudo BufferRAM
> + * S3C64XX: emulate the pseudo BufferRAM
> * S5PC110: use DMA
> */
>
> @@ -32,7 +32,6 @@
> enum soc_type {
> TYPE_S3C6400,
> TYPE_S3C6410,
> - TYPE_S5PC100,
> TYPE_S5PC110,
> };
>
> @@ -59,7 +58,6 @@ enum soc_type {
> #define MAP_11 (0x3)
>
> #define S3C64XX_CMD_MAP_SHIFT 24
> -#define S5PC100_CMD_MAP_SHIFT 26
>
> #define S3C6400_FBA_SHIFT 10
> #define S3C6400_FPA_SHIFT 4
> @@ -69,10 +67,6 @@ enum soc_type {
> #define S3C6410_FPA_SHIFT 6
> #define S3C6410_FSA_SHIFT 4
>
> -#define S5PC100_FBA_SHIFT 13
> -#define S5PC100_FPA_SHIFT 7
> -#define S5PC100_FSA_SHIFT 5
> -
> /* S5PC110 specific definitions */
> #define S5PC110_DMA_SRC_ADDR 0x400
> #define S5PC110_DMA_SRC_CFG 0x404
> @@ -195,11 +189,6 @@ static unsigned int s3c64xx_cmd_map(unsigned type, unsigned val)
> return (type << S3C64XX_CMD_MAP_SHIFT) | val;
> }
>
> -static unsigned int s5pc1xx_cmd_map(unsigned type, unsigned val)
> -{
> - return (type << S5PC100_CMD_MAP_SHIFT) | val;
> -}
> -
> static unsigned int s3c6400_mem_addr(int fba, int fpa, int fsa)
> {
> return (fba << S3C6400_FBA_SHIFT) | (fpa << S3C6400_FPA_SHIFT) |
> @@ -212,12 +201,6 @@ static unsigned int s3c6410_mem_addr(int fba, int fpa, int fsa)
> (fsa << S3C6410_FSA_SHIFT);
> }
>
> -static unsigned int s5pc100_mem_addr(int fba, int fpa, int fsa)
> -{
> - return (fba << S5PC100_FBA_SHIFT) | (fpa << S5PC100_FPA_SHIFT) |
> - (fsa << S5PC100_FSA_SHIFT);
> -}
> -
> static void s3c_onenand_reset(void)
> {
> unsigned long timeout = 0x10000;
> @@ -835,9 +818,6 @@ static void s3c_onenand_setup(struct mtd_info *mtd)
> } else if (onenand->type == TYPE_S3C6410) {
> onenand->mem_addr = s3c6410_mem_addr;
> onenand->cmd_map = s3c64xx_cmd_map;
> - } else if (onenand->type == TYPE_S5PC100) {
> - onenand->mem_addr = s5pc100_mem_addr;
> - onenand->cmd_map = s5pc1xx_cmd_map;
> } else if (onenand->type == TYPE_S5PC110) {
> /* Use generic onenand functions */
> this->read_bufferram = s5pc110_read_bufferram;
> @@ -1111,9 +1091,6 @@ static struct platform_device_id s3c_onenand_driver_ids[] = {
> .name = "s3c6410-onenand",
> .driver_data = TYPE_S3C6410,
> }, {
> - .name = "s5pc100-onenand",
> - .driver_data = TYPE_S5PC100,
> - }, {
> .name = "s5pc110-onenand",
> .driver_data = TYPE_S5PC110,
> }, { },
> --
> 1.7.10.4
>
next prev parent reply other threads:[~2014-07-12 7:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 21:32 [PATCH 00/17] ARM: S5P64X0, S5PC100: no more support in mainline Kukjin Kim
2014-06-30 13:34 ` Arnd Bergmann
2014-06-30 14:22 ` Thierry Reding
2014-06-30 14:31 ` Arnd Bergmann
2014-07-01 2:08 ` Kukjin Kim
2014-06-30 15:31 ` Tushar Behera
2014-07-01 2:08 ` Kukjin Kim
2014-06-30 21:32 ` [PATCH 02/17] gpio: samsung: remove s5p64x0 related gpio codes Kukjin Kim
2014-07-07 16:05 ` Linus Walleij
2014-06-30 21:32 ` [PATCH 03/17] spi: s3c64xx: remove s5p64x0 related spi codes Kukjin Kim
2014-06-30 21:32 ` [PATCH 04/17] ASoC: samsung: no more support for S5P6440 and S5P6450 SoCs Kukjin Kim
2014-06-30 21:32 ` [PATCH 05/17] pwm: samsung: remove s5p64x0 related pwm codes Kukjin Kim
2014-07-04 8:10 ` Tomasz Figa
2014-07-07 22:23 ` Kukjin Kim
2014-07-08 15:43 ` Tomasz Figa
2014-06-30 21:32 ` [PATCH 06/17] video: fbdev: s3c-fb: remove s5p64x0 related fimd codes Kukjin Kim
2014-07-01 2:04 ` Jingoo Han
2014-07-01 6:25 ` Tomi Valkeinen
2014-06-30 21:32 ` [PATCH 07/17] serial: samsung: no more support for S5P6440 and S5P6450 SoCs Kukjin Kim
2014-06-30 21:32 ` [PATCH 09/17] gpio: samsung: remov s5pc100 related gpio codes Kukjin Kim
2014-07-07 16:05 ` Linus Walleij
2014-06-30 21:32 ` [PATCH 10/17] spi: s3c64xx: remove s5pc100 related spi codes Kukjin Kim
2014-06-30 21:32 ` [PATCH 11/17] pwm: samsung: remove s5pc100 related pwm codes Kukjin Kim
2014-07-03 12:44 ` Tomasz Figa
2014-07-04 7:32 ` Kukjin Kim
2014-07-04 8:07 ` Tomasz Figa
2014-06-30 21:32 ` [PATCH 12/17] serial: samsung: no more support for S5PC100 SoC Kukjin Kim
2014-06-30 21:32 ` [PATCH 13/17] ata: pata_samsung_cf: removes s5pc100 related ata codes Kukjin Kim
2014-06-30 14:49 ` Tejun Heo
2014-06-30 21:32 ` [PATCH 14/17] mtd: onenand: remove s5pc100 related onenand codes Kukjin Kim
2014-07-12 7:12 ` Brian Norris [this message]
2014-06-30 21:32 ` [PATCH 15/17] video: fbdev: s3c-fb: remove s5pc100 related fimd and fb codes Kukjin Kim
2014-07-01 2:05 ` Jingoo Han
2014-06-30 21:32 ` [PATCH 16/17] [media] exynos4-is: removes s5pc100 related fimc codes Kukjin Kim
2014-06-30 14:03 ` Sylwester Nawrocki
2014-06-30 21:32 ` [PATCH 17/17] ASoC: Samsung: remove s5pc100 related codes Kukjin Kim
2014-07-14 18:05 ` Mark Brown
2014-07-02 18:02 ` [PATCH 00/17] ARM: S5P64X0, S5PC100: no more support in mainline Tomasz Figa
2014-07-02 22:46 ` Kukjin Kim
2014-07-03 3:35 ` Sachin Kamat
2014-07-04 8:43 ` Kukjin Kim
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=20140712071234.GF23883@brian-ubuntu \
--to=computersforpeace@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).