From: Hans Verkuil <hansverk@cisco.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-media@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH v2] media: vb2-dma-contig: configure DMA max segment size properly
Date: Thu, 28 Apr 2016 15:42:32 +0200 [thread overview]
Message-ID: <57221348.9020306@cisco.com> (raw)
In-Reply-To: <cc31e0a1-f655-2107-a024-58fdf5ba45e4@samsung.com>
On 04/28/2016 03:39 PM, Marek Szyprowski wrote:
> Hello,
>
>
> On 2016-04-28 15:29, Hans Verkuil wrote:
>> On 04/28/2016 03:20 PM, Marek Szyprowski wrote:
>>> This patch lets vb2-dma-contig memory allocator to configure DMA max
>>> segment size properly for the client device. Setting it is needed to let
>>> DMA-mapping subsystem to create a single, contiguous mapping in DMA
>>> address space. This is essential for all devices, which use dma-contig
>>> videobuf2 memory allocator and shared buffers (in USERPTR or DMAbuf modes
>>> of operations).
>>>
>>> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
>> Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
>>
>> Should this go in for 4.7? (might be too late) Should this go into older
>> kernels as well?
Oops, typo. I meant 4.6, not 4.7. I gather that committing this for 4.6 is not
necessary, so I just queue it up for 4.7.
Regards,
Hans
next prev parent reply other threads:[~2016-04-28 13:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 12:12 [PATCH] media: vb2-dma-contig: configure DMA max segment size properly Marek Szyprowski
2016-04-28 12:31 ` Hans Verkuil
2016-04-28 13:20 ` [PATCH v2] " Marek Szyprowski
2016-04-28 13:29 ` Hans Verkuil
2016-04-28 13:39 ` Marek Szyprowski
2016-04-28 13:42 ` Hans Verkuil [this message]
2016-04-29 11:21 ` Sakari Ailus
2016-04-29 11:39 ` Marek Szyprowski
2016-04-29 13:56 ` Sakari Ailus
2016-05-02 8:39 ` Hans Verkuil
2016-05-02 10:59 ` [PATCH v3] " Marek Szyprowski
2016-05-02 13:14 ` Sakari Ailus
2016-05-02 13:16 ` Hans Verkuil
2016-05-04 8:22 ` Hans Verkuil
2016-05-04 8:28 ` Marek Szyprowski
2016-05-04 8:32 ` Hans Verkuil
2016-05-04 8:38 ` Marek Szyprowski
2016-05-04 9:00 ` [PATCH v4] " Marek Szyprowski
2016-05-06 18:52 ` Mauro Carvalho Chehab
2016-05-09 6:13 ` Marek Szyprowski
2016-05-09 10:09 ` Mauro Carvalho Chehab
2016-05-17 7:29 ` Marek Szyprowski
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=57221348.9020306@cisco.com \
--to=hansverk@cisco.com \
--cc=b.zolnierkie@samsung.com \
--cc=hans.verkuil@cisco.com \
--cc=k.kozlowski@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=s.nawrocki@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.