dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
* Interfacing mipi-lvds bridge with rk3399
@ 2020-01-27 16:18 ` Mika Penttilä
  2020-01-28 10:39   ` Andrzej Hajda
  2020-02-06 10:09   ` rk3399 and two mipi dsi Mika Penttilä
  0 siblings, 2 replies; 3+ messages in thread
From: Mika Penttilä @ 2020-01-27 16:18 UTC (permalink / raw)
  To: hjc; +Cc: linux-rockchip, dri-devel

Hi,

We are developing a custom board, in which we are using the rk3399 soc. 
We have LVDS displays, and use TI SN65dsi84 bridge as a mipi-lvds bridge.
The bridge demands the DSI data lanes be in LP-11 state (stop state). We 
developed support for the bridge as a DRM bridge module. It gets called 
in the places we want, but the problem is the data lanes, no in LP-11. 
Instead, they seem to be lowish, until data starts (they seem to visit 
LP-11 a a short time, like 5ms before data stream. This is not enough 
and not under our control. We would like to demand the mipi dhpy into 
LP-11 (or make sure it stays there from powerup/reset). And after 
configuring bridge, let the data leave LP-11.

Documentation states that the data should be LP-11 upon phy reset. How 
come it is not? And, while booting, we se a couple of set mode calls, 
during which the phy is configured. During the phy init, there's code to 
wait for the phy enter stop state. First time the phy status says it has 
entered stop state. But second time the wait timeouts (after 10ms or 
so). With oscilloscope anything like LP-11 isn't observed.

Has someone successfully integrated SN65dsi8x with rk3399 ? Does someone 
have information on howto command the phy wrt stop states and how it 
should behave?

Thanks in advance,
Mika Penttilä
Nextfour

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Interfacing mipi-lvds bridge with rk3399
  2020-01-27 16:18 ` Interfacing mipi-lvds bridge with rk3399 Mika Penttilä
@ 2020-01-28 10:39   ` Andrzej Hajda
  2020-02-06 10:09   ` rk3399 and two mipi dsi Mika Penttilä
  1 sibling, 0 replies; 3+ messages in thread
From: Andrzej Hajda @ 2020-01-28 10:39 UTC (permalink / raw)
  To: Mika Penttilä, hjc; +Cc: linux-rockchip, dri-devel

On 27.01.2020 17:18, Mika Penttilä wrote:
> Hi,
>
> We are developing a custom board, in which we are using the rk3399 soc. 
> We have LVDS displays, and use TI SN65dsi84 bridge as a mipi-lvds bridge.
> The bridge demands the DSI data lanes be in LP-11 state (stop state). We 
> developed support for the bridge as a DRM bridge module. It gets called 
> in the places we want, but the problem is the data lanes, no in LP-11. 
> Instead, they seem to be lowish, until data starts (they seem to visit 
> LP-11 a a short time, like 5ms before data stream. This is not enough 
> and not under our control. We would like to demand the mipi dhpy into 
> LP-11 (or make sure it stays there from powerup/reset). And after 
> configuring bridge, let the data leave LP-11.
>
> Documentation states that the data should be LP-11 upon phy reset. How 
> come it is not? And, while booting, we se a couple of set mode calls, 
> during which the phy is configured. During the phy init, there's code to 
> wait for the phy enter stop state. First time the phy status says it has 
> entered stop state. But second time the wait timeouts (after 10ms or 
> so). With oscilloscope anything like LP-11 isn't observed.
>
> Has someone successfully integrated SN65dsi8x with rk3399 ? Does someone 
> have information on howto command the phy wrt stop states and how it 
> should behave?


I am not familiar neither with rk3399, neither sn65dsi84 so I cannot
tell about these chips,

but generally power-on on mipi source (rk3399 or external mipi phy)
should drive LP-11 state.

So I would look into rk3389-mipi driver, mipi-phy code (especially if
there is external phy), maybe regulators powering display pipeline,
maybe some gpios, voltage level shifters, power domains, SoCs external
interfaces isolation configuration ???

Additionally you should study all wires on board's schematics regarding
display pipeline.

Without the code or documentation is hard to say more what is going on here.


Regards

Andrzej


>
> Thanks in advance,
> Mika Penttilä
> Nextfour
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://protect2.fireeye.com/url?k=c52bdf84-98f8863a-c52a54cb-0cc47a31ba82-d8a0e87cde99a622&u=https://lists.freedesktop.org/mailman/listinfo/dri-devel


_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

* rk3399 and two mipi dsi
  2020-01-27 16:18 ` Interfacing mipi-lvds bridge with rk3399 Mika Penttilä
  2020-01-28 10:39   ` Andrzej Hajda
@ 2020-02-06 10:09   ` Mika Penttilä
  1 sibling, 0 replies; 3+ messages in thread
From: Mika Penttilä @ 2020-02-06 10:09 UTC (permalink / raw)
  To: hjc; +Cc: linux-rockchip, dri-devel

[-- Attachment #1: Type: text/plain, Size: 451 bytes --]

Hi,

We are developing a custom board based on the rk3399 soc. We need two
displays, and would like to use the two mipi DSI interfaces
ff960000.mipi and ff968000.mipi,
simultaneously, independently, both with an own touch controller, 4
lanes per display.

Question, is this a possible scenario, concerning rk3399 and mipi dphys.
So two fully independent, no dual modes, master-slaves etc.


Thanks in advance,
Mika Penttilä
Nextfour


[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 3157 bytes --]

[-- Attachment #3: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-02-07 17:02 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CGME20200128083655eucas1p2665cc13d4794ce4796c91f7146dd4dc4@eucas1p2.samsung.com>
2020-01-27 16:18 ` Interfacing mipi-lvds bridge with rk3399 Mika Penttilä
2020-01-28 10:39   ` Andrzej Hajda
2020-02-06 10:09   ` rk3399 and two mipi dsi Mika Penttilä

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).