linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] iommu: Remove OMAP IOVMM driver
Date: Mon, 21 Jul 2014 11:14:49 +0200	[thread overview]
Message-ID: <9251918.dhlInzvbvO@avalon> (raw)
In-Reply-To: <53C95124.1010902@ti.com>

Hi Suman, Joerg and Tony,

On Friday 18 July 2014 11:53:56 Suman Anna wrote:
> On 07/18/2014 05:49 AM, Laurent Pinchart wrote:
> > Hello,
> > 
> > The OMAP3 ISP driver was the only user of the OMAP IOVMM API. Now that is
> > has been ported to the DMA API, remove the unused virtual memory manager.
> > 
> > The removal is split in three patches to ease upstream merge. The first
> > patch removes the omap-iovmm driver, the second patch removes setting of
> > now unused platform data fields from arch code, and the last patch cleans
> > up the platform data structure.
> 
> Thanks for the revised series, it looks good. I have also tested the
> series on OMAP3, OMAP4 and OMAP5.
> 
> For the changes in the entire series,
> Acked-by: Suman Anna <s-anna@ti.com>

Thank you.

> > I'd like to get at least the first patch merged in v3.17. To avoid
> > splitting the series across three kernel versions, it would be nice to
> > also merge at least the second patch for v3.17. If there's no risk of
> > conflict everything could be merged in one go through the ARM SoC tree.
> > Otherwise a stable branch with patch 1/3 will be needed to base the arch
> > change on.
> > 
> > Joerg, Tony, how would you like to proceed ?

The v3.17 merge window is getting close, it's probably too late to merge patch 
2/3. Joerg, could you please take 1/3 in your tree for v3.17 ? 2/3 and 3/3 
would then get in v3.18. Tony, how would you like to proceed for those ?

> > Changes compared to v1:
> > 
> > - Fix OMAP_IOMMU_DEBUG dependency on OMAP_IOMMU
> > - Remove omap_iommu da_start and da_end fields
> > - Added patches 2/3 and 3/3
> > 
> > Laurent Pinchart (3):
> >   iommu/omap: Remove virtual memory manager
> >   ARM: omap: Don't set iommu pdata da_start and da_end fields
> >   iommu/omap: Remove platform data da_start and da_end fields
> >  
> >  arch/arm/mach-omap2/omap-iommu.c           |   2 -
> >  arch/arm/mach-omap2/omap_hwmod_3xxx_data.c |   4 -
> >  arch/arm/mach-omap2/omap_hwmod_44xx_data.c |   4 -
> >  drivers/iommu/Kconfig                      |  10 +-
> >  drivers/iommu/Makefile                     |   1 -
> >  drivers/iommu/omap-iommu-debug.c           | 114 -----
> >  drivers/iommu/omap-iommu.c                 |  13 -
> >  drivers/iommu/omap-iommu.h                 |   8 +-
> >  drivers/iommu/omap-iovmm.c                 | 791 ------------------------
> >  include/linux/omap-iommu.h                 |  37 +-
> >  include/linux/platform_data/iommu-omap.h   |   6 -
> >  11 files changed, 8 insertions(+), 982 deletions(-)
> >  delete mode 100644 drivers/iommu/omap-iovmm.c

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2014-07-21  9:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 10:49 [PATCH v2 0/3] iommu: Remove OMAP IOVMM driver Laurent Pinchart
2014-07-18 10:49 ` [PATCH v2 1/3] iommu/omap: Remove virtual memory manager Laurent Pinchart
2014-07-18 10:49 ` [PATCH v2 2/3] ARM: omap: Don't set iommu pdata da_start and da_end fields Laurent Pinchart
2014-07-18 10:49 ` [PATCH v2 3/3] iommu/omap: Remove platform data " Laurent Pinchart
2014-07-18 16:53 ` [PATCH v2 0/3] iommu: Remove OMAP IOVMM driver Suman Anna
2014-07-21  9:14   ` Laurent Pinchart [this message]
2014-07-21  9:33     ` Tony Lindgren
2014-07-21 18:15       ` Laurent Pinchart
2014-07-22  6:19         ` Tony Lindgren
2014-07-22 23:42           ` Laurent Pinchart
2014-07-23 13:52           ` Joerg Roedel
2014-07-23 14:00             ` Laurent Pinchart
2014-07-24  6:54               ` Tony Lindgren
2014-07-29 10:43               ` Joerg Roedel

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=9251918.dhlInzvbvO@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).