From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Subject: Re: OMAPDSS: omap5 SYNC_LOST error with DPI/LCD Date: Mon, 12 May 2014 14:58:20 +0300 Message-ID: <5370B75C.3060602@ti.com> References: <536CB9C7.8070404@ti.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2046849961==" Return-path: Received: from devils.ext.ti.com (devils.ext.ti.com [198.47.26.153]) by gabe.freedesktop.org (Postfix) with ESMTP id AB79B6E4DE for ; Mon, 12 May 2014 04:58:30 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Vikas Patil Cc: "dri-devel@lists.freedesktop.org" List-Id: dri-devel@lists.freedesktop.org --===============2046849961== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="P2x7uV9w363ciHnQ907eV0EwFgfd6Lfjb" --P2x7uV9w363ciHnQ907eV0EwFgfd6Lfjb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 12/05/14 14:33, Vikas Patil wrote: > Hi, >=20 > Re-posting as previous posting was rejected due to length. >=20 > Forgot to mention, DPI pins are connected to TDF19988 chip for HDMI > conversion. > I have build the driver for it from > https://gitorious.org/thierryreding/linux/source/e7792ce2da5ded80861db7= 87ace9b57ecf7bc96c:drivers/gpu/drm/i2c/tda998x_drv.c. > Is this the correct driver for it? That driver cannot be used with omapdrm, which uses omapdss. There's no TDF19988 driver for omapdss (at least in the mainline), so you need to write one. > Also I am trying to use the generic-dpi-panel driver for this with > OMAP5. It seems I also need to add support for TDF19988 somewhere in > omapdrm or lcd/panel driver by calling drm_i2c_encoder_init to > initialize it. Can I use somecode from ticldc driver or driver itself? > Could you please give some inputs, how should I proceed further to > adding support for TDF19988 for which the input is coming from DPI > interface? You need to write a driver for it. Something similar to drivers/video/fbdev/omap2/displays-new/encoder-tfp410.c, except tfp410 is quite simple one. But I think you said you're based on some old customized kernel, so I don't know which kind of omapdss driver you have there, so the mainline tfp410 cannot probably be used as an example. Most likely the omapdss drivers for your kernel are located in drivers/video/omap2/displays/ directory. Tomi --P2x7uV9w363ciHnQ907eV0EwFgfd6Lfjb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJTcLdcAAoJEPo9qoy8lh71BZQP/150XzbUq3CVdDxiUYizOkYi Xt3KO3rEDodl2NE85OvNbfAhS47nrqP/+YvjcS3XsQzAAAQ92lWx5hSWMVvpOwz3 IKUL4La2/vWBrBj6DSrb3nwfQl90WHpz+8I6pDus739rxYUSqahP69ck1p+LVlsL HZvmKuRdkgfrai+28Ue89k26Qdo7ND0uAh1ifElyzGT1UqfIXwUr2LuCoWXbKYU6 d/pDfclIHxO5wdo+7HjSDxA3a2GRyo4u+sNgACDjHAVT9rxUrogRtE+t1utFSs6I ePn2NkNNhjSJE31x21tVkZl+GKecB3kleRnYKZ93YJ78EvSxCmY59dLVO2MoL2P/ rQaWrVQg4K8QoqtpqJtyPYhdbNwJGbN8rGMK1vhjyb6ZJlpw2OFbob9h/IOvMAfy 9jG2v1GujvJCqehpjzfb5OC1K412lfmrzteQ2Wf229hTJJXUDsXCVlF9rryz1TCX wwDtkxEDPfa14nyiqEvyqa7ScyXyAuIgzSCUwFmOXx/RKvqfnpGUmN4OICRUFqXV OG4dpgxT7wx25AdE6jHE/G2ttflKVrMUV2KAJTqbRBbhsAG3Jlr35OJlH3r/dkha MsAJkFDv0PY8qrpOS1LEyOSEZdqli01K4MHp5zmS+jy+j+w8EPvGJswH5Rkp64BQ 8U9R7i28ivT6c/9cA6q5 =txCw -----END PGP SIGNATURE----- --P2x7uV9w363ciHnQ907eV0EwFgfd6Lfjb-- --===============2046849961== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============2046849961==--