mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
To: LMML <linux-media@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	Sekhar Nori <nsekhar@ti.com>,
	DLOS <davinci-linux-open-source@linux.davincidsp.com>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	LAK <linux-arm-kernel@lists.infradead.org>,
	"Lad, Prabhakar" <prabhakar.lad@ti.com>
Subject: [PATCH RFC 0/3] vpif capture support for async subdevice probing
Date: Wed,  9 Jan 2013 19:11:24 +0530	[thread overview]
Message-ID: <1357738887-8701-1-git-send-email-prabhakar.lad@ti.com> (raw)

This patch series adds support for vpif capture driver to support
asynchronously register subdevices. The second patch add support for
tvp514x decoder to support v4l-async and the last patch adds support
for da850 evm to support v4l-async for vpif capture.

This patch is based on v4l2-async patch
(http://www.spinics.net/lists/linux-media/msg58420.html) from Guennadi.

Need for this support:
Currently bridge device drivers register devices for all subdevices 
synchronously, tupically, during their probing. E.g. if an I2C CMOS sensor 
is attached to a video bridge device, the bridge driver will create an I2C 
device and wait for the respective I2C driver to probe. This makes linking 
of devices straight forward, but this approach cannot be used with 
intrinsically asynchronous and unordered device registration systems like 
the Flattened Device Tree.

Similar impletation is to be done for vpif disaply, based on review comments
on this series.

Lad, Prabhakar (3):
  davinci: vpif: capture: add V4L2-async support
  tvp514x: support asynchronous probing
  ARM: da850/omap-l138: vpif capture convert to asynchronously register
    of subdev

 arch/arm/mach-davinci/board-da850-evm.c       |   57 +++++++-
 drivers/media/i2c/tvp514x.c                   |   20 ++-
 drivers/media/platform/davinci/vpif_capture.c |  171 ++++++++++++++++++-------
 drivers/media/platform/davinci/vpif_capture.h |    2 +
 include/media/davinci/vpif_types.h            |    2 +
 5 files changed, 192 insertions(+), 60 deletions(-)

-- 
1.7.4.1


             reply	other threads:[~2013-01-09 13:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09 13:41 Lad, Prabhakar [this message]
2013-01-09 13:41 ` [PATCH RFC 1/3] davinci: vpif: capture: add V4L2-async support Lad, Prabhakar
2013-01-09 15:42   ` Hans Verkuil
2013-01-09 17:49     ` Prabhakar Lad
2013-01-09 13:41 ` [PATCH RFC 2/3] tvp514x: support asynchronous probing Lad, Prabhakar
2013-01-09 13:41 ` [PATCH RFC 3/3] ARM: da850/omap-l138: vpif capture convert to asynchronously register of subdev Lad, Prabhakar

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=1357738887-8701-1-git-send-email-prabhakar.lad@ti.com \
    --to=prabhakar.csengg@gmail.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=hans.verkuil@cisco.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=nsekhar@ti.com \
    --cc=prabhakar.lad@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®