From: Damian Hobson-Garcia <dhobsong@igel.co.jp>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
Will Deacon <Will.Deacon@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"msalter@redhat.com" <msalter@redhat.com>,
"linux-c6x-dev@linux-c6x.org" <linux-c6x-dev@linux-c6x.org>,
"deller@gmx.de" <deller@gmx.de>,
"linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] dma-mapping: Define dma_{alloc,free}_attrs() for all archs
Date: Thu, 23 May 2013 11:47:13 +0900 [thread overview]
Message-ID: <519D8331.3060203@igel.co.jp> (raw)
In-Reply-To: <20130522094741.GE14322@arm.com>
Hi Catalin,
On 2013/05/22 18:47, Catalin Marinas wrote:
> On Wed, May 22, 2013 at 03:37:17AM +0100, Damian Hobson-Garcia wrote:
>> Hello,
>> On 2013/04/30 12:01, Damian Hobson-Garcia wrote:
>>> Most architectures that define CONFIG_HAVE_DMA=y, have implementations for
>>> both dma_alloc_attrs() and dma_free_attrs(). All achitectures that do
>>> not define CONFIG_HAVE_DMA also have both of these definitions provided by
>>> dma-mapping-broken.h.
>
> BTW, shouldn't this be called CONFIG_HAVE_DMA_ATTRS?
CONFIG_HAVE_DMA_ATTRS is currently used to enable the functions to
set/get the DMA attribute values. Poking through the headers, it looks
like the struct dma_attrs is defined regardless of the
CONFIG_HAVE_DMA_ATTRS setting, so in that respect
we always seem to "have" DMA attributes (if we have DMA), but they may
not always be meaningful (ie. set to some value).
>
>>> Provide a default definition for the archs that define CONFIG_HAVE_DMA=y,
>>> but have no implementation for dma_{alloc,free}_attrs().
>>>
>>> As I don't have hardware for any of these systems, the patches are only
>>> compile-tested where I could (arm64, s390) and untested for the archs
>>> where I couldn't find a readily available prebuilt cross-compiler (c6x, parisc).
>>
>>> arch/arm64/include/asm/dma-mapping.h | 17 +++++++++++------
>>> arch/c6x/include/asm/dma-mapping.h | 3 +++
>>> arch/parisc/include/asm/dma-mapping.h | 3 +++
>>> arch/s390/include/asm/dma-mapping.h | 17 +++++++++++------
>>> 4 files changed, 28 insertions(+), 12 deletions(-)
>>>
>>
>> Since this series spans several architectures, what would be the best
>> way to have this patch series merged?
>> Should I resubmit each patch to the mailing list for each architecture
>> separately?
>
> I'm happy to take the arm64 patch.
Very much appreciated.
>
> Thanks.
>
Damian
--
Damian Hobson-Garcia
IGEL Co.,Ltd
http://www.igel.co.jp
WARNING: multiple messages have this Message-ID (diff)
From: dhobsong@igel.co.jp (Damian Hobson-Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] dma-mapping: Define dma_{alloc,free}_attrs() for all archs
Date: Thu, 23 May 2013 11:47:13 +0900 [thread overview]
Message-ID: <519D8331.3060203@igel.co.jp> (raw)
In-Reply-To: <20130522094741.GE14322@arm.com>
Hi Catalin,
On 2013/05/22 18:47, Catalin Marinas wrote:
> On Wed, May 22, 2013 at 03:37:17AM +0100, Damian Hobson-Garcia wrote:
>> Hello,
>> On 2013/04/30 12:01, Damian Hobson-Garcia wrote:
>>> Most architectures that define CONFIG_HAVE_DMA=y, have implementations for
>>> both dma_alloc_attrs() and dma_free_attrs(). All achitectures that do
>>> not define CONFIG_HAVE_DMA also have both of these definitions provided by
>>> dma-mapping-broken.h.
>
> BTW, shouldn't this be called CONFIG_HAVE_DMA_ATTRS?
CONFIG_HAVE_DMA_ATTRS is currently used to enable the functions to
set/get the DMA attribute values. Poking through the headers, it looks
like the struct dma_attrs is defined regardless of the
CONFIG_HAVE_DMA_ATTRS setting, so in that respect
we always seem to "have" DMA attributes (if we have DMA), but they may
not always be meaningful (ie. set to some value).
>
>>> Provide a default definition for the archs that define CONFIG_HAVE_DMA=y,
>>> but have no implementation for dma_{alloc,free}_attrs().
>>>
>>> As I don't have hardware for any of these systems, the patches are only
>>> compile-tested where I could (arm64, s390) and untested for the archs
>>> where I couldn't find a readily available prebuilt cross-compiler (c6x, parisc).
>>
>>> arch/arm64/include/asm/dma-mapping.h | 17 +++++++++++------
>>> arch/c6x/include/asm/dma-mapping.h | 3 +++
>>> arch/parisc/include/asm/dma-mapping.h | 3 +++
>>> arch/s390/include/asm/dma-mapping.h | 17 +++++++++++------
>>> 4 files changed, 28 insertions(+), 12 deletions(-)
>>>
>>
>> Since this series spans several architectures, what would be the best
>> way to have this patch series merged?
>> Should I resubmit each patch to the mailing list for each architecture
>> separately?
>
> I'm happy to take the arm64 patch.
Very much appreciated.
>
> Thanks.
>
Damian
--
Damian Hobson-Garcia
IGEL Co.,Ltd
http://www.igel.co.jp
next prev parent reply other threads:[~2013-05-23 2:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 3:01 [PATCH v2 0/4] dma-mapping: Define dma_{alloc,free}_attrs() for all archs Damian Hobson-Garcia
2013-04-30 3:01 ` [PATCH v2 0/4] dma-mapping: Define dma_{alloc, free}_attrs() " Damian Hobson-Garcia
2013-05-22 2:37 ` [PATCH v2 0/4] dma-mapping: Define dma_{alloc,free}_attrs() " Damian Hobson-Garcia
2013-05-22 2:37 ` Damian Hobson-Garcia
2013-05-22 9:47 ` Catalin Marinas
2013-05-22 9:47 ` Catalin Marinas
2013-05-22 9:47 ` Catalin Marinas
2013-05-23 2:47 ` Damian Hobson-Garcia [this message]
2013-05-23 2:47 ` Damian Hobson-Garcia
2013-05-23 9:47 ` Catalin Marinas
2013-05-23 9:47 ` Catalin Marinas
2013-05-24 2:52 ` Damian Hobson-Garcia
2013-05-24 2:52 ` Damian Hobson-Garcia
2013-05-22 18:19 ` Helge Deller
2013-05-22 18:19 ` Helge Deller
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=519D8331.3060203@igel.co.jp \
--to=dhobsong@igel.co.jp \
--cc=Will.Deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=deller@gmx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=msalter@redhat.com \
/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.