From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 0/2] Fix dma mapping when the cache is coherent
Date: Thu, 21 Apr 2016 01:02:29 +0200 [thread overview]
Message-ID: <877ffrx4sa.fsf@free-electrons.com> (raw)
In-Reply-To: <CAPv3WKe2S1qbSByOgUABRcnTVoW-ad1guSSNsmPuFWJ8-W5sOg@mail.gmail.com> (Marcin Wojtas's message of "Sat, 16 Apr 2016 17:27:33 +0200")
Hi Marcin,
On sam., avril 16 2016, Marcin Wojtas <mw@semihalf.com> wrote:
> Hi Gregory,
>
> You can re-add my tested-by. Hang is no longer a problem with your
> patch during my test of neta.
The patch was already submitted in the Russell King's Patch Tracking
System, so I can't add the tested-by on them, but I am sure it will help
these pacthes to be merged.
Thanks,
Gregory
>
> Best regards,
> Marcin
>
> 2016-04-12 17:31 GMT+02:00 Gregory CLEMENT <gregory.clement@free-electrons.com>:
>> Hi,
>>
>> These two patches fixes the dma mapping functions when the system is
>> cache coherent. The first one allows to fix an issue we have on Armada
>> 375/38x with the PL310 that's why it is tagged for stable too.
>>
>> Thanks,
>>
>> Gregory
>>
>> PS: the mailing list was missing in the recipient list of the v7. It
>> was a mistake and I realized it only now. If needed I can repost it
>> with the few exchange we had with Russell King.
>>
>>
>> Changelog
>> v7 -> v8:
>> - Use a flag instead of a boolean for checking the coherency. It
>> improve the readability of the code. Suggested by Russell King.
>> - Consider that when coherency is set, it's for both L1 and L2 caches
>> - Use the arm_dma_alloc_args struct to pass the coherency status when
>> possible. Suggested by Rabin Vincent
>> - Remove the Tested-by flag from Marcin because of the modifications
>> around the L1 cache management in this series.
>>
>> v6 -> v7:
>> - Renamed is coherent by l2_coherent as suggested by Russell
>>
>> v5 -> v6:
>> - Rebased on v4.6-rc1
>>
>> v4 -> v5
>> - Keep the dmac_* function outside the !is_coherent case.
>>
>> v3 -> v4:
>> - Rebased on v4.3-rc1
>> - Fix conflict with commit "21caf3a765b0 ARM: 8398/1: arm DMA: Fix
>> allocation from CMA for coherent DMA"
>>
>> v2 -> v3:
>>
>> - Fix comments in patch 1 as suggested by Catalin.
>> - Fix build issues in patch 2 (by using the multi_v7_defconfig +
>> CONFIG_ROCKCHIP_IOMMU).
>> - Add the arm_coherent_iommu_mmap_attrs function.
>>
>>
>> Gregory CLEMENT (2):
>> ARM: dma-mapping: Don't use outer_flush_range when the L2C is coherent
>> ARM: dma-mapping: Fix the coherent case when iommu is used
>>
>> arch/arm/mm/dma-mapping.c | 144 +++++++++++++++++++++++++++++++++-------------
>> 1 file changed, 105 insertions(+), 39 deletions(-)
>>
>> --
>> 2.5.0
>>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2016-04-20 23:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 15:31 [PATCH v8 0/2] Fix dma mapping when the cache is coherent Gregory CLEMENT
2016-04-12 15:31 ` [PATCH v8 1/2] ARM: dma-mapping: Don't use outer_flush_range when the L2C " Gregory CLEMENT
2016-04-12 15:31 ` Gregory CLEMENT
2016-04-12 15:31 ` [PATCH v8 2/2] ARM: dma-mapping: Fix the coherent case when iommu is used Gregory CLEMENT
2016-04-16 15:27 ` [PATCH v8 0/2] Fix dma mapping when the cache is coherent Marcin Wojtas
2016-04-20 23:02 ` Gregory CLEMENT [this message]
2016-06-16 14:14 ` Gregory CLEMENT
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=877ffrx4sa.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.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 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.