Hi Stephen,
Our patches with DMA-mapping framework redesign proposal have been hanging for over a month with just a few comments. We would like to go further in the development, but first I would like to ask You to give them a try in the linux-next kernel.
For everyone interested in this patch series, here is the relevant thread: https://lkml.org/lkml/2011/12/23/97
If there are any problems with our git tree, please contact Marek Szyprowski m.szyprowski@samsung.com or alternatively Kyungmin Park kyungmin.park@samsung.com.
The following changes since commit 62aa2b537c6f5957afd98e29f96897419ed5ebab:
Linux 3.3-rc2 (2012-01-31 13:31:54 -0800)
are available in the git repository at: git://git.infradead.org/users/kmpark/linux-samsung dma-mapping-next
Andrzej Pietrasiewicz (9): X86: adapt for dma_map_ops changes MIPS: adapt for dma_map_ops changes PowerPC: adapt for dma_map_ops changes IA64: adapt for dma_map_ops changes SPARC: adapt for dma_map_ops changes Alpha: adapt for dma_map_ops changes SH: adapt for dma_map_ops changes Microblaze: adapt for dma_map_ops changes Unicore32: adapt for dma_map_ops changes
Marek Szyprowski (5): common: dma-mapping: introduce alloc_attrs and free_attrs methods common: dma-mapping: remove old alloc_coherent and free_coherent methods common: dma-mapping: introduce mmap method common: DMA-mapping: add WRITE_COMBINE attribute common: DMA-mapping: add NON-CONSISTENT attribute
Documentation/DMA-attributes.txt | 19 +++++++++++++++++++ arch/alpha/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/alpha/kernel/pci-noop.c | 10 ++++++---- arch/alpha/kernel/pci_iommu.c | 10 ++++++---- arch/ia64/hp/common/sba_iommu.c | 11 ++++++----- arch/ia64/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/ia64/kernel/pci-swiotlb.c | 9 +++++---- arch/ia64/sn/pci/pci_dma.c | 9 +++++---- arch/microblaze/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/microblaze/kernel/dma.c | 10 ++++++---- arch/mips/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/mips/mm/dma-default.c | 8 ++++---- arch/powerpc/include/asm/dma-mapping.h | 24 ++++++++++++++++-------- arch/powerpc/kernel/dma-iommu.c | 10 ++++++---- arch/powerpc/kernel/dma-swiotlb.c | 4 ++-- arch/powerpc/kernel/dma.c | 10 ++++++---- arch/powerpc/kernel/ibmebus.c | 10 ++++++---- arch/powerpc/platforms/cell/iommu.c | 16 +++++++++------- arch/powerpc/platforms/ps3/system-bus.c | 13 +++++++------ arch/sh/include/asm/dma-mapping.h | 28 ++++++++++++++++++---------- arch/sh/kernel/dma-nommu.c | 4 ++-- arch/sh/mm/consistent.c | 6 ++++-- arch/sparc/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/sparc/kernel/iommu.c | 10 ++++++---- arch/sparc/kernel/ioport.c | 18 ++++++++++-------- arch/sparc/kernel/pci_sun4v.c | 9 +++++---- arch/unicore32/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/unicore32/mm/dma-swiotlb.c | 4 ++-- arch/x86/include/asm/dma-mapping.h | 26 ++++++++++++++++---------- arch/x86/kernel/amd_gart_64.c | 11 ++++++----- arch/x86/kernel/pci-calgary_64.c | 9 +++++---- arch/x86/kernel/pci-dma.c | 3 ++- arch/x86/kernel/pci-nommu.c | 6 +++--- arch/x86/kernel/pci-swiotlb.c | 12 +++++++----- arch/x86/xen/pci-swiotlb-xen.c | 4 ++-- drivers/iommu/amd_iommu.c | 10 ++++++---- drivers/iommu/intel-iommu.c | 9 +++++---- drivers/xen/swiotlb-xen.c | 5 +++-- include/linux/dma-attrs.h | 2 ++ include/linux/dma-mapping.h | 13 +++++++++---- include/linux/swiotlb.h | 6 ++++-- include/xen/swiotlb-xen.h | 6 ++++-- lib/swiotlb.c | 5 +++-- 43 files changed, 305 insertions(+), 182 deletions(-)
Best regards Marek Szyprowski Samsung Poland R&D Center
Hi Marek,
On Fri, 10 Feb 2012 19:32:17 +0100 Marek Szyprowski m.szyprowski@samsung.com wrote:
Our patches with DMA-mapping framework redesign proposal have been hanging for over a month with just a few comments. We would like to go further in the development, but first I would like to ask You to give them a try in the linux-next kernel.
For everyone interested in this patch series, here is the relevant thread: https://lkml.org/lkml/2011/12/23/97
If there are any problems with our git tree, please contact Marek Szyprowski m.szyprowski@samsung.com or alternatively Kyungmin Park kyungmin.park@samsung.com.
The following changes since commit 62aa2b537c6f5957afd98e29f96897419ed5ebab:
Linux 3.3-rc2 (2012-01-31 13:31:54 -0800)
are available in the git repository at: git://git.infradead.org/users/kmpark/linux-samsung dma-mapping-next
I have added this from today.
Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgment of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have been: * submitted under GPL v2 (or later) and include the Contributor's Signed-off-by, * posted to the relevant mailing list, * reviewed by you (or another maintainer of your subsystem tree), * successfully unit tested, and * destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.
Hi Stephen,
On Monday, February 13, 2012 1:22 AM Stephen Rothwell wrote:
On Fri, 10 Feb 2012 19:32:17 +0100 Marek Szyprowski m.szyprowski@samsung.com wrote:
Our patches with DMA-mapping framework redesign proposal have been hanging for over a month with just a few comments. We would like to go further in the development, but first I would like to ask You to give them a try in the linux-next kernel.
For everyone interested in this patch series, here is the relevant thread: https://lkml.org/lkml/2011/12/23/97
If there are any problems with our git tree, please contact Marek Szyprowski m.szyprowski@samsung.com or alternatively Kyungmin Park kyungmin.park@samsung.com.
The following changes since commit 62aa2b537c6f5957afd98e29f96897419ed5ebab:
Linux 3.3-rc2 (2012-01-31 13:31:54 -0800)
are available in the git repository at: git://git.infradead.org/users/kmpark/linux-samsung dma-mapping-next
I have added this from today.
Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgment of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have been: * submitted under GPL v2 (or later) and include the Contributor's Signed-off-by, * posted to the relevant mailing list, * reviewed by you (or another maintainer of your subsystem tree), * successfully unit tested, and * destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.
I've prepared a separate git repository for all our dma-mapping related works. Could you update your database with the new entry? From now the dma-mapping updates will be available at:
git://git.linaro.org/people/mszyprowski/linux-dma-mapping.git dma-mapping-next
Best regards
Hi Marek,
On Wed, 28 Mar 2012 10:04:08 +0200 Marek Szyprowski m.szyprowski@samsung.com wrote:
I've prepared a separate git repository for all our dma-mapping related works. Could you update your database with the new entry? From now the dma-mapping updates will be available at:
git://git.linaro.org/people/mszyprowski/linux-dma-mapping.git dma-mapping-next
I have changed to use that new tree.
linaro-mm-sig@lists.linaro.org