From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 0/4] mtd/NAND: Support for FSMC controller
Date: Mon, 7 May 2012 10:19:46 +0200 [thread overview]
Message-ID: <201205071019.46296.sr@denx.de> (raw)
In-Reply-To: <cover.1336374946.git.amit.virdi@st.com>
Hi Scott,
On Monday 07 May 2012 09:26:05 Amit Virdi wrote:
> This patchset adds support for ST's FSMC controller. In the current u-boot,
> a SPEAr specific driver exists for FSMC controller. This patchset adds a
> full fledged driver that can be used across multiple platforms and removes
> the obsolete SPEAr specific driver.
>
> V1 -> V2
> - Defined CONFIG_SYS_NAND_SELF_INIT and did the related changes
> - Modified the error index calculation process
> - Modified newly erased page read algorithm
> - Initialized the badblockbits index to 7
> - Improved fsmc_bch8_correct_data() implementation
>
> Vipin KUMAR (4):
> ARM: Define change_bit routine
> mtd/NAND: Add FSMC driver support
> SPEAr: Configure FSMC driver for NAND interface
> mtd/NAND: Remove obsolete SPEAr specific NAND drivers
>
> arch/arm/include/asm/arch-spear/hardware.h | 8 +-
> arch/arm/include/asm/arch-spear/spr_nand.h | 57 ----
> arch/arm/include/asm/bitops.h | 11 +-
> board/spear/spear300/spear300.c | 14 +-
> board/spear/spear310/spear310.c | 14 +-
> board/spear/spear320/spear320.c | 13 +-
> board/spear/spear600/spear600.c | 14 +-
> drivers/mtd/nand/Makefile | 1 +
> drivers/mtd/nand/fsmc_nand.c | 484 ++++++++++++++++++++++++++++
> drivers/mtd/nand/spr_nand.c | 124 -------
> include/configs/spear-common.h | 3 +-
> include/configs/spear3xx.h | 4 +
> include/configs/spear6xx.h | 3 +
> include/linux/mtd/fsmc_nand.h | 110 +++++++
> 14 files changed, 653 insertions(+), 207 deletions(-)
> delete mode 100644 arch/arm/include/asm/arch-spear/spr_nand.h
> create mode 100644 drivers/mtd/nand/fsmc_nand.c
> delete mode 100644 drivers/mtd/nand/spr_nand.c
> create mode 100644 include/linux/mtd/fsmc_nand.h
Scott, are you okay with this patchset? If yes, how should we handle
this patch series. As its NAND related it should go through your
git repository. But it also touches the SPEAr board files and config
headers. And other pending SPEAr related patches depend on this patchset.
Perhaps its easiest if I would collect all pending SPEAr patches
and push them upstream via my staging repository (if nobody objects)?
What do you think?
Thanks,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
next prev parent reply other threads:[~2012-05-07 8:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 7:26 [U-Boot] [PATCH V2 0/4] mtd/NAND: Support for FSMC controller Amit Virdi
2012-05-07 7:26 ` [U-Boot] [PATCH V2 1/4] ARM: Define change_bit routine Amit Virdi
2012-05-07 7:26 ` [U-Boot] [PATCH V2 2/4] mtd/NAND: Add FSMC driver support Amit Virdi
2012-05-15 21:14 ` Scott Wood
2012-05-16 10:41 ` Amit Virdi
2012-05-16 11:05 ` Amit Virdi
2012-05-16 11:31 ` Amit Virdi
2012-05-16 16:02 ` Scott Wood
2012-05-17 11:21 ` Amit Virdi
2012-05-07 7:26 ` [U-Boot] [PATCH V2 3/4] SPEAr: Configure FSMC driver for NAND interface Amit Virdi
2012-05-07 7:26 ` [U-Boot] [PATCH V2 4/4] mtd/NAND: Remove obsolete SPEAr specific NAND drivers Amit Virdi
2012-05-07 8:19 ` Stefan Roese [this message]
2012-05-14 13:49 ` [U-Boot] [PATCH V2 0/4] mtd/NAND: Support for FSMC controller Stefan Roese
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=201205071019.46296.sr@denx.de \
--to=sr@denx.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