All of lore.kernel.org
 help / color / mirror / Atom feed
From: <ritesh.harjani@gmail.com>
To: <catalin.marinas@arm.com>, <Will.Deacon@arm.com>,
	<m.szyprowski@samsung.com>, <rmk@arm.linux.org.uk>,
	<gregkh@linuxfoundation.org>
Cc: <ritesh.harjani@gmail.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/1] device.h: Move out arch independent dma_iommu_mapping struct
Date: Wed, 4 Jun 2014 13:41:45 +0530	[thread overview]
Message-ID: <1401869506-48129-1-git-send-email-ritesh.harjani@gmail.com> (raw)

From: Ritesh Harjani <ritesh.harjani@gmail.com>

There has been various ongoing discussions on making arm iommu's dma-mapping
stuff to be common code which is arch independent[1].
Current users of this code will be arm and arm64, but later other archs
can start utilizing this as well.

Based on these discussion there has been work going on to refactor common
arch independent code of arm iommu's dma-mapping to lib/iommu-helper.c [2].

Since now dma_iommu_mapping stuff will be arch independent, so it make sense
to move out struct dma_iommu_mapping *mapping variable from arch/arm/*/device.h 
to include/linux/device.h as a first step [3].
Also, to move out complete structure definition of dma_iommu_mapping 
to include/linux/iommu-helper.h


Links:
[1]: https://www.mail-archive.com/iommu@lists.linux-foundation.org/msg03458.html
[2]: http://www.spinics.net/lists/arm-kernel/msg336343.html
[3]: http://www.spinics.net/lists/arm-kernel/msg336682.html

Ritesh Harjani (1):
  device.h: arm,dma-iommu: Move out dma_iommu_mapping struct

 arch/arm/Kconfig                          |  4 ++++
 arch/arm/include/asm/device.h             |  9 ---------
 arch/arm/include/asm/dma-iommu.h          | 16 +---------------
 arch/arm/mm/dma-mapping.c                 | 20 ++++++++++----------
 drivers/gpu/drm/exynos/exynos_drm_iommu.c | 10 +++++-----
 include/linux/device.h                    |  4 ++++
 include/linux/iommu-helper.h              | 22 ++++++++++++++++++++++
 7 files changed, 46 insertions(+), 39 deletions(-)

-- 
1.8.1.3


WARNING: multiple messages have this Message-ID (diff)
From: ritesh.harjani@gmail.com (ritesh.harjani at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1] device.h: Move out arch independent dma_iommu_mapping struct
Date: Wed, 4 Jun 2014 13:41:45 +0530	[thread overview]
Message-ID: <1401869506-48129-1-git-send-email-ritesh.harjani@gmail.com> (raw)

From: Ritesh Harjani <ritesh.harjani@gmail.com>

There has been various ongoing discussions on making arm iommu's dma-mapping
stuff to be common code which is arch independent[1].
Current users of this code will be arm and arm64, but later other archs
can start utilizing this as well.

Based on these discussion there has been work going on to refactor common
arch independent code of arm iommu's dma-mapping to lib/iommu-helper.c [2].

Since now dma_iommu_mapping stuff will be arch independent, so it make sense
to move out struct dma_iommu_mapping *mapping variable from arch/arm/*/device.h 
to include/linux/device.h as a first step [3].
Also, to move out complete structure definition of dma_iommu_mapping 
to include/linux/iommu-helper.h


Links:
[1]: https://www.mail-archive.com/iommu at lists.linux-foundation.org/msg03458.html
[2]: http://www.spinics.net/lists/arm-kernel/msg336343.html
[3]: http://www.spinics.net/lists/arm-kernel/msg336682.html

Ritesh Harjani (1):
  device.h: arm,dma-iommu: Move out dma_iommu_mapping struct

 arch/arm/Kconfig                          |  4 ++++
 arch/arm/include/asm/device.h             |  9 ---------
 arch/arm/include/asm/dma-iommu.h          | 16 +---------------
 arch/arm/mm/dma-mapping.c                 | 20 ++++++++++----------
 drivers/gpu/drm/exynos/exynos_drm_iommu.c | 10 +++++-----
 include/linux/device.h                    |  4 ++++
 include/linux/iommu-helper.h              | 22 ++++++++++++++++++++++
 7 files changed, 46 insertions(+), 39 deletions(-)

-- 
1.8.1.3

             reply	other threads:[~2014-06-04  8:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  8:11 ritesh.harjani [this message]
2014-06-04  8:11 ` [PATCH 0/1] device.h: Move out arch independent dma_iommu_mapping struct ritesh.harjani at gmail.com
2014-06-04  8:11 ` [PATCH 1/1] device.h: arm,dma-iommu: Move out " ritesh.harjani
2014-06-04  8:11   ` [PATCH 1/1] device.h: arm, dma-iommu: " ritesh.harjani at gmail.com
2014-06-04 17:51   ` [PATCH 1/1] device.h: arm,dma-iommu: " Greg KH
2014-06-04 17:51     ` Greg KH
2014-06-04 18:46     ` Ritesh Harjani
2014-06-04 18:46       ` [PATCH 1/1] device.h: arm, dma-iommu: " Ritesh Harjani
2014-06-04 18:59       ` [PATCH 1/1] device.h: arm,dma-iommu: " Greg KH
2014-06-04 18:59         ` Greg KH
2014-06-05  9:18         ` Ritesh Harjani
2014-06-05  9:18           ` [PATCH 1/1] device.h: arm, dma-iommu: " Ritesh Harjani
2014-06-04 19:01       ` [PATCH 1/1] device.h: arm,dma-iommu: " Greg KH
2014-06-04 19:01         ` Greg KH

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=1401869506-48129-1-git-send-email-ritesh.harjani@gmail.com \
    --to=ritesh.harjani@gmail.com \
    --cc=Will.Deacon@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=rmk@arm.linux.org.uk \
    /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.