From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, sakari.ailus@maxwell.research.nokia.com
Subject: Re: [RFC/PATCH v4 00/11] Media controller (core and V4L2)
Date: Wed, 08 Sep 2010 22:44:15 -0300 [thread overview]
Message-ID: <4C883BEF.5020504@redhat.com> (raw)
In-Reply-To: <1282318153-18885-1-git-send-email-laurent.pinchart@ideasonboard.com>
Em 20-08-2010 12:29, Laurent Pinchart escreveu:
> Hi everybody,
>
> Here's the fourth version of the media controller patches. All comments received
> so far have hopefully been incorporated.
>
> Compared to the previous version, the patches have been rebased on top of 2.6.35
> and a MEDIA_IOC_DEVICE_INFO ioctl has been added.
>
> I won't submit a rebased version of the V4L2 API additions and OMAP3 ISP patches
> right now. I will first clean up (and document) the V4L2 API additions patches,
> and I will submit them as a proper RFC instead of sample code.
Hi Laurent,
Sorry for a late review on the media controller API. I got flooded by patches and
other work since the merge window. Anyway, just finished my review, and sent a
per-patch comment for most patches.
One general comment about it: the userspace API should be documented via DocBook,
to be consistent with V4L2 and DVB API specs.
It should also be clear at the API specs there that not all media drivers will
implement the media controller API, as its main focus is to allow better control
of SoC devices, where there are needs to control some intrinsic characteristics of
parts of the devices, complementing the V4L2 spec.
This means that it is needed to add some comments at the kernelspace API doc, saying that
the drivers implementing the media controller API are required to work properly even
when userspace is not using the media controller API;
This also means that it is needed to add some comments at the userspace API doc, saying
that userspace applications should not assume that media drivers will implement the
media controller API. So, userspace applications implementing the media controller
and V4L2 API's are required to work properly if the device doesn't present a media
controler API interface. It should also say that no driver should just implement the
media controller API.
>
> Laurent Pinchart (9):
> media: Media device node support
> media: Media device
> media: Entities, pads and links
> media: Media device information query
> media: Entities, pads and links enumeration
> media: Links setup
> v4l: Add a media_device pointer to the v4l2_device structure
> v4l: Make video_device inherit from media_entity
> v4l: Make v4l2_subdev inherit from media_entity
>
> Sakari Ailus (2):
> media: Entity graph traversal
> media: Reference count and power handling
>
> Documentation/media-framework.txt | 574 ++++++++++++++++++++++++
> Documentation/video4linux/v4l2-framework.txt | 72 +++-
> drivers/media/Makefile | 8 +-
> drivers/media/media-device.c | 377 ++++++++++++++++
> drivers/media/media-devnode.c | 310 +++++++++++++
> drivers/media/media-entity.c | 614 ++++++++++++++++++++++++++
> drivers/media/video/v4l2-dev.c | 35 ++-
> drivers/media/video/v4l2-device.c | 45 ++-
> drivers/media/video/v4l2-subdev.c | 27 ++-
> include/linux/media.h | 105 +++++
> include/media/media-device.h | 90 ++++
> include/media/media-devnode.h | 78 ++++
> include/media/media-entity.h | 112 +++++
> include/media/v4l2-dev.h | 6 +
> include/media/v4l2-device.h | 2 +
> include/media/v4l2-subdev.h | 7 +
> 16 files changed, 2440 insertions(+), 22 deletions(-)
> create mode 100644 Documentation/media-framework.txt
> create mode 100644 drivers/media/media-device.c
> create mode 100644 drivers/media/media-devnode.c
> create mode 100644 drivers/media/media-entity.c
> create mode 100644 include/linux/media.h
> create mode 100644 include/media/media-device.h
> create mode 100644 include/media/media-devnode.h
> create mode 100644 include/media/media-entity.h
>
next prev parent reply other threads:[~2010-09-09 1:44 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 15:29 [RFC/PATCH v4 00/11] Media controller (core and V4L2) Laurent Pinchart
2010-08-20 15:29 ` [RFC/PATCH v4 01/11] media: Media device node support Laurent Pinchart
2010-08-20 15:29 ` [RFC/PATCH v4 02/11] media: Media device Laurent Pinchart
2010-08-28 10:26 ` Hans Verkuil
2010-09-01 13:51 ` Laurent Pinchart
2010-08-20 15:29 ` [RFC/PATCH v4 03/11] media: Entities, pads and links Laurent Pinchart
2010-08-28 10:31 ` Hans Verkuil
2010-09-01 13:51 ` Laurent Pinchart
2010-09-09 0:41 ` Mauro Carvalho Chehab
2010-09-14 13:51 ` Laurent Pinchart
2010-08-20 15:29 ` [RFC/PATCH v4 04/11] media: Entity graph traversal Laurent Pinchart
2010-09-09 0:46 ` Mauro Carvalho Chehab
2010-09-14 13:59 ` Laurent Pinchart
2010-08-20 15:29 ` [RFC/PATCH v4 05/11] media: Reference count and power handling Laurent Pinchart
2010-09-09 0:58 ` Mauro Carvalho Chehab
2010-09-11 20:38 ` Sakari Ailus
2010-09-16 8:46 ` Laurent Pinchart
2010-09-16 10:35 ` Mauro Carvalho Chehab
2010-09-16 11:11 ` Laurent Pinchart
2010-08-20 15:29 ` [RFC/PATCH v4 06/11] media: Media device information query Laurent Pinchart
2010-08-28 10:44 ` Hans Verkuil
2010-09-01 13:58 ` Laurent Pinchart
2010-08-20 15:29 ` [RFC/PATCH v4 07/11] media: Entities, pads and links enumeration Laurent Pinchart
2010-08-28 11:02 ` Hans Verkuil
2010-09-01 14:05 ` Laurent Pinchart
2010-09-06 16:51 ` Hans Verkuil
2010-09-16 9:20 ` Laurent Pinchart
2010-09-16 15:36 ` Sakari Ailus
2010-09-16 23:05 ` Laurent Pinchart
2010-08-20 15:29 ` [RFC/PATCH v4 08/11] media: Links setup Laurent Pinchart
2010-08-28 11:14 ` Hans Verkuil
2010-09-01 14:08 ` Laurent Pinchart
2010-09-06 17:09 ` Hans Verkuil
2010-09-16 9:02 ` Laurent Pinchart
2010-09-09 1:14 ` Mauro Carvalho Chehab
2010-09-16 9:04 ` Laurent Pinchart
2010-08-20 15:29 ` [RFC/PATCH v4 09/11] v4l: Add a media_device pointer to the v4l2_device structure Laurent Pinchart
2010-08-20 15:29 ` [RFC/PATCH v4 10/11] v4l: Make video_device inherit from media_entity Laurent Pinchart
2010-08-20 15:29 ` [RFC/PATCH v4 11/11] v4l: Make v4l2_subdev " Laurent Pinchart
2010-09-09 1:25 ` Mauro Carvalho Chehab
2010-09-16 8:55 ` Laurent Pinchart
2010-09-09 1:44 ` Mauro Carvalho Chehab [this message]
2010-09-14 12:25 ` [RFC/PATCH v4 00/11] Media controller (core and V4L2) Laurent Pinchart
2010-09-14 13:24 ` Hans Verkuil
2010-09-14 13:49 ` Laurent Pinchart
2010-09-14 13:34 ` Mauro Carvalho Chehab
2010-09-14 13:48 ` Laurent Pinchart
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=4C883BEF.5020504@redhat.com \
--to=mchehab@redhat.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@maxwell.research.nokia.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;
as well as URLs for NNTP newsgroup(s).