From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
Cc: linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
hverkuil@xs4all.nl, ribalda@chromium.org, tfiga@chromium.org,
senozhatsky@google.com, hch@lst.de, kernel@collabora.com
Subject: Re: [PATCH 3/3] media: stk1160: use dma_alloc_noncontiguous API
Date: Tue, 11 Jan 2022 09:38:21 -0300 [thread overview]
Message-ID: <Yd16PXCDGwF5V7aK@eze-laptop> (raw)
In-Reply-To: <20220111065505.6323-4-dafna.hirschfeld@collabora.com>
Hi Dafna,
Very nice work.
I specially like all the testing that you mentioned in the cover-letter.
Back in the day, there were a few users trying to use STK1160 (Easycap)
with Beaglebone boards, without success due to lack of USB throughput.
If anything else, I think it's good to see additional noncontiguous API users.
On Tue, Jan 11, 2022 at 08:55:05AM +0200, Dafna Hirschfeld wrote:
> Replace the urb buffers allocation to
> use the noncontiguous API. This improve performance
> on Arm.
> The noncontiguous API require handling
> synchronization.
> This commit is similar to the one sent to
> uvc: [1]
>
> [1] https://lkml.org/lkml/2021/3/12/1506
>
This commit description needs lots of attention. In particular,
please add the test results here.
> Signed-off-by: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
> ---
> drivers/media/usb/stk1160/stk1160-v4l.c | 3 +
> drivers/media/usb/stk1160/stk1160-video.c | 109 +++++++++++++---------
> drivers/media/usb/stk1160/stk1160.h | 10 ++
> 3 files changed, 79 insertions(+), 43 deletions(-)
>
[..]
> @@ -501,7 +524,7 @@ int stk1160_alloc_isoc(struct stk1160 *dev)
>
> free_i_bufs:
> /* Save the allocated buffers so far, so we can properly free them */
> - dev->isoc_ctl.num_bufs = i+1;
> + dev->isoc_ctl.num_bufs = i;
This looks like a separate fix, similar to 1/3 ?
> stk1160_free_isoc(dev);
> return -ENOMEM;
> }
> diff --git a/drivers/media/usb/stk1160/stk1160.h b/drivers/media/usb/stk1160/stk1160.h
> index 1ffca1343d88..52bea7815ae5 100644
> --- a/drivers/media/usb/stk1160/stk1160.h
> +++ b/drivers/media/usb/stk1160/stk1160.h
> @@ -16,6 +16,8 @@
> #include <media/videobuf2-v4l2.h>
> #include <media/v4l2-device.h>
> #include <media/v4l2-ctrls.h>
> +#include <linux/usb.h>
> +#include <linux/usb/hcd.h>
>
> #define STK1160_VERSION "0.9.5"
> #define STK1160_VERSION_NUM 0x000905
> @@ -87,6 +89,9 @@ struct stk1160_buffer {
> struct stk1160_urb {
> struct urb *urb;
> char *transfer_buffer;
> + struct sg_table *sgt;
> + struct stk1160 *dev;
> + dma_addr_t dma;
> };
>
> struct stk1160_isoc_ctl {
> @@ -190,3 +195,8 @@ void stk1160_select_input(struct stk1160 *dev);
>
> /* Provided by stk1160-ac97.c */
> void stk1160_ac97_setup(struct stk1160 *dev);
> +
> +static inline struct device *stk1160_get_dmadev(struct stk1160 *dev)
> +{
> + return bus_to_hcd(dev->udev->bus)->self.sysdev;
This function looks truly horrible, is there no other way to get the device ?
I suppose this function return something different than (struct stk1160*)dev->dev ?
Thanks,
Ezequiel
next prev parent reply other threads:[~2022-01-11 12:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 6:55 [PATCH 0/3] media: stk1160: allocate urb buffs with the DMA noncontiguous API Dafna Hirschfeld
2022-01-11 6:55 ` [PATCH 1/3] media: stk1160: fix number of buffers in case not all buffers are created Dafna Hirschfeld
2022-01-11 12:21 ` Ezequiel Garcia
2022-01-11 6:55 ` [PATCH 2/3] media: stk1160: move transfer_buffer and urb to same struct 'stk1160_urb' Dafna Hirschfeld
2022-01-11 8:10 ` Christoph Hellwig
2022-01-11 12:29 ` Ezequiel Garcia
2022-01-11 6:55 ` [PATCH 3/3] media: stk1160: use dma_alloc_noncontiguous API Dafna Hirschfeld
2022-01-11 8:13 ` Christoph Hellwig
2022-01-11 8:50 ` Dafna Hirschfeld
2022-01-11 8:52 ` Christoph Hellwig
2022-01-11 8:55 ` Dafna Hirschfeld
2022-01-11 8:59 ` Christoph Hellwig
2022-01-12 9:25 ` Sergey Senozhatsky
2022-01-11 12:38 ` Ezequiel Garcia [this message]
2022-01-24 14:43 ` Dafna Hirschfeld
2022-01-24 16:02 ` Dafna Hirschfeld
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=Yd16PXCDGwF5V7aK@eze-laptop \
--to=ezequiel@vanguardiasur.com.ar \
--cc=dafna.hirschfeld@collabora.com \
--cc=hch@lst.de \
--cc=hverkuil@xs4all.nl \
--cc=kernel@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=ribalda@chromium.org \
--cc=senozhatsky@google.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