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
Subject: [RFC 3/3] dt: bindings: Add a binding for referencing EEPROM from camera sensors
Date: Tue, 2 May 2017 13:25:49 +0300 [thread overview]
Message-ID: <1493720749-31509-4-git-send-email-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <1493720749-31509-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Many camera sensor devices contain EEPROM chips that describe the
properties of a given unit --- the data is specific to a given unit can
thus is not stored e.g. in user space or the driver.
Some sensors embed the EEPROM chip and it can be accessed through the
sensor's I²C interface. This property is to be used for devices where the
EEPROM chip is accessed through a different I²C address than the sensor.
The intent is to later provide this information to the user space.
Signed-off-by: Sakari Ailus <sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
---
Documentation/devicetree/bindings/media/video-interfaces.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/media/video-interfaces.txt b/Documentation/devicetree/bindings/media/video-interfaces.txt
index e52aefc..9bd2005 100644
--- a/Documentation/devicetree/bindings/media/video-interfaces.txt
+++ b/Documentation/devicetree/bindings/media/video-interfaces.txt
@@ -80,6 +80,9 @@ Optional properties
- lens-focus: A phandle to the node of the lens. Only valid for device
nodes that are related to an image sensor.
+- eeprom: A phandle to the node of the related EEPROM. Only valid for
+ device nodes that are related to an image sensor.
+
Optional endpoint properties
----------------------------
--
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
next prev parent reply other threads:[~2017-05-02 10:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 10:25 [RFC 0/3] Document bindings for camera modules and associated flash devices Sakari Ailus
[not found] ` <1493720749-31509-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
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 ` Sakari Ailus [this message]
[not found] ` <1493720749-31509-4-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-05-04 14:38 ` [RFC 3/3] dt: bindings: Add a binding for referencing EEPROM from camera sensors 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-4-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 \
/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).