From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: Greg Kroah-Hartman <gregkh@suse.de>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Omar Ramirez Luna <omar.ramirez@ti.com>,
Fernando Guzman Lugo <x0095840@ti.com>,
Ohad Ben-Cohen <ohad@wizery.com>, Nishanth Menon <nm@ti.com>,
lkml <linux-kernel@vger.kernel.org>,
devel <devel@driverdev.osuosl.org>
Subject: [PATCH v4 0/6] staging tidspbridge: iommu migration
Date: Thu, 28 Apr 2011 10:31:46 -0500 [thread overview]
Message-ID: <1304004712-8487-1-git-send-email-omar.ramirez@ti.com> (raw)
DO-NOT-APPLY to staging yet.
Rework and rebase of the previous set of patches for iommu migration[1].
Reorganized the patches to avoid several iterations to change the same code.
Patches were tested with an OMAP3630 board, with both, basic samples and
gst-dsp; these are dependant on patch:
"OMAP: iovmm: fix SW flags passed by user"[2].
[1] http://bit.ly/lUxbRO
[2] http://bit.ly/mgSrr8
Fernando Guzman Lugo (3):
staging: tidspbridge: remove custom mmu code
staging: tidspbridge: remove dmm module
staging: tidspbridge: decouple mmu functions from regular code
Omar Ramirez Luna (3):
staging: tidspbridge: introduce mapping search based on device
address
staging: tidspbridge: replace custom mmu for omap iommu framework
staging: tidspbridge: mapping support when SG_CHAIN is not defined
drivers/staging/tidspbridge/Kconfig | 11 +
drivers/staging/tidspbridge/Makefile | 7 +-
drivers/staging/tidspbridge/core/_deh.h | 5 +-
drivers/staging/tidspbridge/core/_tiomap.h | 19 +-
drivers/staging/tidspbridge/core/dsp_mmu.c | 396 +++++++
drivers/staging/tidspbridge/core/io_sm.c | 181 +---
drivers/staging/tidspbridge/core/tiomap3430.c | 1087 +++-----------------
drivers/staging/tidspbridge/core/tiomap3430_pwr.c | 6 +-
drivers/staging/tidspbridge/core/tiomap_io.c | 14 +-
drivers/staging/tidspbridge/core/ue_deh.c | 115 +--
drivers/staging/tidspbridge/hw/EasiGlobal.h | 41 -
drivers/staging/tidspbridge/hw/MMUAccInt.h | 76 --
drivers/staging/tidspbridge/hw/MMURegAcM.h | 225 ----
drivers/staging/tidspbridge/hw/hw_defs.h | 58 -
drivers/staging/tidspbridge/hw/hw_mmu.c | 562 ----------
drivers/staging/tidspbridge/hw/hw_mmu.h | 163 ---
.../tidspbridge/include/dspbridge/cfgdefs.h | 1 -
.../staging/tidspbridge/include/dspbridge/dev.h | 24 -
.../staging/tidspbridge/include/dspbridge/dmm.h | 75 --
.../staging/tidspbridge/include/dspbridge/drv.h | 13 -
.../tidspbridge/include/dspbridge/dsp_mmu.h | 33 +
.../tidspbridge/include/dspbridge/dspdefs.h | 44 -
.../tidspbridge/include/dspbridge/dspioctl.h | 7 -
.../staging/tidspbridge/include/dspbridge/proc.h | 46 -
drivers/staging/tidspbridge/pmgr/dev.c | 63 +--
drivers/staging/tidspbridge/pmgr/dmm.c | 533 ----------
drivers/staging/tidspbridge/pmgr/dspapi.c | 36 +-
drivers/staging/tidspbridge/rmgr/drv.c | 14 -
drivers/staging/tidspbridge/rmgr/drv_interface.c | 2 -
drivers/staging/tidspbridge/rmgr/node.c | 57 +-
drivers/staging/tidspbridge/rmgr/proc.c | 224 +---
31 files changed, 684 insertions(+), 3454 deletions(-)
create mode 100644 drivers/staging/tidspbridge/core/dsp_mmu.c
delete mode 100644 drivers/staging/tidspbridge/hw/EasiGlobal.h
delete mode 100644 drivers/staging/tidspbridge/hw/MMUAccInt.h
delete mode 100644 drivers/staging/tidspbridge/hw/MMURegAcM.h
delete mode 100644 drivers/staging/tidspbridge/hw/hw_defs.h
delete mode 100644 drivers/staging/tidspbridge/hw/hw_mmu.c
delete mode 100644 drivers/staging/tidspbridge/hw/hw_mmu.h
delete mode 100644 drivers/staging/tidspbridge/include/dspbridge/dmm.h
create mode 100644 drivers/staging/tidspbridge/include/dspbridge/dsp_mmu.h
delete mode 100644 drivers/staging/tidspbridge/pmgr/dmm.c
next reply other threads:[~2011-04-28 15:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 15:31 Omar Ramirez Luna [this message]
2011-04-28 15:31 ` [PATCH v4 1/6] staging: tidspbridge: introduce mapping search based on device address Omar Ramirez Luna
2011-04-28 15:31 ` [PATCH v4 2/6] staging: tidspbridge: replace custom mmu for omap iommu framework Omar Ramirez Luna
2011-04-28 15:31 ` [PATCH v4 3/6] staging: tidspbridge: mapping support when SG_CHAIN is not defined Omar Ramirez Luna
2011-04-28 15:31 ` [PATCH v4 4/6] staging: tidspbridge: remove custom mmu code Omar Ramirez Luna
2011-04-28 15:31 ` [PATCH v4 5/6] staging: tidspbridge: remove dmm module Omar Ramirez Luna
2011-04-28 15:31 ` [PATCH v4 6/6] staging: tidspbridge: decouple mmu functions from regular code Omar Ramirez Luna
2011-05-03 17:55 ` [PATCH v4 0/6] staging tidspbridge: iommu migration Greg KH
2011-05-03 20:34 ` Ramirez Luna, Omar
2011-05-03 20:18 ` Arnd Bergmann
2011-05-03 20:48 ` Ramirez Luna, Omar
2011-05-04 13:01 ` Arnd Bergmann
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=1304004712-8487-1-git-send-email-omar.ramirez@ti.com \
--to=omar.ramirez@ti.com \
--cc=devel@driverdev.osuosl.org \
--cc=felipe.contreras@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=ohad@wizery.com \
--cc=x0095840@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox