From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org
Subject: [PATCH 0/3] omap_device implementation, and HSMMC example
Date: Fri, 05 Jun 2009 04:30:37 -0600 [thread overview]
Message-ID: <20090605102716.13544.65328.stgit@localhost.localdomain> (raw)
Hello,
This patch series implements the first public version of the
omap_device code. The basic point of this code is to extend the
platform_device code with some features that are suited to OMAP code.
Most of these features concern device initialization, resource enumeration,
and power management.
The series consists of the core code and data structures, along
with an example HSMMC conversion for OMAP2430 and OMAP34xx.
The omap_device code is initially intended for use with OMAP2+
chips. It depends on the omap_hwmod patch series posted earlier -- each
omap_device structure is connected to one or more omap_hwmod structures.
A slightly different approach is perhaps best in the long run;
either to extend platform_device with subarchitecture-specific
hooks to call these functions perhaps along the lines of Magnus
Damm's recent proposal, or to replace platform_device/platform_bus with
an omap_device/omap_bus layer.
More detailed descriptions are found in each individual patch
description.
Boot-tested on OMAP3 Beagle and 3430SDP. Compile-tested on 2430SDP and
N800. The code has only been lightly tested, so there are likely to be
bugs -- patches and other feedback are welcome and solicited.
- Paul
---
omap_device
text data bss dec hex filename
3417637 194016 104080 3715733 38b295 vmlinux.omap3beagle.orig
3420233 194016 104080 3718329 38bcb9 vmlinux.omap3beagle
Paul Walmsley (3):
OMAP2/3 MMC: initial conversion to omap_device
OMAP: MMC (core): split device registration by OMAP variant
OMAP2/3/4 core: create omap_device layer
arch/arm/mach-omap1/devices.c | 41 ++
arch/arm/mach-omap2/devices.c | 104 +++-
arch/arm/mach-omap2/mmc-twl4030.c | 12
arch/arm/plat-omap/Makefile | 6
arch/arm/plat-omap/devices.c | 50 --
arch/arm/plat-omap/include/mach/mmc.h | 11
arch/arm/plat-omap/include/mach/omap_device.h | 140 +++++
arch/arm/plat-omap/omap_device.c | 654 +++++++++++++++++++++++++
drivers/mmc/host/omap_hsmmc.c | 99 ++--
9 files changed, 974 insertions(+), 143 deletions(-)
create mode 100644 arch/arm/plat-omap/include/mach/omap_device.h
create mode 100644 arch/arm/plat-omap/omap_device.c
next reply other threads:[~2009-06-05 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 10:30 Paul Walmsley [this message]
2009-06-05 10:30 ` [PATCH 1/3] OMAP2/3/4 core: create omap_device layer Paul Walmsley
2009-06-05 10:30 ` [PATCH 2/3] OMAP: MMC (core): split device registration by OMAP variant Paul Walmsley
2009-06-05 10:30 ` [PATCH 3/3] OMAP2/3 MMC: initial conversion to omap_device Paul Walmsley
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=20090605102716.13544.65328.stgit@localhost.localdomain \
--to=paul@pwsan.com \
--cc=linux-omap@vger.kernel.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 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.