From patchwork Wed Apr 12 05:21:25 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Suman Anna X-Patchwork-Id: 97282 Delivered-To: patch@linaro.org Received: by 10.140.109.52 with SMTP id k49csp114978qgf; Tue, 11 Apr 2017 22:21:48 -0700 (PDT) X-Received: by 10.84.229.3 with SMTP id b3mr80812889plk.190.1491974508623; Tue, 11 Apr 2017 22:21:48 -0700 (PDT) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z95si8495582plh.321.2017.04.11.22.21.48; Tue, 11 Apr 2017 22:21:48 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-omap-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@ti.com; spf=pass (google.com: best guess record for domain of linux-omap-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-omap-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752776AbdDLFVq (ORCPT + 3 others); Wed, 12 Apr 2017 01:21:46 -0400 Received: from lelnx193.ext.ti.com ([198.47.27.77]:35274 "EHLO lelnx193.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752738AbdDLFVn (ORCPT ); Wed, 12 Apr 2017 01:21:43 -0400 Received: from dflxv15.itg.ti.com ([128.247.5.124]) by lelnx193.ext.ti.com (8.15.1/8.15.1) with ESMTP id v3C5LYYw018185; Wed, 12 Apr 2017 00:21:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ti.com; s=ti-com-17Q1; t=1491974494; bh=CZJRT70OGIZfuvZ/mti9dVAQq0eX270+la7S7rWbZJw=; h=From:To:CC:Subject:Date; b=k7AVS3FxPnhbqbAHLIelSWQh99Yy5DuM1y8S5UiQYDjDzuOw9GQun45WAszFIXlqj Wzl4AoC5V+6uyB1Zn96nnVCzW8n+1aE460QcOXWC/ZjDoyHvCZuA42U1RoLGJEcBNq ec8jbRb32Zjqg6R7VZbHDzNTlBEELFPDNaWzVGXY= Received: from DLEE70.ent.ti.com (dlee70.ent.ti.com [157.170.170.113]) by dflxv15.itg.ti.com (8.14.3/8.13.8) with ESMTP id v3C5LYT0027054; Wed, 12 Apr 2017 00:21:34 -0500 Received: from dlep32.itg.ti.com (157.170.170.100) by DLEE70.ent.ti.com (157.170.170.113) with Microsoft SMTP Server id 14.3.294.0; Wed, 12 Apr 2017 00:21:33 -0500 Received: from legion.dal.design.ti.com (legion.dal.design.ti.com [128.247.22.53]) by dlep32.itg.ti.com (8.14.3/8.13.8) with ESMTP id v3C5LX8S017099; Wed, 12 Apr 2017 00:21:33 -0500 Received: from localhost (irmo.am.dhcp.ti.com [128.247.83.68]) by legion.dal.design.ti.com (8.11.7p1+Sun/8.11.7) with ESMTP id v3C5LX304055; Wed, 12 Apr 2017 00:21:33 -0500 (CDT) From: Suman Anna To: Joerg Roedel CC: , Laurent Pinchart , Suman Anna , , Subject: [PATCH v3 0/7] iommu/omap: Add support for iommu-groups and 'struct iommu_device' Date: Wed, 12 Apr 2017 00:21:25 -0500 Message-ID: <20170412052132.14406-1-s-anna@ti.com> X-Mailer: git-send-email 2.12.0 MIME-Version: 1.0 Sender: linux-omap-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-omap@vger.kernel.org Hi Joerg, I have taken the liberty of refreshing the series you have posted based on my testing and review comments. My unit tests are passing now with the series. I have summarized the changes below and also outlined the changes in each patch. Laurent, I cannot test the OMAP3 ISP, so request you to verify that the OMAP3ISP driver functionality is maintained. I have created the last patch separately for now since it's a separate subsystem, but ideally I think it should go with the patch that adds the iommu-group support. I am not sure how we want to merge this patch. Changes in v3: * Added 3 new patches - The first patch now results in the OMAP IOMMU devices being probed before the callbacks kick in. This allowed me to go back and use the patches from v1 where the IOMMU groups are added in probe. - The second patch drops the non-DT IOMMU device support so that the name can be dropped from the platform data as well. - Patch 7 fixes the OMAP3ISP driver after the addition of the IOMMU group support. * Squashed the "iommu/omap: Set dev->archdata.iommu = NULL in omap_iommu_remove_device" patch into Patch 4 * Failure path cleanups in patches 4, 5 and 6 Changes in v2: * Dropped patch 2 and moved device-link and group-handling to attach/detach_dev call-backs for now. Joerg Roedel (4): iommu/omap: Move data structures to omap-iommu.h iommu/omap: Store iommu_dev pointer in arch_data iommu/omap: Make use of 'struct iommu_device' iommu/omap: Add iommu-group support Suman Anna (3): iommu/omap: Register driver before setting IOMMU ops iommu/omap: Drop legacy-style device support [media] omap3isp: Remove iommu_group related code drivers/iommu/omap-iommu.c | 190 ++++++++++++++++++++----------- drivers/iommu/omap-iommu.h | 34 ++++++ drivers/media/platform/omap3isp/isp.c | 17 --- drivers/media/platform/omap3isp/isp.h | 1 - include/linux/platform_data/iommu-omap.h | 20 ---- 5 files changed, 156 insertions(+), 106 deletions(-) -- 2.12.0 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html