From: tomi.valkeinen@ti.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP5: DSS hwmod data
Date: Tue, 18 Mar 2014 07:29:34 +0200 [thread overview]
Message-ID: <5327D9BE.80503@ti.com> (raw)
In-Reply-To: <53270510.1030301@compulab.co.il>
On 17/03/14 16:22, Dmitry Lifshitz wrote:
> Hi Tomi,
>
> Unfortunately, I have a lack of experience with DT DSS stuff.
>
> How should I define the endpoints and the connector in my case?
> Please, could you provide some reference.
See Documentation/devicetree/bindings/media/video-interfaces.txt for a
description of the ports and endpoints.
If your board is similar to uevm except you don't have the tpd12s015,
then you just need to remove the tpd12s015 from the .dts file, and
connect the OMAP's HDMI output directly to the connector.
> Regarding omapfb, is it sufficient to turn it on in the Kernel config?
Yes.
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140318/1e2da321/attachment.sig>
next prev parent reply other threads:[~2014-03-18 5:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 10:26 [PATCH] ARM: OMAP5: DSS hwmod data Tomi Valkeinen
2014-03-12 10:26 ` [PATCH] ARM: OMAP5: Add omap5 DSS related " Tomi Valkeinen
2014-03-12 10:33 ` [PATCH] ARM: OMAP5: DSS " Tomi Valkeinen
2014-03-16 11:41 ` Dmitry Lifshitz
2014-03-17 6:13 ` Tomi Valkeinen
2014-03-17 13:22 ` Dmitry Lifshitz
2014-03-17 13:28 ` Tomi Valkeinen
2014-03-17 14:22 ` Dmitry Lifshitz
2014-03-18 5:29 ` Tomi Valkeinen [this message]
2014-03-18 8:19 ` Dmitry Lifshitz
2014-03-18 8:37 ` Tomi Valkeinen
2014-03-18 12:23 ` Dmitry Lifshitz
2014-05-08 4:37 ` Paul Walmsley
2014-05-08 5:48 ` Archit Taneja
2014-05-08 16:01 ` Paul Walmsley
2014-05-09 6:19 ` Archit Taneja
2014-05-09 6:36 ` Tomi Valkeinen
2014-05-14 19:44 ` Paul Walmsley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5327D9BE.80503@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).