All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Joerg Roedel <Joerg.Roedel@amd.com>,
	Arnd Bergmann <arnd@arndb.de>,
	iommu@lists.linux-foundation.org
Subject: Re: [PATCH v2 0/7] omap: iommu migration, relocation and cleanups
Date: Thu, 25 Aug 2011 19:03:48 +0300	[thread overview]
Message-ID: <20110825160348.GZ4996@atomide.com> (raw)
In-Reply-To: <1314205694-28935-1-git-send-email-ohad@wizery.com>

* Ohad Ben-Cohen <ohad@wizery.com> [110824 19:36]:
> 1. Migrate OMAP's iommu driver to the generic IOMMU API, and move it
> to the dedicated iommu folder.
> 
> 2. Fix omap3isp appropriately so it doesn't break.
> 
> 3. Adapt OMAP's iovmm appropriately as well, because omap3isp still relies
> on it. The plan is eventually to remove iovmm and replace it with the
> upcoming IOMMU-based generic DMA-API. Move iovmm to the iommu folder too;
> it belongs there more than it belongs in the OMAP folders.
> 
> 4. Start cleaning up OMAP's iommu components towards the end goal, where
>     1) omap-iommu no longer exports public API (and instead provides its
>        entire functionality via the generic IOMMU API).
>     2) omap-iovmm is removed.
> 
> Tested on OMAP3 (with omap3isp) and OMAP4 (with rpmsg/remoteproc).

Glad to see this, thanks for doing this! For all the patches:

Acked-by: Tony Lindgren <tony@atomide.com>

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] omap: iommu migration, relocation and cleanups
Date: Thu, 25 Aug 2011 19:03:48 +0300	[thread overview]
Message-ID: <20110825160348.GZ4996@atomide.com> (raw)
In-Reply-To: <1314205694-28935-1-git-send-email-ohad@wizery.com>

* Ohad Ben-Cohen <ohad@wizery.com> [110824 19:36]:
> 1. Migrate OMAP's iommu driver to the generic IOMMU API, and move it
> to the dedicated iommu folder.
> 
> 2. Fix omap3isp appropriately so it doesn't break.
> 
> 3. Adapt OMAP's iovmm appropriately as well, because omap3isp still relies
> on it. The plan is eventually to remove iovmm and replace it with the
> upcoming IOMMU-based generic DMA-API. Move iovmm to the iommu folder too;
> it belongs there more than it belongs in the OMAP folders.
> 
> 4. Start cleaning up OMAP's iommu components towards the end goal, where
>     1) omap-iommu no longer exports public API (and instead provides its
>        entire functionality via the generic IOMMU API).
>     2) omap-iovmm is removed.
> 
> Tested on OMAP3 (with omap3isp) and OMAP4 (with rpmsg/remoteproc).

Glad to see this, thanks for doing this! For all the patches:

Acked-by: Tony Lindgren <tony@atomide.com>

  parent reply	other threads:[~2011-08-25 16:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 17:08 [PATCH v2 0/7] omap: iommu migration, relocation and cleanups Ohad Ben-Cohen
2011-08-24 17:08 ` Ohad Ben-Cohen
2011-08-24 17:08 ` [PATCH v2 1/7] omap: iommu: migrate to the generic IOMMU API Ohad Ben-Cohen
2011-08-24 17:08   ` Ohad Ben-Cohen
2011-08-24 17:08 ` [PATCH v2 2/7] omap: iommu/iovmm: move to dedicated iommu folder Ohad Ben-Cohen
2011-08-24 17:08   ` Ohad Ben-Cohen
2011-08-24 17:08 ` [PATCH v2 3/7] omap: iommu: stop exporting local functions Ohad Ben-Cohen
2011-08-24 17:08   ` Ohad Ben-Cohen
2011-08-24 17:08 ` [PATCH v2 4/7] omap: iommu: PREFETCH_IOTLB cleanup Ohad Ben-Cohen
2011-08-24 17:08   ` Ohad Ben-Cohen
2011-08-24 17:08 ` [PATCH v2 5/7] omap: iovmm: remove unused functionality Ohad Ben-Cohen
2011-08-24 17:08   ` Ohad Ben-Cohen
2011-08-24 17:08 ` [PATCH v2 6/7] omap: iommu: remove unused exported API Ohad Ben-Cohen
2011-08-24 17:08   ` Ohad Ben-Cohen
2011-08-24 17:08 ` [PATCH v2 7/7] omap: iommu: omapify 'struct iommu' and exposed API Ohad Ben-Cohen
2011-08-24 17:08   ` Ohad Ben-Cohen
2011-08-25 16:03 ` Tony Lindgren [this message]
2011-08-25 16:03   ` [PATCH v2 0/7] omap: iommu migration, relocation and cleanups Tony Lindgren
2011-08-26 11:25 ` Roedel, Joerg
2011-08-26 11:25   ` Roedel, Joerg
2011-08-26 12:21   ` Ohad Ben-Cohen
2011-08-26 12:21     ` Ohad Ben-Cohen

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=20110825160348.GZ4996@atomide.com \
    --to=tony@atomide.com \
    --cc=Hiroshi.DOYU@nokia.com \
    --cc=Joerg.Roedel@amd.com \
    --cc=arnd@arndb.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=ohad@wizery.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.