From: Arun Kumar K <arun.kk@samsung.com>
To: linux-media@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
devicetree@vger.kernel.org
Cc: s.nawrocki@samsung.com, hverkuil@xs4all.nl,
swarren@wwwdotorg.org, a.hajda@samsung.com,
sachin.kamat@linaro.org, shaik.ameer@samsung.com,
kilyeon.im@samsung.com, arunkk.samsung@gmail.com
Subject: [PATCH v5 02/13] [media] exynos5-fimc-is: Add Exynos5 FIMC-IS device tree bindings documentation
Date: Wed, 14 Aug 2013 10:16:03 +0530 [thread overview]
Message-ID: <1376455574-15560-3-git-send-email-arun.kk@samsung.com> (raw)
In-Reply-To: <1376455574-15560-1-git-send-email-arun.kk@samsung.com>
The patch adds the DT binding documentation for Samsung
Exynos5 SoC series imaging subsystem (FIMC-IS).
Signed-off-by: Arun Kumar K <arun.kk@samsung.com>
Reviewed-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
---
.../devicetree/bindings/media/exynos5-fimc-is.txt | 47 ++++++++++++++++++++
1 file changed, 47 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/exynos5-fimc-is.txt
diff --git a/Documentation/devicetree/bindings/media/exynos5-fimc-is.txt b/Documentation/devicetree/bindings/media/exynos5-fimc-is.txt
new file mode 100644
index 0000000..bfd36df
--- /dev/null
+++ b/Documentation/devicetree/bindings/media/exynos5-fimc-is.txt
@@ -0,0 +1,47 @@
+Samsung EXYNOS5 SoC series Imaging Subsystem (FIMC-IS)
+------------------------------------------------------
+
+The camera subsystem on Samsung Exynos5 SoC has some changes relative
+to previous SoC versions. Exynos5 has almost similar MIPI-CSIS and
+FIMC-LITE IPs but has a much improved version of FIMC-IS which can
+handle sensor controls and camera post-processing operations. The
+Exynos5 FIMC-IS has a dedicated ARM Cortex A5 processor, many
+post-processing blocks (ISP, DRC, FD, ODC, DIS, 3DNR) and two
+dedicated scalers (SCC and SCP).
+
+fimc-is node
+------------
+
+Required properties:
+
+- compatible : must be "samsung,exynos5250-fimc-is"
+- reg : physical base address and size of the memory mapped
+ registers
+- interrupt-parent : parent interrupt controller
+- interrupts : fimc-is interrupt to the parent combiner
+- clocks : list of clock specifiers, corresponding to entries in
+ clock-names property;
+- clock-names : must contain "isp", "mcu_isp", "isp_div0", "isp_div1",
+ "isp_divmpwm", "mcu_isp_div0", "mcu_isp_div1" entries,
+ matching entries in the clocks property.
+- pmu : phandle to the fimc-is pmu node describing the register
+ base and size for FIMC-IS PMU.
+
+i2c-isp (ISP I2C bus controller) nodes
+------------------------------------------
+
+Required properties:
+
+- compatible : should be "samsung,exynos4212-i2c-isp" for Exynos4212,
+ Exynos4412 and Exynos5250 SoCs;
+- reg : physical base address and length of the registers set;
+- clocks : must contain gate clock specifier for this controller;
+- clock-names : must contain "i2c_isp" entry.
+
+For the i2c-isp node, it is required to specify a pinctrl state named "default",
+according to the pinctrl bindings defined in ../pinctrl/pinctrl-bindings.txt.
+
+Device tree nodes of the image sensors' controlled directly by the FIMC-IS
+firmware must be child nodes of their corresponding ISP I2C bus controller node.
+The data link of these image sensors must be specified using the common video
+interfaces bindings, defined in video-interfaces.txt.
--
1.7.9.5
next prev parent reply other threads:[~2013-08-14 4:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 4:46 [PATCH v5 00/13] Exynos5 IS driver Arun Kumar K
2013-08-14 4:46 ` [PATCH v5 01/13] [media] exynos5-is: Adding media device driver for exynos5 Arun Kumar K
2013-08-14 4:59 ` Sachin Kamat
2013-08-14 5:09 ` Arun Kumar K
2013-08-15 11:32 ` Sylwester Nawrocki
2013-08-14 4:46 ` Arun Kumar K [this message]
2013-08-15 15:09 ` [PATCH v5 02/13] [media] exynos5-fimc-is: Add Exynos5 FIMC-IS device tree bindings documentation Sylwester Nawrocki
2013-08-14 4:46 ` [PATCH v5 03/13] [media] exynos5-fimc-is: Add driver core files Arun Kumar K
2013-08-14 4:46 ` [PATCH v5 04/13] [media] exynos5-fimc-is: Add common driver header files Arun Kumar K
2013-08-14 4:46 ` [PATCH v5 05/13] [media] exynos5-fimc-is: Add register definition and context header Arun Kumar K
2013-08-14 4:46 ` [PATCH v5 06/13] [media] exynos5-fimc-is: Add isp subdev Arun Kumar K
2013-08-14 4:46 ` [PATCH v5 07/13] [media] exynos5-fimc-is: Add scaler subdev Arun Kumar K
2013-08-14 4:46 ` [PATCH v5 08/13] [media] exynos5-fimc-is: Add sensor interface Arun Kumar K
2013-08-14 4:46 ` [PATCH v5 09/13] [media] exynos5-fimc-is: Add the hardware pipeline control Arun Kumar K
2013-08-14 4:46 ` [PATCH v5 10/13] [media] exynos5-fimc-is: Add the hardware interface module Arun Kumar K
2013-08-14 4:46 ` [PATCH v5 11/13] [media] exynos5-is: Add Kconfig and Makefile Arun Kumar K
2013-08-14 4:46 ` [PATCH v5 12/13] V4L: s5k6a3: Change sensor min/max resolutions Arun Kumar K
2013-08-14 4:46 ` [PATCH v5 13/13] V4L: Add driver for s5k4e5 image sensor Arun Kumar K
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=1376455574-15560-3-git-send-email-arun.kk@samsung.com \
--to=arun.kk@samsung.com \
--cc=a.hajda@samsung.com \
--cc=arunkk.samsung@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=kilyeon.im@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=sachin.kamat@linaro.org \
--cc=shaik.ameer@samsung.com \
--cc=swarren@wwwdotorg.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).