From: Hans Verkuil <hverkuil@xs4all.nl>
To: Archit Taneja <archit@ti.com>
Cc: linux-media@vger.kernel.org, k.debski@samsung.com,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/2] v4l: ti-vpe: Some VPE fixes
Date: Tue, 17 Dec 2013 08:52:29 +0100 [thread overview]
Message-ID: <52B002BD.6000105@xs4all.nl> (raw)
In-Reply-To: <1386071473-10808-1-git-send-email-archit@ti.com>
On 12/03/2013 12:51 PM, Archit Taneja wrote:
> This series fixes 2 issues in the VPE driver. The first fix allows us to use
> UYVY color format for source and destination buffers. The second fix makes sure
> we don't set pixel format widths which the VPDMA HW can't support. None of these
> fixes are fatal, so they don't necessarily need to go in for the 3.13-rc fixes.
>
> Archit Taneja (2):
> v4l: ti-vpe: Fix the data_type value for UYVY VPDMA format
> v4l: ti-vpe: make sure VPDMA line stride constraints are met
>
> drivers/media/platform/ti-vpe/vpdma.c | 4 +--
> drivers/media/platform/ti-vpe/vpdma.h | 5 ++-
> drivers/media/platform/ti-vpe/vpdma_priv.h | 2 +-
> drivers/media/platform/ti-vpe/vpe.c | 53 ++++++++++++++++++++++--------
> 4 files changed, 47 insertions(+), 17 deletions(-)
>
For this patch series:
Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
Regards,
Hans
next prev parent reply other threads:[~2013-12-17 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 11:51 [PATCH 0/2] v4l: ti-vpe: Some VPE fixes Archit Taneja
2013-12-03 11:51 ` Archit Taneja
2013-12-03 11:51 ` [PATCH 1/2] v4l: ti-vpe: Fix the data_type value for UYVY VPDMA format Archit Taneja
2013-12-03 11:51 ` Archit Taneja
2013-12-03 11:51 ` [PATCH 2/2] v4l: ti-vpe: make sure VPDMA line stride constraints are met Archit Taneja
2013-12-03 11:51 ` Archit Taneja
2013-12-17 7:52 ` Hans Verkuil [this message]
2013-12-17 8:03 ` [PATCH 0/2] v4l: ti-vpe: Some VPE fixes Hans Verkuil
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=52B002BD.6000105@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=archit@ti.com \
--cc=k.debski@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@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.