From: Randy Li <ayaka@soulik.info>
To: devicetree@vger.kernel.org
Cc: mark.rutland@arm.com, linux@armlinux.org.uk, kgene@kernel.org,
krzk@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
inki.dae@samsung.com, jy0922.shim@samsung.com,
kyungmin.park@samsung.com, dri-devel@lists.freedesktop.org,
Randy Li <ayaka@soulik.info>
Subject: [PATCH RFC] ARM: dts: samsung: add rga-lvds panel in itop elite
Date: Tue, 30 Aug 2016 06:50:02 +0800 [thread overview]
Message-ID: <1472511002-9019-1-git-send-email-ayaka@soulik.info> (raw)
It is actually a lvds panel connected through a rga-lvds bridge.
But I really have no idea about what does a port mean in fimd node.
Also how should I configure this panel size? I think the i2c found
on the panel schematic, but it more likely to be used a touch screen
touth. Also the touch screen is not supported in currently driver.
Signed-off-by: Randy Li <ayaka@soulik.info>
---
arch/arm/boot/dts/exynos4412-itop-elite.dts | 35 ++++++++++++++++++++++++++---
1 file changed, 32 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/exynos4412-itop-elite.dts b/arch/arm/boot/dts/exynos4412-itop-elite.dts
index e1cda54..2d67385 100644
--- a/arch/arm/boot/dts/exynos4412-itop-elite.dts
+++ b/arch/arm/boot/dts/exynos4412-itop-elite.dts
@@ -139,6 +139,20 @@
assigned-clocks = <&clock CLK_MOUT_CAM0>;
assigned-clock-parents = <&clock CLK_XUSBXTI>;
};
+
+ vcc_sys_lcd: sys-lcd {
+ compatible = "regulator-fixed";
+ regulator-name = "vcc_5v";
+ regulator-min-microvolt = <5000000>;
+ regulator-max-microvolt = <5000000>;
+ gpio = <&gpl0 4 GPIO_ACTIVE_HIGH>;
+ };
+
+ panel: panel {
+ ddc-i2c-bus = <&i2c_3>;
+ power-supply = <&vcc_sys_lcd>;
+ enable-gpios = <&gpl0 2 GPIO_ACTIVE_HIGH>;
+ };
};
&pinctrl_1 {
@@ -221,9 +235,6 @@
};
&pwm {
- pinctrl-0 = <&pwm1_out>;
- pinctrl-names = "default";
- samsung,pwm-outputs = <1>;
status = "okay";
};
@@ -239,3 +250,21 @@
assigned-clock-parents = <&clock CLK_MOUT_MPLL_USER_T>;
assigned-clock-rates = <0>, <176000000>;
};
+
+&i2c_3 {
+ status = "okay";
+};
+
+&fimd {
+ pinctrl-0 = <&lcd_clk &lcd_data24 &pwm1_out>;
+ pinctrl-names = "default";
+ status = "okay";
+ #address-cells = <1>;
+ #size-cells = <0>;
+ port@0 {
+ reg = <0>;
+ rga_lvds: endpoint {
+ remote-endpoint = <&panel>;
+ };
+ };
+};
--
2.7.4
next reply other threads:[~2016-08-29 22:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 22:50 Randy Li [this message]
2016-08-31 12:30 ` [PATCH RFC] ARM: dts: samsung: add rga-lvds panel in itop elite Andrzej Hajda
2016-08-31 17:53 ` ayaka
2016-08-31 17:55 ` ayaka
2016-09-01 7:04 ` Andrzej Hajda
[not found] ` <94dc2e0d-2521-a636-ee3d-90168f30fe28-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-09-01 8:24 ` Ayaka
2016-09-01 8:53 ` Andrzej Hajda
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=1472511002-9019-1-git-send-email-ayaka@soulik.info \
--to=ayaka@soulik.info \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
/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).