Re: [PATCH v2 0/3] iommu: Remove OMAP IOVMM driver

2014-07-29 Thread Joerg Roedel
On Wed, Jul 23, 2014 at 04:00:47PM +0200, Laurent Pinchart wrote:
 Thank you. Assuming there's currently no conflict to be resolved, I believe 
 the easiest would be for both you and Tony to merge my branch in your trees.

Okay, I applied the patches to my arm/omap branch. I will push them out
today.


Joerg

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v2 0/3] iommu: Remove OMAP IOVMM driver

2014-07-24 Thread Tony Lindgren
* Laurent Pinchart laurent.pinch...@ideasonboard.com [140723 07:02]:
 Hi Joerg,
 
 On Wednesday 23 July 2014 15:52:17 Joerg Roedel wrote:
  On Mon, Jul 21, 2014 at 11:19:29PM -0700, Tony Lindgren wrote:
Tony, is there still time to get this (and especially patch 2/3, which
touches arch/ code) in v3.17 ?
   
   Yes as long as Joerg is OK to merge that branch in :)
  
  Fine with me, I can take only patch 1 or all 3 into my arm/omap branch,
  given Tony's Acked-by.
  
  Then you guys can merge in this branch wherever you want :)
 
 Thank you. Assuming there's currently no conflict to be resolved, I believe 
 the easiest would be for both you and Tony to merge my branch in your trees.

Yes please merge that branch via the IOMMU tree, I only need to merge it
if I see merge conflicts with it.

Regards,

Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v2 0/3] iommu: Remove OMAP IOVMM driver

2014-07-23 Thread Laurent Pinchart
Hi Joerg,

On Wednesday 23 July 2014 15:52:17 Joerg Roedel wrote:
 On Mon, Jul 21, 2014 at 11:19:29PM -0700, Tony Lindgren wrote:
   Tony, is there still time to get this (and especially patch 2/3, which
   touches arch/ code) in v3.17 ?
  
  Yes as long as Joerg is OK to merge that branch in :)
 
 Fine with me, I can take only patch 1 or all 3 into my arm/omap branch,
 given Tony's Acked-by.
 
 Then you guys can merge in this branch wherever you want :)

Thank you. Assuming there's currently no conflict to be resolved, I believe 
the easiest would be for both you and Tony to merge my branch in your trees.

-- 
Regards,

Laurent Pinchart

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v2 0/3] iommu: Remove OMAP IOVMM driver

2014-07-23 Thread Joerg Roedel
On Mon, Jul 21, 2014 at 11:19:29PM -0700, Tony Lindgren wrote:
  Tony, is there still time to get this (and especially patch 2/3, which 
  touches 
  arch/ code) in v3.17 ?
 
 Yes as long as Joerg is OK to merge that branch in :)

Fine with me, I can take only patch 1 or all 3 into my arm/omap branch,
given Tony's Acked-by.

Then you guys can merge in this branch wherever you want :)

Cheers,

Joerg

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v2 0/3] iommu: Remove OMAP IOVMM driver

2014-07-22 Thread Tony Lindgren
* Laurent Pinchart laurent.pinch...@ideasonboard.com [140721 11:17]:
 Hi Tony and Joerg,
 
 On Monday 21 July 2014 02:33:36 Tony Lindgren wrote:
  * Laurent Pinchart laurent.pinch...@ideasonboard.com [140721 02:16]:
   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-a...@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 ?
 
  How about Joerg maybe do an immutable branch against v3.16-rc1
  with just these three patches and merge it into your tree?
  
  That way I too can merge the minimal branch in if there are conflics.
  If that works for Joerg, then for arch/arm/*omap* changes:
  
  Acked-by: Tony Lindgren t...@atomide.com
 
 I've created an immutable branch (or, rather, immutable until the changes 
 reach mainline, at which point I will remove the branch) on top of v3.16-rc1 
 with just the three patches from this series. You can find it at.
 
   git://linuxtv.org/pinchartl/media.git omap/iommu
 
 Tony, is there still time to get this (and especially patch 2/3, which 
 touches 
 arch/ code) in v3.17 ?

Yes as long as Joerg is OK to merge that branch in :)

Regards,

Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v2 0/3] iommu: Remove OMAP IOVMM driver

2014-07-22 Thread Laurent Pinchart
Hi Joerg,

(Your attention is kindly requested in time for v3.17, please see below)

On Monday 21 July 2014 23:19:29 Tony Lindgren wrote:
 * Laurent Pinchart laurent.pinch...@ideasonboard.com [140721 11:17]:
  On Monday 21 July 2014 02:33:36 Tony Lindgren wrote:
  * Laurent Pinchart laurent.pinch...@ideasonboard.com [140721 02:16]:
  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-a...@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 ?
  
  How about Joerg maybe do an immutable branch against v3.16-rc1
  with just these three patches and merge it into your tree?
  
  That way I too can merge the minimal branch in if there are conflics.
  If that works for Joerg, then for arch/arm/*omap* changes:
  
  Acked-by: Tony Lindgren t...@atomide.com
  
  I've created an immutable branch (or, rather, immutable until the changes
  reach mainline, at which point I will remove the branch) on top of
  v3.16-rc1 with just the three patches from this series. You can find it
  at.
  
  git://linuxtv.org/pinchartl/media.git omap/iommu
  
  Tony, is there still time to get this (and especially patch 2/3, which
  touches arch/ code) in v3.17 ?
 
 Yes as long as Joerg is OK to merge that branch in :)

Are you ? :-)

-- 
Regards,

Laurent Pinchart

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v2 0/3] iommu: Remove OMAP IOVMM driver

2014-07-21 Thread Tony Lindgren
* Laurent Pinchart laurent.pinch...@ideasonboard.com [140721 02:16]:
 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-a...@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 ?

How about Joerg maybe do an immutable branch against v3.16-rc1
with just these three patches and merge it into your tree?

That way I too can merge the minimal branch in if there are conflics.
If that works for Joerg, then for arch/arm/*omap* changes:

Acked-by: Tony Lindgren t...@atomide.com

If the above is too complicated, then how about Laurent resend patches
2 - 3 once the dependencies have cleared so I can pick them up. This
is assuming nothing breaks with patchs 2 - 3 missing naturally :)

Regards,

Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v2 0/3] iommu: Remove OMAP IOVMM driver

2014-07-21 Thread Laurent Pinchart
Hi Tony and Joerg,

On Monday 21 July 2014 02:33:36 Tony Lindgren wrote:
 * Laurent Pinchart laurent.pinch...@ideasonboard.com [140721 02:16]:
  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-a...@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 ?

 How about Joerg maybe do an immutable branch against v3.16-rc1
 with just these three patches and merge it into your tree?
 
 That way I too can merge the minimal branch in if there are conflics.
 If that works for Joerg, then for arch/arm/*omap* changes:
 
 Acked-by: Tony Lindgren t...@atomide.com

I've created an immutable branch (or, rather, immutable until the changes 
reach mainline, at which point I will remove the branch) on top of v3.16-rc1 
with just the three patches from this series. You can find it at.

git://linuxtv.org/pinchartl/media.git omap/iommu

Tony, is there still time to get this (and especially patch 2/3, which touches 
arch/ code) in v3.17 ?

 If the above is too complicated, then how about Laurent resend patches
 2 - 3 once the dependencies have cleared so I can pick them up. This
 is assuming nothing breaks with patchs 2 - 3 missing naturally :)

-- 
Regards,

Laurent Pinchart

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[PATCH v2 0/3] iommu: Remove OMAP IOVMM driver

2014-07-18 Thread Laurent Pinchart
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.

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 ?

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

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v2 0/3] iommu: Remove OMAP IOVMM driver

2014-07-18 Thread Suman Anna
Hi Laurent,

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-a...@ti.com

regards
Suman

 
 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 ?
 
 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
 

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html