From: Sumit Semwal <sumit.semwal@linaro.org>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org
Cc: linaro-kernel@lists.linaro.org, robdclark@gmail.com,
daniel@ffwll.ch, m.szyprowski@samsung.com,
t.stanislaws@samsung.com, Sumit Semwal <sumit.semwal@linaro.org>
Subject: [RFCv2 0/2] dma-parms, constraints and helpers for dma-buf
Date: Wed, 21 Jan 2015 09:46:45 +0530 [thread overview]
Message-ID: <1421813807-9178-1-git-send-email-sumit.semwal@linaro.org> (raw)
Hello Everyone,
Based on review comments received, I've split my earlier patchset on
'dma-buf constraints-enabled allocation' [1] into 2 sets:
- first one is this one, to use dma_parms and related parameters from
struct device to share constraints, and then to use these constraints in
dma-buf to help find the least common constraint set that could then be
used by exporters to decide on allocation.
This is a partial re-write of what Rob Clark proposed some while ago [2];
I've tried to take care of review comments on his patchset, but any errors
and omissions are, ofcourse, mine.
- Second part, one which I'm working on, and will post soon, aims at adding
allocator-helpers in dma-buf framework which could use this constraint
information to help choose the right allocator from a list.
While I work on the second part, I thought of sending the RFC for this one,
to get feedback on whether this mechanism seems ok to everyone.
[1] https://lkml.org/lkml/2014/10/10/340
[2] https://lkml.org/lkml/2012/7/19/285
Rob Clark (1):
device: add dma_params->max_segment_count
Sumit Semwal (1):
dma-buf: add helpers for sharing attacher constraints with dma-parms
drivers/dma-buf/dma-buf.c | 134 +++++++++++++++++++++++++++++++++++++++++++-
include/linux/device.h | 1 +
include/linux/dma-buf.h | 22 ++++++++
include/linux/dma-mapping.h | 19 +++++++
4 files changed, 175 insertions(+), 1 deletion(-)
--
1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: Sumit Semwal <sumit.semwal@linaro.org>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org
Cc: linaro-kernel@lists.linaro.org, robdclark@gmail.com,
daniel@ffwll.ch, m.szyprowski@samsung.com,
t.stanislaws@samsung.com, Sumit Semwal <sumit.semwal@linaro.org>
Subject: [RFCv2 0/2] dma-parms, constraints and helpers for dma-buf
Date: Wed, 21 Jan 2015 09:46:45 +0530 [thread overview]
Message-ID: <1421813807-9178-1-git-send-email-sumit.semwal@linaro.org> (raw)
Hello Everyone,
Based on review comments received, I've split my earlier patchset on
'dma-buf constraints-enabled allocation' [1] into 2 sets:
- first one is this one, to use dma_parms and related parameters from
struct device to share constraints, and then to use these constraints in
dma-buf to help find the least common constraint set that could then be
used by exporters to decide on allocation.
This is a partial re-write of what Rob Clark proposed some while ago [2];
I've tried to take care of review comments on his patchset, but any errors
and omissions are, ofcourse, mine.
- Second part, one which I'm working on, and will post soon, aims at adding
allocator-helpers in dma-buf framework which could use this constraint
information to help choose the right allocator from a list.
While I work on the second part, I thought of sending the RFC for this one,
to get feedback on whether this mechanism seems ok to everyone.
[1] https://lkml.org/lkml/2014/10/10/340
[2] https://lkml.org/lkml/2012/7/19/285
Rob Clark (1):
device: add dma_params->max_segment_count
Sumit Semwal (1):
dma-buf: add helpers for sharing attacher constraints with dma-parms
drivers/dma-buf/dma-buf.c | 134 +++++++++++++++++++++++++++++++++++++++++++-
include/linux/device.h | 1 +
include/linux/dma-buf.h | 22 ++++++++
include/linux/dma-mapping.h | 19 +++++++
4 files changed, 175 insertions(+), 1 deletion(-)
--
1.9.1
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: sumit.semwal@linaro.org (Sumit Semwal)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFCv2 0/2] dma-parms, constraints and helpers for dma-buf
Date: Wed, 21 Jan 2015 09:46:45 +0530 [thread overview]
Message-ID: <1421813807-9178-1-git-send-email-sumit.semwal@linaro.org> (raw)
Hello Everyone,
Based on review comments received, I've split my earlier patchset on
'dma-buf constraints-enabled allocation' [1] into 2 sets:
- first one is this one, to use dma_parms and related parameters from
struct device to share constraints, and then to use these constraints in
dma-buf to help find the least common constraint set that could then be
used by exporters to decide on allocation.
This is a partial re-write of what Rob Clark proposed some while ago [2];
I've tried to take care of review comments on his patchset, but any errors
and omissions are, ofcourse, mine.
- Second part, one which I'm working on, and will post soon, aims at adding
allocator-helpers in dma-buf framework which could use this constraint
information to help choose the right allocator from a list.
While I work on the second part, I thought of sending the RFC for this one,
to get feedback on whether this mechanism seems ok to everyone.
[1] https://lkml.org/lkml/2014/10/10/340
[2] https://lkml.org/lkml/2012/7/19/285
Rob Clark (1):
device: add dma_params->max_segment_count
Sumit Semwal (1):
dma-buf: add helpers for sharing attacher constraints with dma-parms
drivers/dma-buf/dma-buf.c | 134 +++++++++++++++++++++++++++++++++++++++++++-
include/linux/device.h | 1 +
include/linux/dma-buf.h | 22 ++++++++
include/linux/dma-mapping.h | 19 +++++++
4 files changed, 175 insertions(+), 1 deletion(-)
--
1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: Sumit Semwal <sumit.semwal@linaro.org>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org
Cc: t.stanislaws@samsung.com, linaro-kernel@lists.linaro.org,
m.szyprowski@samsung.com
Subject: [RFCv2 0/2] dma-parms, constraints and helpers for dma-buf
Date: Wed, 21 Jan 2015 09:46:45 +0530 [thread overview]
Message-ID: <1421813807-9178-1-git-send-email-sumit.semwal@linaro.org> (raw)
Hello Everyone,
Based on review comments received, I've split my earlier patchset on
'dma-buf constraints-enabled allocation' [1] into 2 sets:
- first one is this one, to use dma_parms and related parameters from
struct device to share constraints, and then to use these constraints in
dma-buf to help find the least common constraint set that could then be
used by exporters to decide on allocation.
This is a partial re-write of what Rob Clark proposed some while ago [2];
I've tried to take care of review comments on his patchset, but any errors
and omissions are, ofcourse, mine.
- Second part, one which I'm working on, and will post soon, aims at adding
allocator-helpers in dma-buf framework which could use this constraint
information to help choose the right allocator from a list.
While I work on the second part, I thought of sending the RFC for this one,
to get feedback on whether this mechanism seems ok to everyone.
[1] https://lkml.org/lkml/2014/10/10/340
[2] https://lkml.org/lkml/2012/7/19/285
Rob Clark (1):
device: add dma_params->max_segment_count
Sumit Semwal (1):
dma-buf: add helpers for sharing attacher constraints with dma-parms
drivers/dma-buf/dma-buf.c | 134 +++++++++++++++++++++++++++++++++++++++++++-
include/linux/device.h | 1 +
include/linux/dma-buf.h | 22 ++++++++
include/linux/dma-mapping.h | 19 +++++++
4 files changed, 175 insertions(+), 1 deletion(-)
--
1.9.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-01-21 4:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 4:16 Sumit Semwal [this message]
2015-01-21 4:16 ` [RFCv2 0/2] dma-parms, constraints and helpers for dma-buf Sumit Semwal
2015-01-21 4:16 ` Sumit Semwal
2015-01-21 4:16 ` Sumit Semwal
2015-01-21 4:16 ` [RFCv2 1/2] device: add dma_params->max_segment_count Sumit Semwal
2015-01-21 4:16 ` Sumit Semwal
2015-01-21 4:16 ` Sumit Semwal
2015-01-21 18:56 ` Robin Murphy
2015-01-21 18:56 ` Robin Murphy
2015-01-21 18:56 ` Robin Murphy
2015-01-21 18:56 ` Robin Murphy
2015-01-22 3:46 ` Sumit Semwal
2015-01-22 3:46 ` Sumit Semwal
2015-01-22 3:46 ` Sumit Semwal
2015-01-22 3:46 ` Sumit Semwal
2015-01-21 4:16 ` [RFCv2 2/2] dma-buf: add helpers for sharing attacher constraints with dma-parms Sumit Semwal
2015-01-21 4:16 ` Sumit Semwal
2015-01-21 4:16 ` Sumit Semwal
2015-01-21 4:16 ` Sumit Semwal
2015-01-21 17:31 ` Russell King - ARM Linux
2015-01-21 17:31 ` Russell King - ARM Linux
2015-01-21 17:31 ` Russell King - ARM Linux
2015-01-21 17:31 ` Russell King - ARM Linux
2015-01-27 7:04 ` Sumit Semwal
2015-01-27 7:04 ` Sumit Semwal
2015-01-27 7:04 ` Sumit Semwal
2015-01-27 7:04 ` Sumit Semwal
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=1421813807-9178-1-git-send-email-sumit.semwal@linaro.org \
--to=sumit.semwal@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=robdclark@gmail.com \
--cc=t.stanislaws@samsung.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.