From: Hans Verkuil <hverkuil@xs4all.nl>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
linux-media@vger.kernel.org
Cc: "Krzysztof Hałasa" <khalasa@piap.pl>
Subject: Re: [PATCH v3] media: Support Intersil/Techwell TW686x-based video capture cards
Date: Mon, 21 Mar 2016 12:44:44 +0100 [thread overview]
Message-ID: <56EFDEAC.2040904@xs4all.nl> (raw)
In-Reply-To: <1456929016-4160-1-git-send-email-ezequiel@vanguardiasur.com.ar>
Hi Ezequiel,
On 03/02/2016 03:30 PM, Ezequiel Garcia wrote:
> This commit introduces the support for the Techwell TW686x video
> capture IC. This hardware supports a few DMA modes, including
> scatter-gather and frame (contiguous).
>
> This commit makes little use of the DMA engine and instead has
> a memcpy based implementation. DMA frame and scatter-gather modes
> support may be added in the future.
>
> Currently supported chips:
> - TW6864 (4 video channels),
> - TW6865 (4 video channels, not tested, second generation chip),
> - TW6868 (8 video channels but only 4 first channels using
> built-in video decoder are supported, not tested),
> - TW6869 (8 video channels, second generation chip).
>
> Cc: Krzysztof Hałasa <khalasa@piap.pl>
> Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
I've tested this with my PCIe tw6869 card (arrived this week).
Video is fine, but only the first audio input is available. I suspect you
have only one audio input?
Regarding the memcpy: if you have a patch for me that reverts back to a non-memcpy
situation, then I can do duration tests for you.
Unless you've ordered one of these PCIe cards yourself?
Regards,
Hans
next prev parent reply other threads:[~2016-03-21 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 5:23 [PATCH v2] media: Support Intersil/Techwell TW686x-based video capture cards Ezequiel Garcia
2016-02-29 21:40 ` Ezequiel Garcia
2016-03-02 8:22 ` Hans Verkuil
2016-03-02 14:30 ` [PATCH v3] " Ezequiel Garcia
2016-03-21 11:44 ` Hans Verkuil [this message]
2016-03-21 18:49 ` Ezequiel Garcia
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=56EFDEAC.2040904@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=khalasa@piap.pl \
--cc=linux-media@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox