From: Daniel Mack <zonque@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-omap@vger.kernel.org, jon-hunter@ti.com, x0148406@ti.com,
tony@atomide.com, paul@pwsan.com, nsekhar@ti.com,
Daniel Mack <zonque@gmail.com>
Subject: [PATCH 0/4] RFC: OMAP GPMC bindings
Date: Mon, 22 Oct 2012 21:55:54 +0200 [thread overview]
Message-ID: <1350935758-9215-1-git-send-email-zonque@gmail.com> (raw)
This is a series of patches to support GPMC peripherals on OMAP boards.
Depends on Linus' master +
omap-next (branch omap-for-v3.8/cleanup-headers-gpmc)
The only supported peripheral for now is NAND, but other types would be
easy to add.
In order to make the gpmc driver the 'hub' for all sub-nodes, I had to
add some includes. I'm not particularily happy about the fact that there
are mutual references from gpmc.c to gpmc-nand.c now, but that was the
easiest way.
I successfully tested these patches on an AM33xx board to make NAND
work.
Comments welcome!
Thanks,
Daniel
Daniel Mack (4):
mtd: omap-nand: pass device_node in platform data
ARM: OMAP: gpmc: enable hwecc for AM33xx SoCs
ARM: OMAP: gpmc: don't create devices from initcall on DT
OMAP: mtd: gpmc: add DT bindings for GPMC timings and NAND
Documentation/devicetree/bindings/bus/gpmc.txt | 59 +++++++++
.../devicetree/bindings/mtd/gpmc-nand.txt | 65 +++++++++
arch/arm/mach-omap2/gpmc-nand.c | 2 +-
arch/arm/mach-omap2/gpmc.c | 146 +++++++++++++++++++++
drivers/mtd/nand/omap2.c | 4 +-
include/linux/platform_data/mtd-nand-omap2.h | 2 +
6 files changed, 276 insertions(+), 2 deletions(-)
create mode 100644 Documentation/devicetree/bindings/bus/gpmc.txt
create mode 100644 Documentation/devicetree/bindings/mtd/gpmc-nand.txt
--
1.7.11.7
WARNING: multiple messages have this Message-ID (diff)
From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] RFC: OMAP GPMC bindings
Date: Mon, 22 Oct 2012 21:55:54 +0200 [thread overview]
Message-ID: <1350935758-9215-1-git-send-email-zonque@gmail.com> (raw)
This is a series of patches to support GPMC peripherals on OMAP boards.
Depends on Linus' master +
omap-next (branch omap-for-v3.8/cleanup-headers-gpmc)
The only supported peripheral for now is NAND, but other types would be
easy to add.
In order to make the gpmc driver the 'hub' for all sub-nodes, I had to
add some includes. I'm not particularily happy about the fact that there
are mutual references from gpmc.c to gpmc-nand.c now, but that was the
easiest way.
I successfully tested these patches on an AM33xx board to make NAND
work.
Comments welcome!
Thanks,
Daniel
Daniel Mack (4):
mtd: omap-nand: pass device_node in platform data
ARM: OMAP: gpmc: enable hwecc for AM33xx SoCs
ARM: OMAP: gpmc: don't create devices from initcall on DT
OMAP: mtd: gpmc: add DT bindings for GPMC timings and NAND
Documentation/devicetree/bindings/bus/gpmc.txt | 59 +++++++++
.../devicetree/bindings/mtd/gpmc-nand.txt | 65 +++++++++
arch/arm/mach-omap2/gpmc-nand.c | 2 +-
arch/arm/mach-omap2/gpmc.c | 146 +++++++++++++++++++++
drivers/mtd/nand/omap2.c | 4 +-
include/linux/platform_data/mtd-nand-omap2.h | 2 +
6 files changed, 276 insertions(+), 2 deletions(-)
create mode 100644 Documentation/devicetree/bindings/bus/gpmc.txt
create mode 100644 Documentation/devicetree/bindings/mtd/gpmc-nand.txt
--
1.7.11.7
next reply other threads:[~2012-10-22 19:56 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 19:55 Daniel Mack [this message]
2012-10-22 19:55 ` [PATCH 0/4] RFC: OMAP GPMC bindings Daniel Mack
2012-10-22 19:55 ` [PATCH 1/4] mtd: omap-nand: pass device_node in platform data Daniel Mack
2012-10-22 19:55 ` Daniel Mack
2012-10-22 19:55 ` [PATCH 2/4] ARM: OMAP: gpmc: enable hwecc for AM33xx SoCs Daniel Mack
2012-10-22 19:55 ` Daniel Mack
2012-10-22 19:55 ` [PATCH 3/4] ARM: OMAP: gpmc: don't create devices from initcall on DT Daniel Mack
2012-10-22 19:55 ` Daniel Mack
2012-10-22 19:55 ` [PATCH 4/4] OMAP: mtd: gpmc: add DT bindings for GPMC timings and NAND Daniel Mack
2012-10-22 19:55 ` Daniel Mack
2012-10-24 23:27 ` Tony Lindgren
2012-10-24 23:27 ` Tony Lindgren
2012-10-24 23:31 ` Daniel Mack
2012-10-24 23:31 ` Daniel Mack
2012-10-29 8:10 ` Afzal Mohammed
2012-10-29 8:10 ` Afzal Mohammed
2012-10-29 11:15 ` Daniel Mack
2012-10-29 11:15 ` Daniel Mack
2012-10-29 11:28 ` Afzal Mohammed
2012-10-29 11:28 ` Afzal Mohammed
2012-10-29 12:32 ` Daniel Mack
2012-10-29 12:32 ` Daniel Mack
2012-10-29 12:56 ` Afzal Mohammed
2012-10-29 12:56 ` Afzal Mohammed
2012-10-25 1:28 ` Jon Hunter
2012-10-25 1:28 ` Jon Hunter
2012-10-25 8:00 ` Daniel Mack
2012-10-25 8:00 ` Daniel Mack
2012-10-25 13:16 ` Jon Hunter
2012-10-25 13:16 ` Jon Hunter
2012-10-29 8:09 ` Afzal Mohammed
2012-10-29 8:09 ` Afzal Mohammed
2012-10-25 1:53 ` Jon Hunter
2012-10-25 1:53 ` Jon Hunter
2012-10-25 9:43 ` Daniel Mack
2012-10-25 9:43 ` Daniel Mack
2012-10-25 13:22 ` Jon Hunter
2012-10-25 13:22 ` Jon Hunter
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=1350935758-9215-1-git-send-email-zonque@gmail.com \
--to=zonque@gmail.com \
--cc=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=paul@pwsan.com \
--cc=tony@atomide.com \
--cc=x0148406@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.