From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: linux-leds@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: kyungmin.park@samsung.com, pavel@ucw.cz, cooloney@gmail.com,
rpurdie@rpsys.net, sakari.ailus@iki.fi, s.nawrocki@samsung.com,
Jacek Anaszewski <j.anaszewski@samsung.com>
Subject: [PATCH/RFC v13 11/13] DT: Add documentation for exynos4-is 'flashes' property
Date: Thu, 12 Mar 2015 16:45:12 +0100 [thread overview]
Message-ID: <1426175114-14876-12-git-send-email-j.anaszewski@samsung.com> (raw)
In-Reply-To: <1426175114-14876-1-git-send-email-j.anaszewski@samsung.com>
This patch adds a description of 'flashes' property
to the samsung-fimc.txt.
Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
Acked-by: Kyungmin Park <kyungmin.park@samsung.com>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>
---
.../devicetree/bindings/media/samsung-fimc.txt | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/bindings/media/samsung-fimc.txt b/Documentation/devicetree/bindings/media/samsung-fimc.txt
index 922d6f8..cb0e263 100644
--- a/Documentation/devicetree/bindings/media/samsung-fimc.txt
+++ b/Documentation/devicetree/bindings/media/samsung-fimc.txt
@@ -40,6 +40,13 @@ should be inactive. For the "active-a" state the camera port A must be activated
and the port B deactivated and for the state "active-b" it should be the other
way around.
+Optional properties:
+
+- flashes - Array of phandles to the flash LEDs that can be controlled by the
+ sub-devices contained in this media device. Flash LED is
+ represented by a child node of a flash LED device
+ (see Documentation/devicetree/bindings/leds/common.txt).
+
The 'camera' node must include at least one 'fimc' child node.
@@ -166,6 +173,7 @@ Example:
clock-output-names = "cam_a_clkout", "cam_b_clkout";
pinctrl-names = "default";
pinctrl-0 = <&cam_port_a_clk_active>;
+ flashes = <&camera_flash>, <&system_torch>;
status = "okay";
#address-cells = <1>;
#size-cells = <1>;
--
1.7.9.5
next prev parent reply other threads:[~2015-03-12 15:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 15:45 [PATCH/RFC v13 00/13] LED / flash API integration Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 01/13] leds: flash: Fix the size of sysfs_groups array Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 02/13] dt-binding: leds: Add common LED DT bindings macros Jacek Anaszewski
2015-03-18 1:33 ` Bryan Wu
2015-03-12 15:45 ` [PATCH/RFC v13 03/13] leds: Add support for max77693 mfd flash cell Jacek Anaszewski
2015-03-23 11:56 ` Lee Jones
2015-03-23 12:07 ` Lee Jones
2015-03-12 15:45 ` [PATCH/RFC v13 04/13] DT: Add documentation for the mfd Maxim max77693 Jacek Anaszewski
2015-03-23 12:07 ` Lee Jones
2015-03-23 14:22 ` Pavel Machek
2015-03-23 15:02 ` Lee Jones
2015-03-23 15:48 ` Pavel Machek
2015-03-23 15:59 ` Lee Jones
2015-03-23 18:28 ` Sylwester Nawrocki
2015-04-02 14:50 ` Pavel Machek
2015-04-02 19:33 ` Lee Jones
2015-03-12 15:45 ` [PATCH/RFC v13 05/13] leds: Add driver for AAT1290 current regulator Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 06/13] of: Add Skyworks Solutions, Inc. vendor prefix Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 07/13] DT: Add documentation for the Skyworks AAT1290 Jacek Anaszewski
2015-03-18 10:28 ` Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 08/13] exynos4-is: Add support for v4l2-flash subdevs Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 09/13] media: Add registration helpers for V4L2 flash sub-devices Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 10/13] Documentation: leds: Add description of v4l2-flash sub-device Jacek Anaszewski
2015-03-18 12:39 ` Sakari Ailus
2015-03-18 14:36 ` Jacek Anaszewski
2015-03-12 15:45 ` Jacek Anaszewski [this message]
2015-03-12 15:45 ` [PATCH/RFC v13 12/13] leds: max77693: add support for V4L2 Flash sub-device Jacek Anaszewski
2015-03-12 15:45 ` [PATCH/RFC v13 13/13] leds: aat1290: " Jacek Anaszewski
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=1426175114-14876-12-git-send-email-j.anaszewski@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=cooloney@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=s.nawrocki@samsung.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
all inboxes | Powered by JetHome®