From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
linux-media@vger.kernel.org
Subject: Re: [RFC PATCH 9/9] omap3isp/rcar_fdp1/vsp1/xilinx: drop VB2_USERPTR
Date: Sat, 22 Feb 2020 12:43:48 +0200 [thread overview]
Message-ID: <20200222104348.GE4846@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20200221194640.GI5023@valkosipuli.retiisi.org.uk>
Hi Sakari,
On Fri, Feb 21, 2020 at 09:46:41PM +0200, Sakari Ailus wrote:
> Hi Hans, Laurent,
>
> On Fri, Feb 21, 2020 at 04:31:01PM +0200, Laurent Pinchart wrote:
> > Hi Hans,
> >
> > CC'ing Sakari for the omap3isp part.
>
> Thanks.
>
> The omap3isp is behind an IOMMU, so the USERPTR memory does not need to be
> physically contiguous. I don't see a reason to drop userptr support from
> the driver.
Apart from the fact that this API should be discouraged :-) I wonder if
it's used, that's my real question. As we can't rule it out, I'd be
cautious about dropping it.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2020-02-22 10:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 8:45 [RFC PATCH 0/9] Drop VB2_USERPTR + dma-contig combo Hans Verkuil
2020-02-21 8:45 ` [RFC PATCH 1/9] mtk-vcodec: drop VB2_USERPTR Hans Verkuil
2020-02-21 8:45 ` [RFC PATCH 2/9] solo6x10: " Hans Verkuil
2020-02-21 8:45 ` [RFC PATCH 3/9] m2m-deinterlace: " Hans Verkuil
2020-02-21 8:45 ` [RFC PATCH 4/9] mcam-core: " Hans Verkuil
2020-02-21 8:45 ` [RFC PATCH 5/9] sh_veu: " Hans Verkuil
2020-02-21 8:45 ` [RFC PATCH 6/9] mx2_emmaprp: " Hans Verkuil
2020-02-21 8:45 ` [RFC PATCH 7/9] davinci: " Hans Verkuil
2020-02-21 8:45 ` [RFC PATCH 8/9] exynos/s3c/s5p: " Hans Verkuil
2020-02-21 8:53 ` Tomasz Figa
2020-02-21 11:54 ` Hans Verkuil
2020-02-21 13:11 ` Marek Szyprowski
2020-02-21 13:34 ` Tomasz Figa
2020-02-21 8:45 ` [RFC PATCH 9/9] omap3isp/rcar_fdp1/vsp1/xilinx: " Hans Verkuil
2020-02-21 9:01 ` Kieran Bingham
2020-02-21 14:31 ` Laurent Pinchart
2020-02-21 19:46 ` Sakari Ailus
2020-02-22 10:43 ` Laurent Pinchart [this message]
2020-02-22 13:13 ` Sakari Ailus
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=20200222104348.GE4846@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
/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