From: Fernando Guzman Lugo <x0095840@ti.com>
To: <Hiroshi.DOYU@nokia.com>
Cc: <felipe.contreras@nokia.com>, <david.cohen@nokia.com>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
Fernando Guzman Lugo <x0095840@ti.com>
Subject: [PATCHv4 0/4] iovmm: fixes for iovmm module
Date: Tue, 19 Oct 2010 21:48:48 -0500 [thread overview]
Message-ID: <1287542932-14206-1-git-send-email-x0095840@ti.com> (raw)
Version 4:
* Changes in "iommu: create new api to set valid da range"
- Validate range for fixed address.
- Change way of change boundaries to avoid possible overflow
instead of style :
start + bytes >= end which start + end can overflow
use style:
end - start < bytes
Version 3:
* change patch 2 base on Felipe Contreras' comments,
now it uses min_t and I deleted some blank lines.
* patch "create new api to set valid da range" is base on
"iovmm: IVA2 MMU range is from 0x11000000 to 0xFFFFFFFF"
patch and on Hiroshi's comments and now it is added to
this set.
Version 2:
* Removed "iovmm: fixes for iovmm module" that patch was already
sent.
* Modified "iovmm: fix roundup for next area and end check for the
last area" patch, base on Davin Cohen's comments and rename it
to a proper name that describes what it is doing now.
Fernando Guzman Lugo (4):
iovmm: no gap checking for fixed address
iovmm: add superpages support to fixed da address
iovmm: replace __iounmap with omap_iounmap
iommu: create new api to set valid da range
arch/arm/plat-omap/include/plat/iommu.h | 3 +
arch/arm/plat-omap/iommu.c | 29 +++++++++++
arch/arm/plat-omap/iovmm.c | 81 +++++++++++++++++-------------
3 files changed, 78 insertions(+), 35 deletions(-)
next reply other threads:[~2010-10-20 2:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 2:48 Fernando Guzman Lugo [this message]
2010-10-20 2:48 ` [PATCHv4 1/4] iovmm: no gap checking for fixed address Fernando Guzman Lugo
2010-10-20 2:48 ` [PATCHv4 2/4] iovmm: add superpages support to fixed da address Fernando Guzman Lugo
2010-10-20 2:48 ` [PATCHv4 3/4] iovmm: replace __iounmap with omap_iounmap Fernando Guzman Lugo
2010-10-20 2:48 ` [PATCHv4 4/4] iommu: create new api to set valid da range Fernando Guzman Lugo
2010-10-20 8:35 ` felipe.contreras
2010-10-20 8:45 ` Hiroshi DOYU
2010-10-20 8:58 ` Felipe Contreras
2010-10-20 9:26 ` Hiroshi DOYU
2010-10-20 15:26 ` Guzman Lugo, Fernando
2010-10-20 15:22 ` Guzman Lugo, Fernando
2010-10-20 16:26 ` Felipe Contreras
2010-10-22 9:59 ` Felipe Contreras
2010-10-22 16:23 ` Guzman Lugo, Fernando
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=1287542932-14206-1-git-send-email-x0095840@ti.com \
--to=x0095840@ti.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=david.cohen@nokia.com \
--cc=felipe.contreras@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®