mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vladimir Murzin <vladimir.murzin@arm.com>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Russell King - ARM Linux" <linux@armlinux.org.uk>,
	"Szemző András" <sza@esh.hu>, "Arnd Bergmann" <arnd@arndb.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Alexandre Torgue" <alexandre.torgue@st.com>,
	robin.murphy@arm.com, kbuild-all@01.org,
	"Christoph Hellwig" <hch@lst.de>,
	"Marek Szyprowski" <m.szyprowski@samsung.com>,
	"Steven Miao" <realmz6@gmail.com>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Michal Simek" <monstr@monstr.eu>,
	"Yoshinori Sato" <ysato@users.sourceforge.jp>,
	"Rich Felker" <dalias@libc.org>,
	"Chris Zankel" <chris@zankel.net>,
	"Max Filippov" <jcmvbkbc@gmail.com>
Subject: Re: [PATCH 0/2] Follow-up on "ARM: Fix dma_alloc_coherent() and friends for NOMMU"
Date: Fri, 30 Jun 2017 12:59:06 +0100	[thread overview]
Message-ID: <ad020e7b-9f4b-3f34-f8b6-cfcde158915c@arm.com> (raw)
In-Reply-To: <CA+M3ks5OqDwdmz6dTR87zX+OH_F+dJgXwfo96EWBg8XbvhmY4g@mail.gmail.com>

On 30/06/17 12:36, Benjamin Gaignard wrote:
> 2017-06-28 11:16 GMT+02:00 Vladimir Murzin <vladimir.murzin@arm.com>:
>> These two patches are folloups on "[PATCH v6 0/7] ARM: Fix
>> dma_alloc_coherent() and friends for NOMMU" which has been partly
>> merged in [1]. PATCH 1/2 is done per Christoph's suggestion [2] to
>> eliminate duplication in dma-noop.c.  PATCH 2/2 is fixup for ARM's dma
>> operations for NOMMU due to aforementioned change.
>>
>> @Benjamin, your Tested-by for ARM bits would be very appretiated!
> 
> I have been able to test on stm32f4 with drm/kms drivers which is
> calling dma_alloc_coherent
> and modetest doing mmap and it is working fine.
> 
> tested-by: Benjamin Gaignard <benjamin.gaignard@linaro.org>
> 

Great thanks!

Vladimir

>>
>> @Christoph, in case you decide to queue PATCH 1/2, can you put it
>> before "ARM: NOMMU: Introduce dma operations for noMMU", so transition
>> to the new dma operations won't break bisectability.
>>
>> [1] git://git.infradead.org/users/hch/dma-mapping.git for-next
>> [2] https://www.spinics.net/lists/arm-kernel/msg590587.html
>>
>> Cc: Steven Miao <realmz6@gmail.com>
>> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
>> Cc: Michal Simek <monstr@monstr.eu>
>> Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
>> Cc: Rich Felker <dalias@libc.org>
>> Cc: Chris Zankel <chris@zankel.net>
>> Cc: Max Filippov <jcmvbkbc@gmail.com>
>>
>> Thanks!
>>
>> Vladimir Murzin (2):
>>   drivers: dma-mapping: allow dma_common_mmap() for NOMMU
>>   fixup: ARM: NOMMU: Introduce dma operations for noMMU
>>
>>  arch/arm/mm/dma-mapping-nommu.c | 18 ------------------
>>  arch/blackfin/Kconfig           |  1 +
>>  arch/m32r/Kconfig               |  1 +
>>  arch/m68k/Kconfig               |  1 +
>>  arch/microblaze/Kconfig         |  1 +
>>  arch/sh/Kconfig                 |  1 +
>>  arch/xtensa/Kconfig             |  1 +
>>  drivers/base/dma-mapping.c      |  4 ++--
>>  8 files changed, 8 insertions(+), 20 deletions(-)
>>
>> --
>> 2.0.0
>>
> 
> 
> 

      reply	other threads:[~2017-06-30 11:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28  9:16 Vladimir Murzin
2017-06-28  9:16 ` [PATCH 1/2] drivers: dma-mapping: allow dma_common_mmap() for NOMMU Vladimir Murzin
2017-06-28  9:16 ` [PATCH 2/2] fixup: ARM: NOMMU: Introduce dma operations for noMMU Vladimir Murzin
2017-06-28 13:52 ` [PATCH 0/2] Follow-up on "ARM: Fix dma_alloc_coherent() and friends for NOMMU" Christoph Hellwig
2017-07-03  8:49   ` Vladimir Murzin
2017-07-03  8:54     ` Vladimir Murzin
2017-06-30 11:36 ` Benjamin Gaignard
2017-06-30 11:59   ` Vladimir Murzin [this message]

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=ad020e7b-9f4b-3f34-f8b6-cfcde158915c@arm.com \
    --to=vladimir.murzin@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexandre.torgue@st.com \
    --cc=arnd@arndb.de \
    --cc=benjamin.gaignard@linaro.org \
    --cc=chris@zankel.net \
    --cc=dalias@libc.org \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=jcmvbkbc@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=monstr@monstr.eu \
    --cc=realmz6@gmail.com \
    --cc=robin.murphy@arm.com \
    --cc=sza@esh.hu \
    --cc=ysato@users.sourceforge.jp \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®