From: afzal@ti.com (Afzal Mohammed)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/15] OMAP-GPMC related cleanup for common zImage
Date: Fri, 5 Oct 2012 21:22:50 +0530 [thread overview]
Message-ID: <cover.1349450454.git.afzal@ti.com> (raw)
Hi,
This series cleans up omap-gpmc related code so that omap can
be a part of common zImage.
This series moves gpmc.h from plat-omap/include/plat to mach-omap2
so that header file is local.
Patches 1-4 qualifies as -rc material (assuming pull request
containing basic gpmc driver is accepted by Linus).
Patch 1 is an already posted one, has been pulled into this series.
Patches 5-6 removes necessity of cpu.h from onenand driver based
on Tony's suggestion.
Patches 7 & 8 cleans up the already moved platform data header files
to contain only platform data. Also gpmc-nand information is moved
to nand platform data header.
Patches 9-14 makes nand driver independent of gpmc header file
And the final patch localizes gpmc header.
This has been tested on omap3evm.
This series is available
@ git://gitorious.org/x0148406-public/linux-kernel.git gpmc-czimage-v1
and is based on
linux-next (next-20121005)
and is dependent on
http://marc.info/?l=linux-omap&m=134945131602622&w=2
Regards
Afzal
Afzal Mohammed (15):
ARM: OMAP2+: gpmc: annotate exit sections properly
mtd: onenand: omap: cleanup gpmc dependency
mtd: nand: omap: free region as per resource size
mtd: nand: omap: read nand using register address
ARM: OMAP2+: onenand: connected soc info in pdata
mtd: onenand: omap: use pdata info instead of cpu_is
ARM: OMAP2+: onenand: header cleanup
ARM: OMAP2+: nand: header cleanup
mtd: nand: omap: bring in gpmc nand macros
ARM: OMAP2+: nand: bch capability check
ARM: OMAP2+: gpmc: nand register helper bch update
mtd: nand: omap: handle gpmc bch[48]
ARM: OMAP2+: gpmc: remove exported nand functions
mtd: nand: omap: gpmc header removal
ARM: OMAP2+: gpmc: localize gpmc header
arch/arm/mach-omap2/board-2430sdp.c | 2 +-
arch/arm/mach-omap2/board-3430sdp.c | 2 +-
arch/arm/mach-omap2/board-apollon.c | 2 +-
arch/arm/mach-omap2/board-cm-t35.c | 5 +-
arch/arm/mach-omap2/board-cm-t3517.c | 5 +-
arch/arm/mach-omap2/board-devkit8000.c | 2 +-
arch/arm/mach-omap2/board-flash.c | 7 +-
arch/arm/mach-omap2/board-flash.h | 2 +-
arch/arm/mach-omap2/board-h4.c | 2 +-
arch/arm/mach-omap2/board-igep0020.c | 3 +-
arch/arm/mach-omap2/board-ldp.c | 2 +-
arch/arm/mach-omap2/board-n8x0.c | 1 +
arch/arm/mach-omap2/board-omap3beagle.c | 2 +-
arch/arm/mach-omap2/board-omap3logic.c | 2 +-
arch/arm/mach-omap2/board-omap3pandora.c | 3 +-
arch/arm/mach-omap2/board-omap3stalker.c | 2 +-
arch/arm/mach-omap2/board-omap3touchbook.c | 2 +-
arch/arm/mach-omap2/board-overo.c | 2 +-
arch/arm/mach-omap2/board-rm680.c | 3 +-
arch/arm/mach-omap2/board-rx51-peripherals.c | 3 +-
arch/arm/mach-omap2/board-rx51.c | 2 +-
arch/arm/mach-omap2/board-zoom-debugboard.c | 2 +-
arch/arm/mach-omap2/common-board-devices.c | 1 -
arch/arm/mach-omap2/gpmc-nand.c | 81 ++--
arch/arm/mach-omap2/gpmc-nand.h | 27 ++
arch/arm/mach-omap2/gpmc-onenand.c | 9 +-
arch/arm/mach-omap2/gpmc-onenand.h | 24 ++
arch/arm/mach-omap2/gpmc-smc91x.c | 2 +-
arch/arm/mach-omap2/gpmc-smsc911x.c | 2 +-
arch/arm/mach-omap2/gpmc.c | 459 +--------------------
.../{plat-omap/include/plat => mach-omap2}/gpmc.h | 59 +--
arch/arm/mach-omap2/pm34xx.c | 2 +-
arch/arm/mach-omap2/usb-tusb6010.c | 2 +-
drivers/mtd/nand/omap2.c | 121 +++++-
drivers/mtd/onenand/omap2.c | 9 +-
include/linux/platform_data/mtd-nand-omap2.h | 46 ++-
include/linux/platform_data/mtd-onenand-omap2.h | 20 +-
37 files changed, 317 insertions(+), 605 deletions(-)
create mode 100644 arch/arm/mach-omap2/gpmc-nand.h
create mode 100644 arch/arm/mach-omap2/gpmc-onenand.h
rename arch/arm/{plat-omap/include/plat => mach-omap2}/gpmc.h (70%)
--
1.7.12
next reply other threads:[~2012-10-05 15:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 15:52 Afzal Mohammed [this message]
2012-10-05 15:53 ` [PATCH 01/15] ARM: OMAP2+: gpmc: annotate exit sections properly Afzal Mohammed
2012-10-05 15:53 ` [PATCH 02/15] mtd: onenand: omap: cleanup gpmc dependency Afzal Mohammed
2012-10-05 15:53 ` [PATCH 03/15] mtd: nand: omap: free region as per resource size Afzal Mohammed
2012-10-05 15:53 ` [PATCH 04/15] mtd: nand: omap: read nand using register address Afzal Mohammed
2012-10-05 15:53 ` [PATCH 05/15] ARM: OMAP2+: onenand: connected soc info in pdata Afzal Mohammed
2012-10-05 15:54 ` [PATCH 06/15] mtd: onenand: omap: use pdata info instead of cpu_is Afzal Mohammed
2012-10-05 15:54 ` [PATCH 07/15] ARM: OMAP2+: onenand: header cleanup Afzal Mohammed
2012-10-05 15:54 ` [PATCH 08/15] ARM: OMAP2+: nand: " Afzal Mohammed
2012-10-05 15:54 ` [PATCH 09/15] mtd: nand: omap: bring in gpmc nand macros Afzal Mohammed
2012-10-05 15:54 ` [PATCH 10/15] ARM: OMAP2+: nand: bch capability check Afzal Mohammed
2012-10-05 15:54 ` [PATCH 11/15] ARM: OMAP2+: gpmc: nand register helper bch update Afzal Mohammed
2012-10-05 15:54 ` [PATCH 12/15] mtd: nand: omap: handle gpmc bch[48] Afzal Mohammed
2012-10-05 15:54 ` [PATCH 13/15] ARM: OMAP2+: gpmc: remove exported nand functions Afzal Mohammed
2012-10-05 15:54 ` [PATCH 14/15] mtd: nand: omap: gpmc header removal Afzal Mohammed
2012-10-05 15:54 ` [PATCH 15/15] ARM: OMAP2+: gpmc: localize gpmc header Afzal Mohammed
2012-10-08 5:39 ` [PATCH 00/15] OMAP-GPMC related cleanup for common zImage Mohammed, Afzal
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=cover.1349450454.git.afzal@ti.com \
--to=afzal@ti.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).