From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Robert Krakora <rob.krakora@messagenetsystems.com>
Cc: Oleksij Rempel <bug-track@fisher-privat.net>,
linux-uvc-devel@lists.sourceforge.net, sakari.ailus@iki.fi,
linux-media@vger.kernel.org
Subject: Re: [linux-uvc-devel] [RFC] Media controller entity information ioctl [was "Re: [patch] suggestion for media framework"]
Date: Fri, 08 Jun 2012 04:46:37 +0200 [thread overview]
Message-ID: <1915602.ON5YbSOUmP@avalon> (raw)
In-Reply-To: <CA+Dpati=kqq52JMu0gJBT=VeLGLXVgd3E-aY4YmfkXytMCDzyA@mail.gmail.com>
Hi Robert,
On Monday 04 June 2012 10:11:33 Robert Krakora wrote:
> When you say "static" you mean items that are "well known" by the system by
> reading a registry at initialization?
By static I mean items that are initialized at driver initialization time and
not modified afterwards. I don't think we should support adding/removing items
at runtime, at least in the first version.
> When a new device exposes functionality that necessitates the creation of a
> new "static" item then how does the registry get updated to reflect this or
> am I misunderstanding?
Item types should be defined in a kernel header and documented. If a driver
needs a new item types, the driver developer should add the new type to the
header and document it.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2012-06-08 2:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FCB9C12.1@fisher-privat.net>
2012-06-04 14:02 ` [RFC] Media controller entity information ioctl [was "Re: [patch] suggestion for media framework"] Laurent Pinchart
2012-06-04 14:17 ` Hans Verkuil
2012-06-04 15:35 ` Oleksij Rempel
2012-06-05 20:44 ` Sakari Ailus
[not found] ` <CA+Dpati=kqq52JMu0gJBT=VeLGLXVgd3E-aY4YmfkXytMCDzyA@mail.gmail.com>
2012-06-08 2:46 ` Laurent Pinchart [this message]
2012-06-21 17:11 ` [linux-uvc-devel] " Oleksij Rempel
2012-06-21 23:12 ` 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=1915602.ON5YbSOUmP@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=bug-track@fisher-privat.net \
--cc=linux-media@vger.kernel.org \
--cc=linux-uvc-devel@lists.sourceforge.net \
--cc=rob.krakora@messagenetsystems.com \
--cc=sakari.ailus@iki.fi \
/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).