linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Igor Grinberg <grinberg@compulab.co.il>
Cc: "Aaro Koskinen" <aaro.koskinen@iki.fi>,
	"Thomas Weber" <weber@corscience.de>,
	"Mike Rapoport" <mike@compulab.co.il>,
	"Steve Sakoman" <steve@sakoman.com>,
	"Gražvydas Ignotas" <notasas@gmail.com>,
	linux-omap <linux-omap@vger.kernel.org>
Subject: Re: Request for OMAPDSS testing
Date: Mon, 17 Jun 2013 10:08:13 +0300	[thread overview]
Message-ID: <51BEB5DD.4000605@ti.com> (raw)
In-Reply-To: <51BDAF6A.1020102@compulab.co.il>

[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

On 16/06/13 15:28, Igor Grinberg wrote:

>>> Although one thing is missing from the tfp410 driver is
>>> the PD GPIO polarity. I had to adjust it locally to get the DVI working.
>>> The original polarity was high = disabled, low = enabled.
> 
>> Hmm, but this is missing from the old driver also, isn't it? At least
>> with a quick glance the old and new tfp410 drivers do the same thing
>> with the PD gpio.
> 
> Well, we were driving the PD GPIO from the board file...

Ah, I see. That was inverted PD handling was removed in 3.5, by accident
as far as I see. So DVI on cm-t35 has been broken since?

I wonder how that should be fixed... The tfp410 driver handles it
correctly, as the PD gpio is active low (i.e. high == tfp410 enabled),
so having it inverted is a board specific thing. Do you know what is the
reason to have it inverted?

There seems to be OF_GPIO_ACTIVE_LOW, but I'm not sure how it should be
used, as I don't see anyone setting that flag... And supporting that
would mean, in principle, that every driver should support inverting the
gpio with every gpio they have.

 Tomi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2013-06-17  7:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04  7:40 Request for OMAPDSS testing Tomi Valkeinen
2013-06-06 11:30 ` Igor Grinberg
2013-06-06 20:43 ` Aaro Koskinen
2013-06-07  8:39   ` Tomi Valkeinen
2013-06-09 14:28 ` Grazvydas Ignotas
2013-06-12  6:01   ` Tomi Valkeinen
2013-06-13 15:51 ` Igor Grinberg
2013-06-13 16:01   ` Tomi Valkeinen
2013-06-16 12:28     ` Igor Grinberg
2013-06-17  7:08       ` Tomi Valkeinen [this message]
2013-06-17  8:40         ` Igor Grinberg
2013-06-27  6:41           ` Tomi Valkeinen

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=51BEB5DD.4000605@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=grinberg@compulab.co.il \
    --cc=linux-omap@vger.kernel.org \
    --cc=mike@compulab.co.il \
    --cc=notasas@gmail.com \
    --cc=steve@sakoman.com \
    --cc=weber@corscience.de \
    /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).