All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Randy Li <ayaka@soulik.info>
Cc: linux-usb@vger.kernel.org,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	linux-kernel@vger.kernel.org, corbet@lwn.net,
	linux-doc@vger.kernel.org
Subject: Re: USB: DMA: mapping existing buffer is not supported?
Date: Wed, 13 Sep 2023 21:19:01 +0200	[thread overview]
Message-ID: <2023091323-trombone-storeroom-cbd3@gregkh> (raw)
In-Reply-To: <1e783efe-8659-8be1-82b7-15186302e88c@soulik.info>

On Thu, Sep 14, 2023 at 03:06:58AM +0800, Randy Li wrote:
> Hello
> 
> I was trying to understand why USB webcams (UVC) have to copy video data
> through the CPU (uvc_video_complete() schedules uvc_video_copy_data_work()
> for this purpose). During my investigation, I noticed that functions
> like|usb_sg_*() and |usb_buffer_*() are not available since kernel version
> 2.6.12.

What do you mean by "not available"?  I see them in the tree today, why
do you think they are not present?

> I can comprehend that USB host controllers such as xHCI, commonly found in
> embedded implementations like dwc3, do not support IOMMU. However, this
> should not prevent them from operating on a contiguous buffer.

Are you sure that the protocol for these devices allow this?

> If the USB subsystem can no longer work with existing buffers, I propose
> that we consider removing the remaining documentation in the "Working with
> existing buffers" section of Documentation/driver-api/usb/dma.rst.

I don't understand, what is wrong with the information there exactly?
Have you tried following the suggestions there?

thanks,

greg k-h

  reply	other threads:[~2023-09-13 19:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 19:06 USB: DMA: mapping existing buffer is not supported? Randy Li
2023-09-13 19:19 ` Greg KH [this message]
2023-09-13 20:09   ` Randy Li
2023-09-13 20:32     ` Greg KH
2023-09-13 21:11       ` Alan Stern

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=2023091323-trombone-storeroom-cbd3@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=ayaka@soulik.info \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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 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.