From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Sathya Prakash <a0393677@ti.com>
Cc: Sathya Prakash M R <sathyap@ti.com>,
tony@atomide.com, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, pawel.moll@arm.com, paul@pwsan.com
Subject: Re: [PATCH 2/2] ARM: DTS: AM43x: Add sii9022 dt information
Date: Tue, 18 Mar 2014 13:03:26 +0200 [thread overview]
Message-ID: <532827FE.30203@ti.com> (raw)
In-Reply-To: <5328268C.1030306@ti.com>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
On 18/03/14 12:57, Sathya Prakash wrote:
>> You add the same label, "dpi_out" to both endpoints. Does this even
>> compile?
>>
>> As there's just one port, you can leave out the 'ports' node.
> Will check. the ports was added as per documentation in
> video-interfaces.txt
It mentions that the 'ports' is optional.
> Can you suggest how to add the 2 dpi_out endpoints?
Didn't try, but:
port {
#address-cells = <1>;
#size-cells = <0>;
dpi_lcd_out: endpoint@0 {
reg = <0>;
remote-endpoint = <&lcd_in>;
data-lines = <24>;
};
dpi_sii_out: endpoint@1 {
reg = <1>;
remote-endpoint = <&sii9022_in>;
data-lines = <24>;
};
};
However, we still need to handle the GPIO which is used to select the
LCD or HDMI. So, maybe the above works, but we should try the
encoder-gpio-switch to handle the GPIO, which we discussed about earlier.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-03-18 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 10:07 [RFC PATCH 0/2] Sil9022 DPI to HDMI Encoder Sathya Prakash M R
2014-03-18 10:07 ` [PATCH 1/2] OMAPDSS: Add Sil9022 DPI-HDMI Encoder Driver Sathya Prakash M R
2014-03-18 11:20 ` Tomi Valkeinen
2014-03-18 10:07 ` [PATCH 2/2] ARM: DTS: AM43x: Add sii9022 dt information Sathya Prakash M R
2014-03-18 10:31 ` Tomi Valkeinen
2014-03-18 10:57 ` Sathya Prakash
2014-03-18 11:03 ` Tomi Valkeinen [this message]
2014-03-18 10:56 ` [RFC PATCH 0/2] Sil9022 DPI to HDMI Encoder Mark Rutland
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=532827FE.30203@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=a0393677@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=pawel.moll@arm.com \
--cc=sathyap@ti.com \
--cc=tony@atomide.com \
/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).