From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Date: Mon, 18 Nov 2013 13:29:54 +0000 Subject: Re: [PATCH 0/3] omapdss: venc: Add support for bypass and acbias. Message-Id: <528A1652.4000806@ti.com> MIME-Version: 1 Content-Type: multipart/mixed; boundary="3WILi8Rrmjxp5j7DTGaKoVD7JD76b7NcU" List-Id: References: <1381784555-18344-1-git-send-email-marek@goldelico.com> <5280DBA6.50303@ti.com> <5280E617.3000004@ti.com> In-Reply-To: To: linux-arm-kernel@lists.infradead.org --3WILi8Rrmjxp5j7DTGaKoVD7JD76b7NcU Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2013-11-11 16:30, Dr. H. Nikolaus Schaller wrote: > Maybe it looks as if it is an unsolvable problem. The OPA works only if= acbias > and bypass are enabled, but is not allowed to tell that it is there. That's why the board file or dts file is there, to have "glue" data to make different pieces work together. The perfect (?) solution would be a CDF like data. The idea would be that in the board file, you would describe configuration options for VENC and for OPA. In this particular case, you'd tell VENC that it needs to enable acbias and bypass when OPA is to be connected to VENC. Then there could be more entries for VENC, saying disable acbias and bypass when BAR is to be connected to VENC. However, we don't have such support (yet). For now, I hope it's enough if we handle VENC in a "single configuration" manner, i.e. you'll tell VENC to enable acbias and bypass when VENC is enabled. This means you can't have board setups where you'd change the VENC->OPA connection to some other analog tv output at runtime. I hope that's the case (i.e. OPA is always in use on that board)= =2E If so, then I think you can just pass the acbias and bypass configuration values via omapdss platform data. And VENC driver will use them to configure those. OPA doesn't know anything about this at all. Tomi --3WILi8Rrmjxp5j7DTGaKoVD7JD76b7NcU 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.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSihZSAAoJEPo9qoy8lh71ZhsP/1DLeXny3KsX6fC1jDPS8IBd Ux7TLBA0mbxpKHrofM+nI72ohQ1hq+HyjhEhNltDFGgmjtOIqGlFisyaW/M0XDxu tcHYnB9VHZrMSPmmM6HSt1INhAjAaamPSyqjY23aoJ2SZcyKqHLfiMHkPxBh/EOU 587Cjpp9URq1vqD8dRRhoHgVkTjUuSzG8dxzoSQLzGQcvLMp2oN+ZieNbNgWzJ6n qQvEsNtfyBT78zRdpXaQvKQHK3Q/3uoy1tET4kPzEzwh1Arj/i+uJwcA27CTm2m3 JdHrhbvaGfsrXzD7nBrGuJIWqnAewyubo4e/i1IRxIFaTykqE4f8Eqe6uisuuAbI QH+AkK+kOIWkzx5eme8s1iTEZVMI6aoP/DkU5yXf3AAhDBsXw6+veowqGWtzcjnd UX9sERkrOhVFGI1NynYAXXHsJe9ZepssjebpMU9cYLOzXwTQDKFc4eS3lxaSKSGs WExByrIf4u8GcsdmSiSYo8cWgQ6+Wg1bNq3n1+wVKNA3qhL5s2GYEeJkYq6vLjx3 RXLVs+tYOaCYz9ZexM2pHyo9YPYfUx42EnBRLkaSXFofIbg1prbWpOpk43+JQbMk zrBsIzCclbw4FASxyRQKvmyH7ttO8k9laM4nGNtte6K+J9YbdRfY2w2b5HBgcqX6 YCBny9yOgFCRDp6E8ccR =4lFa -----END PGP SIGNATURE----- --3WILi8Rrmjxp5j7DTGaKoVD7JD76b7NcU--