From: Alex Courbot <acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Thierry Reding
<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
markz-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH] tegra: ventana: display and backlight DT entries
Date: Wed, 14 Nov 2012 14:36:13 +0900 [thread overview]
Message-ID: <1393946.fMW2YXfOao@percival> (raw)
In-Reply-To: <50A2797C.9030807-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On Wednesday 14 November 2012 00:46:52 Stephen Warren wrote:
> I do tend to think that we should use EDID where there is one.
>
> 1) If there is an EDID in the panel HW, and the panel's I2C is hooked
> up to Tegra, we should read it out at runtime.
According to Ventana' platform design guide the LCD panel is hooked on I2C2.
The panel's data sheet lists CLK_EDID and DATA_EDID pins, which I assume are
for I2C, but there is no mention of an I2C address in both guides.
> 2) Otherwise, if the panel's documentation provides an EDID, we should
> use that, since it's the most canonical/common/standard representation
> of the panel's properties.
Panel's documentation indeed provides full EDID specification in appendix. Mark
sent me an EDID blob which works but I don't know where it comes from - Mark,
could you tell us?
> 3) Otherwise, use the videomode DT bindings.
>
> Another benefit of (2) is that we can actually support the panel
> without waiting for the videomode DT bindings to be finalized and merged.
Is there another incentive for preferring (2) over (3)? EDID specs can easily
be turned into videomode bindings, and it would also avoid introducing a new
file into the kernel source.
> Although if Ventana requires the power sequences helpers, that already
> means we won't be able to support Ventana's panel in 3.8 unless the
> power sequences code gets merged for 3.8; is that likely?
Likely, I don't know, possible - maybe. Power seqs work and I could push to
get them merged, but the following points need to be considered:
- DT bindings are likely to change from their current form. I want to take
advantage of the gpio API changes that are undergoing, and also probably of
your preprocessor patch for dtc (not sure if that is already usable in the
kernel?). Considering the feature is young I don't think a DT change would be
a big deal, but the general consensus seems to be that DT bindings are
immutable - maybe my perception is wrong?
- If I am to take maintainership of the feature, I guess I will have to get
the patches sufficiently Ack'ed by enough people, and also have someone else
pull from my tree (Linus? Or maybe some other power maintainer?). I am not
familiar with the exact procedure here - moreover, my GPG key only has one
signature from a trusted kernel dev, I am not sure if this is enough.
Alex.
next prev parent reply other threads:[~2012-11-14 5:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 10:23 [PATCH] tegra: ventana: display and backlight DT entries Alexandre Courbot
[not found] ` <1352802204-1740-1-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-11-13 12:34 ` Thierry Reding
[not found] ` <20121113123410.GA11202-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2012-11-13 16:46 ` Stephen Warren
[not found] ` <50A2797C.9030807-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-11-14 2:59 ` Mark Zhang
2012-11-14 5:36 ` Alex Courbot [this message]
2012-11-14 5:56 ` Mark Zhang
[not found] ` <50A3329D.8000708-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-11-14 6:01 ` Mark Zhang
2012-11-14 6:55 ` Thierry Reding
2012-11-14 16:09 ` Stephen Warren
[not found] ` <50A3C24C.6090004-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-11-15 5:45 ` Power sequences upstreaming (Was: Re: [PATCH] tegra: ventana: display and backlight DT entries) Alex Courbot
2012-11-15 6:03 ` Anton Vorontsov
2012-11-15 6:09 ` Alex Courbot
2012-11-15 6:25 ` Anton Vorontsov
2012-11-16 5:52 ` Alex Courbot
2012-11-16 7:45 ` Anton Vorontsov
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=1393946.fMW2YXfOao@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).