linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org, devicetree@vger.kernel.org
Cc: pavel@ucw.cz
Subject: [RFC 0/3] Document bindings for camera modules and associated flash devices
Date: Tue,  2 May 2017 13:25:46 +0300	[thread overview]
Message-ID: <1493720749-31509-1-git-send-email-sakari.ailus@linux.intel.com> (raw)

Hi folks,

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>

-- 
Regards,
Sakari

             reply	other threads:[~2017-05-02 10:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02 10:25 Sakari Ailus [this message]
2017-05-02 10:25 ` [RFC 1/3] dt: bindings: Add a binding for flash devices associated to a sensor Sakari Ailus
2017-05-04 14:27   ` Sebastian Reichel
2017-05-05  8:28     ` Sakari Ailus
2017-05-05  8:38       ` Sebastian Reichel
2017-05-02 10:25 ` [RFC 2/3] dt: bindings: Add lens-focus binding for image sensors Sakari Ailus
2017-05-04 14:33   ` Sebastian Reichel
2017-05-02 10:25 ` [RFC 3/3] dt: bindings: Add a binding for referencing EEPROM from camera sensors Sakari Ailus
2017-05-04 14:38   ` Sebastian Reichel
2017-05-05  8:49     ` Sakari Ailus
2017-05-04 22:01 ` [RFC 0/3] Document bindings for camera modules and associated flash devices Pavel Machek

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=1493720749-31509-1-git-send-email-sakari.ailus@linux.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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).