From: Ricardo Ribalda <ribalda@chromium.org>
To: ". Christoph Hellwig" <hch@lst.de>
Cc: Sergey Senozhatsky <senozhatsky@google.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
IOMMU DRIVERS <iommu@lists.linux-foundation.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH v3 5/6] media: uvcvideo: Use dma_alloc_noncontiguos API
Date: Fri, 15 Jan 2021 14:08:14 +0100 [thread overview]
Message-ID: <CANiDSCvuvj47=nhoWhvzc5raMxM60w+JYRWjd0YepcbcbkrUjA@mail.gmail.com> (raw)
In-Reply-To: <20210111083614.GA27589@lst.de>
On Mon, Jan 11, 2021 at 9:36 AM . Christoph Hellwig <hch@lst.de> wrote:
>
> On Thu, Jan 07, 2021 at 03:14:08PM +0100, Ricardo Ribalda wrote:
> > > So I think we do want these branches for coherent vs non-coherent as they
> > > have very different semantics and I do not think that hiding them under
> > > the same API helps people to understand those vastly different semantics.
> > >
> > > OTOH we should look into a fallback for DMA API instances that do not
> > > support the discontigous allocations.
> > >
> > > I think between your comments and those from Ricardo I have a good idea
> > > for a somewhat updated API. I'll try to post something in the next days.
> >
> > Did you have time to look into this?
> >
> > No hurry, I just want to make sure that I didn't miss anything ;)
>
> Haven't managed to get to it, sorry.
No worries!, is there something we can do to help you with this?
>
> >
> > Best regards!
> >
> >
> >
> > --
> > Ricardo Ribalda
> ---end quoted text---
--
Ricardo Ribalda
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-01-15 13:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 22:19 [PATCH v3 5/6] media: uvcvideo: Use dma_alloc_noncontiguos API Ricardo Ribalda
2020-11-26 11:44 ` Sergey Senozhatsky
2020-11-30 8:31 ` Christoph Hellwig
2020-11-30 8:34 ` Christoph Hellwig
2020-11-30 10:49 ` Ricardo Ribalda
2020-12-01 3:36 ` Sergey Senozhatsky
2020-12-01 14:49 ` Christoph Hellwig
2020-12-08 4:54 ` Tomasz Figa
2020-12-08 6:45 ` Sergey Senozhatsky via iommu
2020-12-08 7:13 ` Sergey Senozhatsky
2020-12-09 11:16 ` . Christoph Hellwig
2021-01-07 14:14 ` Ricardo Ribalda
2021-01-11 8:36 ` . Christoph Hellwig
2021-01-15 13:08 ` Ricardo Ribalda [this message]
2021-01-20 17:17 ` . Christoph Hellwig
2021-01-26 17:06 ` . Christoph Hellwig
2021-01-26 23:29 ` Ricardo Ribalda
2021-01-27 15:56 ` . Christoph Hellwig
2021-01-27 21:35 ` Ricardo Ribalda
2021-01-28 7:57 ` . Christoph Hellwig
2020-12-09 11:12 ` Christoph Hellwig
2020-12-09 13:05 ` Robin Murphy
2020-12-10 5:08 ` Tomasz Figa
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='CANiDSCvuvj47=nhoWhvzc5raMxM60w+JYRWjd0YepcbcbkrUjA@mail.gmail.com' \
--to=ribalda@chromium.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robin.murphy@arm.com \
--cc=senozhatsky@google.com \
--cc=sergey.senozhatsky.work@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).