All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: linux-media@vger.kernel.org
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>
Subject: [PATCH 0/2] omap_vout: clean up and convert to vb2
Date: Tue, 30 Jul 2019 08:38:15 +0200	[thread overview]
Message-ID: <20190730063817.47674-1-hverkuil-cisco@xs4all.nl> (raw)

While working on the m2m-deinterlace driver I needed to test it,
and the easiest way to do that was with a Pandaboard. While
doing that I found a bug in the omap-dma driver:

https://patchwork.linuxtv.org/patch/57778/

That bug affected omap_vout as well, so the next step was to
test that driver. And if I had to do that, I might as well
take the opportunity to clean up this driver and convert it
to vb2 so that it passes the v4l2-compliance tests.

Hence this series.

Note that this series relies on a second patch as well:

https://patchwork.linuxtv.org/patch/57779/

Tested on a Pandaboard and a Beagle XM board.

Regards,

	Hans

Hans Verkuil (2):
  omap_vout: fix various v4l2-compliance failures
  omap_vout: convert to vb2

 drivers/media/platform/omap/Kconfig          |    3 +-
 drivers/media/platform/omap/omap_vout.c      | 1011 +++++-------------
 drivers/media/platform/omap/omap_vout_vrfb.c |   22 +-
 drivers/media/platform/omap/omap_vout_vrfb.h |    4 +-
 drivers/media/platform/omap/omap_voutdef.h   |   45 +-
 drivers/media/platform/omap/omap_voutlib.c   |    6 +-
 6 files changed, 304 insertions(+), 787 deletions(-)

-- 
2.20.1


             reply	other threads:[~2019-07-30  6:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30  6:38 Hans Verkuil [this message]
2019-07-30  6:38 ` [PATCH 1/2] omap_vout: fix various v4l2-compliance failures Hans Verkuil
2019-07-30  6:38 ` [PATCH 2/2] omap_vout: convert to vb2 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=20190730063817.47674-1-hverkuil-cisco@xs4all.nl \
    --to=hverkuil-cisco@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=tomi.valkeinen@ti.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 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.