what VSPD Means
hi all, I am on a small research on VSPD in kernel.. I googled it a lot but couldn't get a clear explanation..In my knowledge , it is a memory to memory maped video processing engine..It can directly interact to DU etc...But I came accross to know that v4l2 in linux supports VSPD...is v4l2 a driver?...hopping for your reply --- ComeLet's enjoy the world of Open Source --- Best regards, Stuvart
About VSPD
hello Laurent and all, Can anybody give me an insight to VSPD .Recently I am going through the term VSPD..Is it associated with Display Unit ? ..It will be a help if someone share some links about VSPD..I am a beginner in both kernel and RCar families..Thanks in advance Best Regards, Jithin T Raj
Writing data to Video buffer
Hi all, I have an RCAR E2 Board with me which runs smoothly under linux 4.8 ..Now I want to make display output from HDMI as flipped 180 degree ..Through which area that I have to focus to do so.here I pointed only an example only. I am thinking to tap the video buffer/framebuffer to customize the output..Is there any other way to control individual display output from kernel source...? hopping for your suggestions Best Regards, Jithin T Raj
Clarification about frame buffer
hello all, I just started to play with RCAR Boards..Before that , one of my confusion in kernel level is that "is there only one frame buffer for video output? Now I got a documentation about frame buffer https://www.kernel.org/doc/Documentation/fb/framebuffer.txt In my knowledge the only one frame buffer is got shared by various display output (HDMI0,HDMI1, VGA etc ), am I correct ? hopping for your comments Best Regards, Jithin T Raj
About Kernel codes
Got it, thank you Best Regards Jithin T Raj
About Kernel codes
Hi all,
I am always stuck with the declaration or ports in kernel code...
&du{
-
-- bla bla
ports {
port@1 {
endpoint {
remote-endpoint = <&adv7123_in>;
};
};
};};
In my knowledge I understand that here display unit has one port(port1) which
is for
vga encoder IC input signal..is it?and I am eager to know where these ports are
defined in tree(In case of Koelsche,Alt,Lager etc) and am I able to change the
port number..I mean,can I give above as port@0 instead of p...@1..and also how
can I add another ports here??
Hopping for your comments
Best Regards
Jithin T Raj
HDMI No signal in koelsche Board
Thank you for the information.. Now let me check with this and after that I will surely give a look at v4.8 Best Regards Jithin T Raj Engineer - Transport Business Unit TATA ELXSI Gayathri Technopark Campus, Trivandrum 695 581 India Tel +91 471 6661000 Cell +91 9961131260 www.tataelxsi.com
HDMI No signal in koelsche Board
hi simmon, I doesn't checked that yet but now I am cloning " git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-dt-for-v4.1" I think it will solve for me right? Best Regards Jithin T Raj
HDMI No signal for koelsch Board
hi,
I have a trouble in getting HDMI OUT in koelsche Board
I am using source tree v4.1.17-ltsi..also i have applied the below patch to
shmobile_defconfig
diff --git a/arch/arm/configs/shmobile_defconfig
b/arch/arm/configs/shmobile_defconfig
index 0bdeb4925be4..3aef019c0de7 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -140,7 +140,10 @@ CONFIG_VIDEO_RENESAS_VSP1=y
CONFIG_VIDEO_ADV7180=y
CONFIG_VIDEO_ML86V7667=y
CONFIG_DRM=y
+CONFIG_DRM_I2C_ADV7511=y
CONFIG_DRM_RCAR_DU=y
+CONFIG_DRM_RCAR_HDMI=y
+CONFIG_DRM_RCAR_LVDS=y
CONFIG_FB_SH_MOBILE_LCDC=y
CONFIG_FB_SH_MOBILE_MERAM=y
# CONFIG_LCD_CLASS_DEVICE is not set
and when I checked the pinmux it is like
du_pins: du {
renesas,groups = "du_rgb666", "du_sync", "du_disp", "du_clk_out_0";
renesas,function = "du";
};
do I need to change it to 24 bit (du_rgb888)? my UBoot is gb653737..
Best Regards
Jithin T Raj
HDMI support in Koelsch (RCAR M2)
Hi team, sorry for my frequent disturbance ..I am not getting HDMI out in Koelsche Board with source tree 4.7.5...but it does in 3.10.31-ltsi..if you don't mind,please provide me the patch to support HDMI in 4.7.5 Best Regards Jithin T Raj
Kernel configuration R-Car ALT(E2)
Thank you..shmobile_defconfig solvs my problem..now Ibuild kernel and deployed through nfs tftp into ALT Board..The board is accepting kernel but after some time I am getting some errors..I have attached the error log here I have the rootfs of ALT Board in /exports folder.. Best Regards Jithin T Raj errorlog Description: errorlog
Kernel Configure R-Car ATL Board(E2)
hi, I have downloaded source tree 4.7.5..Now I am trying to build kernel for ALT Board(R-Car E2).. Before that i would like to ask something..here I can't see configuration for ALT in /arch/arm/configs/..But multi_v7_defconfig and multi_v5_defconfig is there..I am a newbi in this filed..can you please tell me how I can configure this board using menuconfig or any other way is there? I am doing cross compiling..If that board is configured then only I can proceed with building no? Best Regards Jithin T Raj
Kernal version Issue
hi team, I have downloaded Source tree version 4.7.5 from kernel.org..I have build image for RCAR E2 by using that..but the board is not accepting the kernel..i want to know "Is there any special release of kernel for Renesas only? if yes can you please provide me some links or kernel from www.kernel.org are suitable for all Renesas Board? Hopping your reply Best Regards Jithin T Raj
RGB LVDS BRIDGE SUPPORT IN RCAR E2
hi,
I would like to give support to RGB LVDS BRIDGE RCAR E2
I am attaching the patch file..can you please review it and let me know the
status.is it correct or not?
Best Regards
Jithin T Raj
diff --git a/a/r8a7794-alt.dts b/b/r8a7779-marzen.dts
index 383ad79..b795da6 100644
--- a/a/r8a7794-alt.dts
+++ b/b/r8a7779-marzen.dts
@@ -1,7 +1,8 @@
/*
- * Device Tree Source for the Alt board
+ * Device Tree Source for the Marzen board
*
- * Copyright (C) 2014 Renesas Electronics Corporation
+ * Copyright (C) 2013 Renesas Solutions Corp.
+ * Copyright (C) 2013 Simon Horman
*
* This file is licensed under the terms of the GNU General Public License
* version 2. This program is licensed "as is" without any warranty of any
@@ -9,29 +10,64 @@
*/
/dts-v1/;
-#include "r8a7794.dtsi"
+#include "r8a7779.dtsi"
+#include
+#include
/ {
- model = "Alt";
- compatible = "renesas,alt", "renesas,r8a7794";
+ model = "marzen";
+ compatible = "renesas,marzen", "renesas,r8a7779";
aliases {
serial0 = &scif2;
+ serial1 = &scif4;
};
chosen {
- bootargs = "ignore_loglevel rw root=/dev/nfs ip=dhcp";
- stdout-path = "serial0:115200n8";
+ bootargs = "ignore_loglevel root=/dev/nfs ip=on";
+ stdout-path = &scif2;
};
- memory@4000 {
+ memory {
device_type = "memory";
- reg = <0 0x4000 0 0x4000>;
+ reg = <0x6000 0x4000>;
};
- lbsc {
- #address-cells = <1>;
- #size-cells = <1>;
+ fixedregulator3v3: fixedregulator@0 {
+ compatible = "regulator-fixed";
+ regulator-name = "fixed-3.3V";
+ regulator-min-microvolt = <330>;
+ regulator-max-microvolt = <330>;
+ regulator-boot-on;
+ regulator-always-on;
+ };
+
+ ethernet@1800 {
+ compatible = "smsc,lan9220", "smsc,lan9115";
+ reg = <0x1800 0x100>;
+ pinctrl-0 = <ðernet_pins>;
+ pinctrl-names = "default";
+
+ phy-mode = "mii";
+ interrupt-parent = <&irqpin0>;
+ interrupts = <1 IRQ_TYPE_EDGE_FALLING>;
+ smsc,irq-push-pull;
+ reg-io-width = <4>;
+ vddvario-supply = <&fixedregulator3v3>;
+ vdd33a-supply = <&fixedregulator3v3>;
+ };
+
+ leds {
+ compatible = "gpio-leds";
+ led2 {
+ gpios = <&gpio4 29 GPIO_ACTIVE_HIGH>;
+ };
+ led3 {
+ gpios = <&gpio4 30 GPIO_ACTIVE_HIGH>;
+ };
+ led4 {
+ gpios = <&gpio4 31 GPIO_ACTIVE_HIGH>;
+ };
};
vga-encoder {
@@ -43,13 +79,13 @@
port@0 {
reg = <0>;
-adv7123_in: endpoint {
- remote-endpoint = <&du_out_rgb1>;
+vga_enc_in: endpoint {
+ remote-endpoint = <&du_out_rgb0>;
};
};
port@1 {
reg = <1>;
-adv7123_out: endpoint {
+vga_enc_out: endpoint {
remote-endpoint = <&vga_in>;
};
};
@@ -61,21 +97,36 @@
port {
vga_in: endpoint {
-remote-endpoint = <&adv7123_out>;
+remote-endpoint = <&vga_enc_out>;
};
};
};
- x2_clk: x2-clock {
- compatible = "fixed-clock";
- #clock-cells = <0>;
- clock-frequency = <7425>;
+ lvds-encoder {
+ compatible = "thine,thc63lvdm83d";
+
+ ports {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ port@0 {
+reg = <0>;
+lvds_enc_in: endpoint {
+ remote-endpoint = <&du_out_rgb1>;
+};
+ };
+ port@1 {
+reg = <1>;
+lvds_connector: endpoint {
+};
+ };
+ };
};
- x13_clk: x13-clock {
+ x3_clk: x3-clock {
compatible = "fixed-clock";
#clock-cells = <0>;
- clock-frequency = <14850>;
+ clock-frequency = <6500>;
};
};
@@ -84,22 +135,33 @@
pinctrl-names = "default";
status = "okay";
- clocks = <&mstp7_clks R8A7794_CLK_DU0>,
- <&mstp7_clks R8A7794_CLK_DU0>,
- <&x13_clk>, <&x2_clk>;
- clock-names = "du.0", "du.1", "dclkin.0", "dclkin.1";
+ clocks = <&mstp1_clks R8A7779_CLK_DU>, <&x3_clk>;
+ clock-names = "du", "dclkin.0";
ports {
+ port@0 {
+ endpoint {
+remote-endpoint = <&vga_enc_in>;
+ };
+ };
port@1 {
endpoint {
-remote-endpoint = <&adv7123_in>;
+remote-endpoint = <&lvds_enc_in>;
};
};
};
};
+&irqpin0 {
+ status = "okay";
+};
+
&extal_clk {
- clock-frequency = <2000>;
+ clock-frequency = <3125>;
+};
+
+&tmu0 {
+ status = "okay";
};
&pfc {
@@ -107,152 +169,83 @@
pinctrl-names = "default";
du_pins: du {
- groups = "du1_rgb666", "du1_sync", "du1_disp", &q
RGB-LVDS BRIDGE SUPPORT RCAR
Hi, This is my diff file, diff --git a/a/r8a7794-alt.dts b/b/r8a7779-marzen.dts index 383ad79..b795da6 100644 --- a/a/r8a7794-alt.dts +++ b/b/r8a7779-marzen.dts @@ -1,7 +1,8 @@ /* - * Device Tree Source for the Alt board + * Device Tree Source for the Marzen board * - * Copyright (C) 2014 Renesas Electronics Corporation + * Copyright (C) 2013 Renesas Solutions Corp. + * Copyright (C) 2013 Simon Horman * * This file is licensed under the terms of the GNU General Public License * version 2. This program is licensed "as is" without any warranty of any @@ -9,29 +10,64 @@ */ /dts-v1/; -#include "r8a7794.dtsi" +#include "r8a7779.dtsi" +#include +#include : i just done this command "git diff a/r8a7794-alt.dts b/r8a7779-marzen.dts " i have kept "r8a7794-alt.dts" in "a" and "r8a7779-marzen.dts" in "b" sorry if it is not good Best Regards Jithin T Raj
RGB-LVDS BRIDGE SUPPORT RCAR E2
Thank you so much for the information. Now i compared "arch/arm/boot/dts/r8a7779-marzen.dts" against "arch/arm/boot/dts/r8a7794-alt.dts" and modified r8a7794-alt.dts a little.. also added "thc63lvdm87"in "drivers/gpu/drm/rcar-du/rcar_du_kms.c"..here i am attaching the modified r8a7794-alt.dts file..I am a newby in this field so that I am asking very basics..hope you don't feel bore.. I also build image file and .dtb file successfully but don't deployed it.. if you don't mind can you please give me a feedback of my work..My source tree is v4.7.5 PFA Best Regards Jithin T Raj r8a7794-alt.dts Description: r8a7794-alt.dts
LVDS IF connector (R-Car E2) RTPORC7794SEB00011S ALT Board
Hi, I have an (R-Car E2) RTPORC7794SEB00011S ALT Board with me ..On that I can see a "LVDS IF" Output at the back side..is it same as LVDS?then how can i make it work on that Board Best Regards Jithin T Raj Engineer - Transport Business Unit
LVDS Support in R-Car E2(ALT) Board
Hi Geert and others, I have successfully applied the patch and build R-car M2 Kernel for Koelsch Board..now it support LVDS..Thank you all especially Geert and Laurent..now i tried the same source tree(v4.7.5) to build for R-Car E2(ALT)Board to make LVDS up..but i am getting the following error during making .dtb file ubuntu@teltvm2468l:~/jithin_new/linux-4.7.5$ make -j4 r8a7794-alt.dtb DTC arch/arm/boot/dts/r8a7794-alt.dtb Error: arch/arm/boot/dts/r8a77xx-aa104xd12-panel.dtsi:39.1-16 Label or path lvds_connector not found FATAL ERROR: Syntax error parsing input tree make[1]: *** [arch/arm/boot/dts/r8a7794-alt.dtb] Error 1 make: *** [r8a7794-alt.dtb] Error 2 ubuntu@teltvm2468l:~/jithin_new/linux-4.7.5$ I have included the "#include "r8a77xx-aa104xd12-panel.dtsi" in r8a7794-alt.dts my source tree is v4.7.5 stable edition Best Regards Jithin T Raj
Source tree v4.1.17-ltsi.
hello Geert, if you dont mind can you provide me some links that i get v4.1.17-ltsi.because here i have no access to github Best Regards Jithin T Raj
LVDS SUPPORT RCAR
Thank you Geert. I am eager to solve it..i will use the specified version Best Regards Jithin T Raj
LVDS SUPPORT RCAR
hi, first of all thanks alot for the support you are giving..when i tried to make .dtb file i am getting following error..I am using 3.10.31-ltsi ubuntu@teltvm2468l:~/Jithin/Koelsch/kernel$ make -j4 r8a7791-koelsch.dtb CC scripts/mod/devicetable-offsets.s GEN scripts/mod/devicetable-offsets.h HOSTCC scripts/mod/file2alias.o HOSTLD scripts/mod/modpost DTC arch/arm/boot/dts/r8a7791-koelsch.dtb Error: arch/arm/boot/dts/r8a77xx-aa104xd12-panel.dtsi:41.4-5 label or path, 'lvds_connector', not found FATAL ERROR: Syntax error parsing input tree make[1]: *** [arch/arm/boot/dts/r8a7791-koelsch.dtb] Error 1 make: *** [r8a7791-koelsch.dtb] Error 2 here i am attaching my r8a7791.dts file Best Regards Jithin T Raj r8a7791-koelsch.dts Description: r8a7791-koelsch.dts
LVDS SUPPORT RCAR
f1";
};
sound_pins: sound {
renesas,groups = "ssi0129_ctrl", "ssi0_data", "ssi1_data";
renesas,function = "ssi";
};
sound_clk_pins: sound_clk {
renesas,groups = "audio_clk_a";
renesas,function = "audio_clk";
};
vin0_pins: vin0 {
renesas,groups = "vin0_data24", "vin0_sync", "vin0_field",
"vin0_clkenb", "vin0_clk";
renesas,function = "vin0";
};
vin1_pins: vin1 {
renesas,groups = "vin1_data8", "vin1_clk";
renesas,function = "vin1";
};
usb0_pins: usb0 {
renesas,groups = "usb0";
renesas,function = "usb0";
};
usb1_pins: usb1 {
renesas,groups = "usb1";
renesas,function = "usb1";
};
};
ðer {
pinctrl-0 = <ðer_pins &phy1_pins>;
pinctrl-names = "default";
phy-handle = <&phy1>;
renesas,ether-link-active-low;
status = "ok";
phy1: ethernet-phy@1 {
reg = <1>;
interrupt-parent = <&irqc0>;
interrupts = <0 IRQ_TYPE_LEVEL_LOW>;
micrel,led-mode = <1>;
};
};
&sata0 {
status = "okay";
};
&scif0 {
pinctrl-0 = <&scif0_pins>;
pinctrl-names = "default";
status = "okay";
};
&scif1 {
pinctrl-0 = <&scif1_pins>;
pinctrl-names = "default";
status = "okay";
};
&hscif1 {
pinctrl-0 = <&hscif1_pins>;
pinctrl-names = "default";
};
&sdhi0 {
pinctrl-0 = <&sdhi0_pins>;
pinctrl-names = "default";
vmmc-supply = <&vcc_sdhi0>;
vqmmc-supply = <&vccq_sdhi0>;
cd-gpios = <&gpio6 6 GPIO_ACTIVE_LOW>;
wp-gpios = <&gpio6 7 GPIO_ACTIVE_HIGH>;
status = "okay";
};
&sdhi1 {
pinctrl-0 = <&sdhi1_pins>;
pinctrl-names = "default";
vmmc-supply = <&vcc_sdhi1>;
vqmmc-supply = <&vccq_sdhi1>;
cd-gpios = <&gpio6 14 GPIO_ACTIVE_LOW>;
wp-gpios = <&gpio6 15 GPIO_ACTIVE_HIGH>;
status = "okay";
};
&sdhi2 {
pinctrl-0 = <&sdhi2_pins>;
pinctrl-names = "default";
vmmc-supply = <&vcc_sdhi2>;
vqmmc-supply = <&vccq_sdhi2>;
cd-gpios = <&gpio6 22 GPIO_ACTIVE_LOW>;
status = "okay";
};
&qspi {
pinctrl-0 = <&qspi_pins>;
pinctrl-names = "default";
status = "okay";
flash: flash@0 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "spansion,s25fl512s";
reg = <0>;
spi-max-frequency = <3000>;
spi-tx-bus-width = <4>;
spi-rx-bus-width = <4>;
m25p,fast-read;
spi-cpol;
spi-cpha;
partition@0 {
label = "loader";
reg = <0x 0x0008>;
read-only;
};
partition@4 {
label = "user";
reg = <0x0008 0x0058>;
read-only;
};
partition@44 {
label = "flash";
reg = <0x0060 0x03a0>;
};
};
};
&msiof0 {
pinctrl-0 = <&msiof0_pins>;
pinctrl-names = "default";
status = "okay";
};
&msiof1 {
pinctrl-0 = <&msiof1_pins>;
pinctrl-names = "default";
status = "okay";
};
&i2c2 {
pinctrl-0 = <&i2c2_pins>;
pinctrl-names = "default";
status = "okay";
clock-frequency = <40>;
eeprom@50 {
compatible = "renesas,24c02";
reg = <0x50>;
pagesize = <16>;
};
ak4643: sound-codec@12 {
#sound-dai-cells = <0>;
compatible = "asahi-kasei,ak4643";
reg = <0x12>;
};
};
&i2c6 {
status = "okay";
clock-frequency = <10>;
vdd_dvfs: regulator@68 {
compatible = "diasemi,da9210";
reg = <0x68>;
regulator-min-microvolt = <100>;
regulator-max-microvolt = <100>;
regulator-boot-on;
regulator-always-on;
};
};
&pci0 {
status = "okay";
pinctrl-0 = <&usb0_pins>;
pinctrl-names = "default";
};
&pci1 {
status = "okay";
pinctrl-0 = <&usb1_pins>;
pinctrl-names = "default";
};
&pcie_bus_clk {
status = "okay";
};
&pciec {
status = "okay";
};
&cpu0 {
cpu0-supply = <&vdd_dvfs>;
};
&rcar_sound {
pinctrl-0 = <&sound_pins &sound_clk_pins>;
pinctrl-names = "default";
#sound-dai-cells = <0>;
status = "okay";
rcar_sound,dai {
dai0 {
playback = <&ssi0 &src0 &dvc0>;
capture = <&ssi1 &src1 &dvc1>;
};
};
};
&ssi1 {
shared-pin;
};
#include "r8a77xx-aa104xd12-panel.dtsi"
Best Regards
Jithin T Raj
LVDS SUPPORT RCAR M2
hi Geert, Thank you for the information Actually i am a newby in this field..i have an RCAR M2 koelsch board with me and i am trying to up the lvds support in that.. I have "r8a77xx-aa104xd12-panel.dtsi" in arch/arm/boot/dts/... when i checked the arch/arm/boot/dts/r8a7791-koelsch.dts file,it does not contain lvds connector definition..can anyone please help me to define the same in arch/arm/boot/dts/r8a7791-koelsch.dts Regards, Jithin T Raj
LVDS SUPPORT RCAR M2(R8A7791)
hi, first of all thank u for the patch given..I tryed with that..I am getting uImage after build..but when i tried to make .dtb file i am getting following error ubuntu@teltvm2468l:~/Jithin/Koelsch/kernel$ make -j4 r8a7791-koelsch.dtb CC scripts/mod/devicetable-offsets.s GEN scripts/mod/devicetable-offsets.h HOSTCC scripts/mod/file2alias.o HOSTLD scripts/mod/modpost DTC arch/arm/boot/dts/r8a7791-koelsch.dtb Error: arch/arm/boot/dts/r8a77xx-aa104xd12-panel.dtsi:41.4-5 label or path, 'lvds_connector', not found FATAL ERROR: Syntax error parsing input tree make[1]: *** [arch/arm/boot/dts/r8a7791-koelsch.dtb] Error 1 make: *** [r8a7791-koelsch.dtb] Error 2 Best Regards Jithin T Raj
