* Using i.MX6 quad's IPU#1/DI#1 to drive parallel port #1 failed
@ 2016-02-17 11:10 Juergen Borleis
2016-02-17 13:09 ` Lothar Waßmann
0 siblings, 1 reply; 5+ messages in thread
From: Juergen Borleis @ 2016-02-17 11:10 UTC (permalink / raw)
To: linux-arm-kernel
Hi,
someone here who has a working display (or similar) connected to i.MX6 quad's
parallel port #1 and driven by IPU#1/DI#1? It seems there is currently no user
in the mainline supported boards.
In my application the RGB data signals seem present, HSYNC and VSYNC as well
(with the expected timing), but the display clock and the DE signals are
missing. We already double checked the pin muxing and the physical connection
(for example muxing the clock pad to be a GPIO works as expected).
Are there any known restrictions?
Thanks in advance.
Juergen
^ permalink raw reply [flat|nested] 5+ messages in thread
* Using i.MX6 quad's IPU#1/DI#1 to drive parallel port #1 failed
2016-02-17 11:10 Using i.MX6 quad's IPU#1/DI#1 to drive parallel port #1 failed Juergen Borleis
@ 2016-02-17 13:09 ` Lothar Waßmann
2016-02-17 14:23 ` Juergen Borleis
0 siblings, 1 reply; 5+ messages in thread
From: Lothar Waßmann @ 2016-02-17 13:09 UTC (permalink / raw)
To: linux-arm-kernel
Hi,
On Wed, 17 Feb 2016 12:10:14 +0100 Juergen Borleis wrote:
> Hi,
>
> someone here who has a working display (or similar) connected to i.MX6 quad's
> parallel port #1 and driven by IPU#1/DI#1? It seems there is currently no user
> in the mainline supported boards.
>
I've got a working configuration with two DVI adapters connected to the
DI0 and DI1 ports on an i.MX6Q board.
The relevant portion of the .dts file looks like this:
ipu1_disp0: display at di0 {
compatible = "fsl,imx-parallel-display";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_disp0_1>;
interface-pix-fmt = "rgb24";
status = "okay";
display-timings {
native-mode = <&vga0>;
full-hd {
clock-frequency = <138500000>;
hactive = <1920>;
vactive = <1080>;
hback-porch = <88>;
hsync-len = <128>;
hfront-porch = <40>;
vback-porch = <33>;
vsync-len = <2>;
vfront-porch = <10>;
hsync-active = <0>;
vsync-active = <0>;
de-active = <1>;
pixelclk-active = <1>;
};
vga0: VGA {
clock-frequency = <25200000>;
hactive = <640>;
vactive = <480>;
hback-porch = <48>;
hsync-len = <96>;
hfront-porch = <16>;
vback-porch = <31>;
vsync-len = <2>;
vfront-porch = <12>;
hsync-active = <0>;
vsync-active = <0>;
de-active = <1>;
pixelclk-active = <0>;
};
};
port {
display0_in: endpoint {
remote-endpoint = <&ipu1_di0_disp0>;
};
};
};
ipu1_disp1: display at di1 {
compatible = "fsl,imx-parallel-display";
interface-pix-fmt = "rgb24";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_disp1>;
status = "okay";
display-timings {
native-mode = <&vga1>;
full-hd {
clock-frequency = <138500000>;
hactive = <1920>;
vactive = <1080>;
hback-porch = <88>;
hsync-len = <128>;
hfront-porch = <40>;
vback-porch = <33>;
vsync-len = <2>;
vfront-porch = <10>;
hsync-active = <0>;
vsync-active = <0>;
de-active = <1>;
pixelclk-active = <1>;
};
vga1: VGA {
clock-frequency = <25200000>;
hactive = <640>;
vactive = <480>;
hback-porch = <48>;
hsync-len = <96>;
hfront-porch = <16>;
vback-porch = <31>;
vsync-len = <2>;
vfront-porch = <12>;
hsync-active = <0>;
vsync-active = <0>;
de-active = <1>;
pixelclk-active = <0>;
};
};
port {
display1_in: endpoint {
remote-endpoint = <&ipu1_di0_disp1>;
};
};
};
lcd0_panel: panel0 {
compatible = "auo,b133htn01", "simple-panel";
power-supply = <®_lcd1_pwr>;
ddc-i2c-bus = <&i2c2>;
};
lcd1_panel: lcd-panel {
compatible = "auo,b133htn01", "simple-panel";
power-supply = <®_lcd1_pwr>;
ddc-i2c-bus = <&i2c1>;
};
Lothar Wa?mann
--
___________________________________________________________
Ka-Ro electronics GmbH | Pascalstra?e 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
Gesch?ftsf?hrer: Matthias Kaussen
Handelsregistereintrag: Amtsgericht Aachen, HRB 4996
www.karo-electronics.de | info at karo-electronics.de
___________________________________________________________
^ permalink raw reply [flat|nested] 5+ messages in thread* Using i.MX6 quad's IPU#1/DI#1 to drive parallel port #1 failed
2016-02-17 13:09 ` Lothar Waßmann
@ 2016-02-17 14:23 ` Juergen Borleis
2016-02-17 14:58 ` Lothar Waßmann
0 siblings, 1 reply; 5+ messages in thread
From: Juergen Borleis @ 2016-02-17 14:23 UTC (permalink / raw)
To: linux-arm-kernel
Hi Lothar,
thank you for your answer. Can you also send me your "pinctrl_disp1"
definition, please?
Regards,
Juergen
^ permalink raw reply [flat|nested] 5+ messages in thread
* Using i.MX6 quad's IPU#1/DI#1 to drive parallel port #1 failed
2016-02-17 14:23 ` Juergen Borleis
@ 2016-02-17 14:58 ` Lothar Waßmann
2016-02-18 10:07 ` Juergen Borleis
0 siblings, 1 reply; 5+ messages in thread
From: Lothar Waßmann @ 2016-02-17 14:58 UTC (permalink / raw)
To: linux-arm-kernel
Hi,
On Wed, 17 Feb 2016 15:23:55 +0100 Juergen Borleis wrote:
> Hi Lothar,
>
> thank you for your answer. Can you also send me your "pinctrl_disp1"
> definition, please?
>
pinctrl_disp1: disp1grp {
fsl,pins = <
MX6QDL_PAD_EIM_A16__IPU1_DI1_DISP_CLK 0x10
MX6QDL_PAD_EIM_DA10__IPU1_DI1_PIN15 0x10
MX6QDL_PAD_EIM_DA11__IPU1_DI1_PIN02 0x10
MX6QDL_PAD_EIM_DA12__IPU1_DI1_PIN03 0x10
MX6QDL_PAD_EIM_DA9__IPU1_DISP1_DATA00 0x10
MX6QDL_PAD_EIM_DA8__IPU1_DISP1_DATA01 0x10
MX6QDL_PAD_EIM_DA7__IPU1_DISP1_DATA02 0x10
MX6QDL_PAD_EIM_DA6__IPU1_DISP1_DATA03 0x10
MX6QDL_PAD_EIM_DA5__IPU1_DISP1_DATA04 0x10
MX6QDL_PAD_EIM_DA4__IPU1_DISP1_DATA05 0x10
MX6QDL_PAD_EIM_DA3__IPU1_DISP1_DATA06 0x10
MX6QDL_PAD_EIM_DA2__IPU1_DISP1_DATA07 0x10
MX6QDL_PAD_EIM_DA1__IPU1_DISP1_DATA08 0x10
MX6QDL_PAD_EIM_DA0__IPU1_DISP1_DATA09 0x10
MX6QDL_PAD_EIM_EB1__IPU1_DISP1_DATA10 0x10
MX6QDL_PAD_EIM_EB0__IPU1_DISP1_DATA11 0x10
MX6QDL_PAD_EIM_A17__IPU1_DISP1_DATA12 0x10
MX6QDL_PAD_EIM_A18__IPU1_DISP1_DATA13 0x10
MX6QDL_PAD_EIM_A19__IPU1_DISP1_DATA14 0x10
MX6QDL_PAD_EIM_A20__IPU1_DISP1_DATA15 0x10
MX6QDL_PAD_EIM_A21__IPU1_DISP1_DATA16 0x10
MX6QDL_PAD_EIM_A22__IPU1_DISP1_DATA17 0x10
MX6QDL_PAD_EIM_A23__IPU1_DISP1_DATA18 0x10
MX6QDL_PAD_EIM_A24__IPU1_DISP1_DATA19 0x10
MX6QDL_PAD_EIM_D31__IPU1_DISP1_DATA20 0x10
MX6QDL_PAD_EIM_D30__IPU1_DISP1_DATA21 0x10
MX6QDL_PAD_EIM_D26__IPU1_DISP1_DATA22 0x10
MX6QDL_PAD_EIM_D27__IPU1_DISP1_DATA23 0x10
>;
};
Lothar Wa?mann
--
___________________________________________________________
Ka-Ro electronics GmbH | Pascalstra?e 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
Gesch?ftsf?hrer: Matthias Kaussen
Handelsregistereintrag: Amtsgericht Aachen, HRB 4996
www.karo-electronics.de | info at karo-electronics.de
___________________________________________________________
^ permalink raw reply [flat|nested] 5+ messages in thread* Using i.MX6 quad's IPU#1/DI#1 to drive parallel port #1 failed
2016-02-17 14:58 ` Lothar Waßmann
@ 2016-02-18 10:07 ` Juergen Borleis
0 siblings, 0 replies; 5+ messages in thread
From: Juergen Borleis @ 2016-02-18 10:07 UTC (permalink / raw)
To: linux-arm-kernel
Hi Lothar,
On Wednesday 17 February 2016 15:58:14 Lothar Wa?mann wrote:
> > thank you for your answer. Can you also send me your "pinctrl_disp1"
> > definition, please?
>
> pinctrl_disp1: disp1grp {
> fsl,pins = <
> MX6QDL_PAD_EIM_A16__IPU1_DI1_DISP_CLK 0x10
> MX6QDL_PAD_EIM_DA10__IPU1_DI1_PIN15 0x10
The "PIN15" was the key. With your definition it now works here as well.
Thank you for your help.
Regards,
Juergen
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2016-02-18 10:07 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-02-17 11:10 Using i.MX6 quad's IPU#1/DI#1 to drive parallel port #1 failed Juergen Borleis
2016-02-17 13:09 ` Lothar Waßmann
2016-02-17 14:23 ` Juergen Borleis
2016-02-17 14:58 ` Lothar Waßmann
2016-02-18 10:07 ` Juergen Borleis
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox