From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4 v3] s5pc1xx: support onenand driver
Date: Tue, 22 Sep 2009 09:48:42 -0500 [thread overview]
Message-ID: <4AB8E3CA.6060301@windriver.com> (raw)
In-Reply-To: <4AB8C4AB.4020105@samsung.com>
Minkyu Kang wrote:
> This patch includes the onenand driver for s5pc100
>
> Signed-off-by: Minkyu Kang <mk7.kang@samsung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
> Changes since v1:
> - move samsung_onenand.h to include/linux/mtd/
> - make C struct instead of base+offset
> - Remove the "1 &&" in while loop
>
> Changes since v2:
> - drop blank lines
> - adds some comments
> - modify to lower case letter in C struct
>
> drivers/mtd/onenand/Makefile | 1 +
> drivers/mtd/onenand/samsung.c | 622 +++++++++++++++++++++++++++++++++++
> include/linux/mtd/onenand.h | 1 +
> include/linux/mtd/onenand_regs.h | 4 +
> include/linux/mtd/samsung_onenand.h | 131 ++++++++
> 5 files changed, 759 insertions(+), 0 deletions(-)
> create mode 100644 drivers/mtd/onenand/samsung.c
> create mode 100644 include/linux/mtd/samsung_onenand.h
>
> diff --git a/drivers/mtd/onenand/Makefile b/drivers/mtd/onenand/Makefile
> index 1d35a57..2571df0 100644
> --- a/drivers/mtd/onenand/Makefile
> +++ b/drivers/mtd/onenand/Makefile
> @@ -26,6 +26,7 @@ include $(TOPDIR)/config.mk
> LIB := $(obj)libonenand.a
>
> COBJS-$(CONFIG_CMD_ONENAND) := onenand_uboot.o onenand_base.o onenand_bbt.o
> +COBJS-$(CONFIG_SAMSUNG_ONENAND) += samsung.o
>
> COBJS := $(COBJS-y)
> SRCS := $(COBJS:.o=.c)
> diff --git a/drivers/mtd/onenand/samsung.c b/drivers/mtd/onenand/samsung.c
> new file mode 100644
> index 0000000..5433f19
> --- /dev/null
> +++ b/drivers/mtd/onenand/samsung.c
> @@ -0,0 +1,622 @@
> +/*
> + * S3C64XX/S5PC100 OneNAND driver at U-Boot
> + *
> + * Copyright (C) 2008-2009 Samsung Electronics
> + * Kyungmin Park <kyungmin.park@samsung.com>
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License version 2 as
> + * published by the Free Software Foundation.
Add full GPL 2 copyright.
> + *
> + * Implementation:
> + * Emulate the pseudo BufferRAM
> + */
> +
<snip>
> +
> +#if defined(CONFIG_S3C64XX)
> +#define MAP_00 (0x0 << 24)
> +#define MAP_01 (0x1 << 24)
> +#define MAP_10 (0x2 << 24)
> +#define MAP_11 (0x3 << 24)
> +#elif defined(CONFIG_S5PC1XX)
> +#define MAP_00 (0x0 << 26)
> +#define MAP_01 (0x1 << 26)
> +#define MAP_10 (0x2 << 26)
> +#define MAP_11 (0x3 << 26)
> +#endif
This and other struct, #defines may be better handled in a H file.
Why did you include them all here?
Otherwise fine.
Just fix the copyright.
Tom
next prev parent reply other threads:[~2009-09-22 14:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 7:35 [U-Boot] [PATCH 2/4 v2] s5pc1xx: support onenand driver Minkyu Kang
2009-09-10 11:16 ` Wolfgang Denk
2009-09-15 2:40 ` Minkyu Kang
2009-09-22 12:35 ` [U-Boot] [PATCH 2/4 v3] " Minkyu Kang
2009-09-22 14:48 ` Tom [this message]
2009-09-23 10:49 ` Minkyu Kang
2009-09-23 23:46 ` Kyungmin Park
2009-09-24 1:17 ` Tom
2009-09-24 13:27 ` Wolfgang Denk
2009-09-28 17:55 ` Scott Wood
2009-10-01 8:20 ` [U-Boot] [PATCH 2/4 v4] " Minkyu Kang
2009-10-09 3:10 ` Minkyu Kang
2009-10-03 23:25 ` [U-Boot] [PATCH 2/4 v3] " Wolfgang Denk
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=4AB8E3CA.6060301@windriver.com \
--to=tom.rix@windriver.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