linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Courbot <acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Mark Zhang <markz-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Thierry Reding
	<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2] ARM: tegra: ventana: enable internal display
Date: Mon, 19 Nov 2012 18:35:53 +0900	[thread overview]
Message-ID: <4911534.ydU4D3qycf@percival> (raw)
In-Reply-To: <50A672DF.1070003-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

On Saturday 17 November 2012 01:07:43 Stephen Warren wrote:
> That should be equivalent to something like:
> 
> 	nvidia,ddc-i2c-bus = <&lcd_ddc>;
> 
> with lcd_ddc pointing at /i2cmux/i2c@1
> 
> That seems to work fine for me; how about you?

Yep, this is working! DC probing gets delayed probably because i2c is not 
available when it first tries to initialize it, and as a result fb0 becomes 
available 1 second later than when we feed the EDID data from the DT. But it 
work and is the most elegant solution, so we should definitely do this.

Alex.

  parent reply	other threads:[~2012-11-19  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16  7:44 [PATCH v2] ARM: tegra: ventana: enable internal display Alexandre Courbot
     [not found] ` <1353051891-26725-1-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-11-16  7:51   ` Alex Courbot
2012-11-16 17:07     ` Stephen Warren
     [not found]       ` <50A672DF.1070003-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-11-19  9:35         ` Alex Courbot [this message]
2012-11-19  2:55     ` Mark Zhang
2012-11-16 20:49   ` Thierry Reding

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=4911534.ydU4D3qycf@percival \
    --to=acourbot-ddmlm1+adcrqt0dzr+alfa@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;
as well as URLs for NNTP newsgroup(s).