From: Alex Courbot <acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Mark Zhang <markz-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Thierry Reding
<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v3] ARM: tegra: ventana: enable internal display
Date: Tue, 20 Nov 2012 10:47:44 +0900 [thread overview]
Message-ID: <6034130.4mMqBdPRel@percival> (raw)
In-Reply-To: <50AADEE5.2030302-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On Tuesday 20 November 2012 09:37:41 Mark Zhang wrote:
> Great. So this means I2C2 is used for LCD and HDMI both. While HDMI is
> not plugged, the EDID of LCD will be checked out, right?
Ahhh. So that's why the LCD DDC was not working during my previous tests - I
had HDMI nodes in my DT as well as the HDMI cable plugged! Indeed, things seem
to work as you described. I assumed the i2cmux node would set the right pin
configuration according to whether we want to read the LCD or HDMI DDC, but
apparently this is not totally working yet. Glad we figured it out. Adding the
HDMI nodes to Ventana will probably require to fix this (along with other
things, probably) first.
Alex.
next prev parent reply other threads:[~2012-11-20 1:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 9:43 [PATCH v3] ARM: tegra: ventana: enable internal display Alexandre Courbot
[not found] ` <1353318187-26484-1-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-11-20 1:37 ` Mark Zhang
[not found] ` <50AADEE5.2030302-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-11-20 1:47 ` Alex Courbot [this message]
2012-11-20 5:08 ` Stephen Warren
[not found] ` <50AB1044.5030704-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-11-20 5:11 ` Alex Courbot
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=6034130.4mMqBdPRel@percival \
--to=acourbot-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=markz-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.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