From: Sakari Ailus <sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: pavel-+ZI9xUNit7I@public.gmane.org,
sebastian.reichel-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org
Subject: [RFC v2 0/3] Document bindings for camera modules and associated flash devices
Date: Fri, 5 May 2017 11:48:27 +0300 [thread overview]
Message-ID: <1493974110-26510-1-git-send-email-sakari.ailus@linux.intel.com> (raw)
This RFC patchset documents properties commonly required by camera modules
and associated camera flash devices.
The camera module is essentially a package consisting of an image sensor,
a lens, possibly a voice coil to move the lens and a number of other
things that at least the drivers need not to know of. All the devices in a
camera module are declared separately in the system and as such the fact
that they come in a single package isn't generally very useful to driver
software.
I'm sending the set as RFC as there's no driver implementation, and a
dependency to the V4L2 async changes:
<URL:http://www.spinics.net/lists/linux-media/msg114915.html>
since RFC v1:
- Remove sentences elaborating applicability of the bindings.
- Say a LED driver is a piece of hardware.
- Otherwise reformulate the descriptions according to the comments.
Sakari Ailus (3):
dt: bindings: Add a binding for flash devices associated to a sensor
dt: bindings: Add lens-focus binding for image sensors
dt: bindings: Add a binding for referencing EEPROM from camera sensors
.../devicetree/bindings/media/video-interfaces.txt | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org, devicetree@vger.kernel.org
Cc: pavel@ucw.cz, sebastian.reichel@collabora.co.uk
Subject: [RFC v2 0/3] Document bindings for camera modules and associated flash devices
Date: Fri, 5 May 2017 11:48:27 +0300 [thread overview]
Message-ID: <1493974110-26510-1-git-send-email-sakari.ailus@linux.intel.com> (raw)
This RFC patchset documents properties commonly required by camera modules
and associated camera flash devices.
The camera module is essentially a package consisting of an image sensor,
a lens, possibly a voice coil to move the lens and a number of other
things that at least the drivers need not to know of. All the devices in a
camera module are declared separately in the system and as such the fact
that they come in a single package isn't generally very useful to driver
software.
I'm sending the set as RFC as there's no driver implementation, and a
dependency to the V4L2 async changes:
<URL:http://www.spinics.net/lists/linux-media/msg114915.html>
since RFC v1:
- Remove sentences elaborating applicability of the bindings.
- Say a LED driver is a piece of hardware.
- Otherwise reformulate the descriptions according to the comments.
Sakari Ailus (3):
dt: bindings: Add a binding for flash devices associated to a sensor
dt: bindings: Add lens-focus binding for image sensors
dt: bindings: Add a binding for referencing EEPROM from camera sensors
.../devicetree/bindings/media/video-interfaces.txt | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
--
2.7.4
next reply other threads:[~2017-05-05 8:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 8:48 Sakari Ailus [this message]
2017-05-05 8:48 ` [RFC v2 0/3] Document bindings for camera modules and associated flash devices Sakari Ailus
[not found] ` <1493974110-26510-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-05-05 8:48 ` [RFC v2 1/3] dt: bindings: Add a binding for flash devices associated to a sensor Sakari Ailus
2017-05-05 8:48 ` Sakari Ailus
[not found] ` <1493974110-26510-2-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-05-08 17:13 ` Rob Herring
2017-05-08 17:13 ` Rob Herring
2017-05-05 8:48 ` [RFC v2 3/3] dt: bindings: Add a binding for referencing EEPROM from camera sensors Sakari Ailus
2017-05-05 8:48 ` Sakari Ailus
[not found] ` <1493974110-26510-4-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-05-05 9:10 ` Sebastian Reichel
2017-05-05 9:10 ` Sebastian Reichel
2017-05-08 17:24 ` Rob Herring
2017-05-29 12:20 ` Sakari Ailus
2017-05-29 12:39 ` Daniel Mack
[not found] ` <c7a98681-4c95-0103-96ee-97ca6a02d9b3-cYrQPVfZoowdnm+yROfE0A@public.gmane.org>
2017-05-29 13:05 ` Sakari Ailus
2017-05-29 13:05 ` Sakari Ailus
2017-05-31 17:37 ` Pavel Machek
2017-06-01 8:00 ` Sakari Ailus
2017-06-01 8:00 ` Sakari Ailus
2017-05-05 8:48 ` [RFC v2 2/3] dt: bindings: Add lens-focus binding for image sensors Sakari Ailus
[not found] ` <1493974110-26510-3-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-05-05 9:09 ` Sebastian Reichel
2017-05-05 9:09 ` Sebastian Reichel
2017-05-08 17:14 ` Rob Herring
2017-05-08 17:14 ` Rob Herring
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=1493974110-26510-1-git-send-email-sakari.ailus@linux.intel.com \
--to=sakari.ailus-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@public.gmane.org \
--cc=sebastian.reichel-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.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.