From: Christoph Hellwig <hch@lst.de>
To: Tomasz Figa <tfiga@chromium.org>
Cc: Christoph Hellwig <hch@lst.de>,
Robin Murphy <robin.murphy@arm.com>, Anle Pan <anle.pan@nxp.com>,
m.szyprowski@samsung.com, mchehab@kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
hui.fang@nxp.com, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH] media: videobuf2-dma-sg: limit the sg segment size
Date: Wed, 30 Aug 2023 16:33:41 +0200 [thread overview]
Message-ID: <20230830143341.GA25574@lst.de> (raw)
In-Reply-To: <CAAFQd5CiHXvsJugSi+hXY9ESsmxUzBzmbhF6G48iVsOcL5eMtQ@mail.gmail.com>
On Wed, Aug 30, 2023 at 12:47:57PM +0900, Tomasz Figa wrote:
> Do we see anything replacing it widely anywhere on the short-middle
> term horizon? I think we could possibly migrate vb2 to use that new
> thing internally and just provide some compatibility X to scatterlist
> conversion function for the drivers.
Jason said at LSF/MM that he had a prototype for a mapping API that
takes a phys/len array as input and dma_addr/len a output, which really
is the right thing to do, especially for dmabuf.
Jason, what's the status of your work?
next prev parent reply other threads:[~2023-08-30 18:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 7:54 [PATCH] media: videobuf2-dma-sg: limit the sg segment size Anle Pan
2023-08-29 10:03 ` Tomasz Figa
2023-08-29 11:14 ` Robin Murphy
2023-08-29 15:04 ` Christoph Hellwig
2023-08-30 3:47 ` Tomasz Figa
2023-08-30 14:33 ` Christoph Hellwig [this message]
2023-08-30 16:43 ` Jason Gunthorpe
2023-08-31 12:35 ` Christoph Hellwig
2023-08-31 15:32 ` Jason Gunthorpe
2023-09-01 6:10 ` Christoph Hellwig
2023-09-01 14:26 ` Jason Gunthorpe
[not found] ` <DB9PR04MB92841D8BC1122D5A4210F78987E6A@DB9PR04MB9284.eurprd04.prod.outlook.com>
2023-08-30 13:41 ` [EXT] " Robin Murphy
2023-08-30 3:59 ` Tomasz Figa
2023-09-06 8:52 ` Hans Verkuil
2023-09-06 9:26 ` Tomasz Figa
2023-09-06 9:43 ` Hans Verkuil
2023-08-30 8:50 ` Hui Fang
2023-08-30 9:28 ` Tomasz Figa
2023-09-04 7:10 ` [EXT] " Hui Fang
2023-09-05 3:43 ` Tomasz Figa
2023-09-06 8:16 ` Hui Fang
2023-09-06 9:28 ` Tomasz Figa
2023-09-11 6:13 ` Hui Fang
2023-09-12 2:22 ` Tomasz Figa
2023-09-12 7:01 ` Hui Fang
2023-09-12 7:10 ` Tomasz Figa
2023-09-12 7:43 ` Hui Fang
2023-09-12 7:51 ` Tomasz Figa
2023-09-13 9:13 ` Hui Fang
2023-09-13 9:44 ` Tomasz Figa
2023-09-13 13:16 ` Hui Fang
2023-09-18 2:28 ` Hui Fang
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=20230830143341.GA25574@lst.de \
--to=hch@lst.de \
--cc=anle.pan@nxp.com \
--cc=hui.fang@nxp.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tfiga@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox