From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Lars-Peter Clausen <lars@metafoo.de>,
"Dr. H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Marek Belisko <marek@goldelico.com>,
plagnioj@jcrosoft.com, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD.
Date: Fri, 11 Oct 2013 07:41:03 +0300 [thread overview]
Message-ID: <5257815F.5070803@ti.com> (raw)
In-Reply-To: <5256F8DF.2020801@metafoo.de>
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
On 10/10/13 21:58, Lars-Peter Clausen wrote:
> According to the datasheet the the panel as a dedicated dout pin. Maybe
> you did not connect it in your design, which means you won't be able to
> read any data from the panel at all.
I don't see a dedicated dout in the datasheet...
http://dl.wolfgang-draxinger.net/openmoko/doc/TD028TTEC1.pdf
> Also your custom bitbang code looks a bit strange:
>
> gpio_set_value(data->dout_gpio, 1);
> if (gpio_get_value(data->din_gpio) == 0)
> return 1;
>
> You set the state on the dout pin and then read the din pin, if both do
> not match you abort with an error. This suggest that, for whatever
> reason, you feed the dout pin back into the din pin in your design. Btw.
> this is also the only place where din is used in your driver.
Yes, he said the single "Serial interface data input/output" pin is
connected to both din and dout on the SoC. I guess the purpose of that
gpio_get_value() is to ensure that the panel is not pulling the line
when the SoC is writing to it. Not that I really understand how that can
work, but I'm not a HW guy =).
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2013-10-11 4:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 21:08 [PATCH] omapdss: Add new panel driver for Topolly td028ttec1 LCD Marek Belisko
2013-10-10 8:19 ` Tomi Valkeinen
2013-10-10 9:34 ` Dr. H. Nikolaus Schaller
2013-10-10 11:10 ` Tomi Valkeinen
2013-10-10 11:52 ` Dr. H. Nikolaus Schaller
2013-10-10 12:13 ` Tomi Valkeinen
2013-10-10 12:26 ` Lars-Peter Clausen
2013-10-10 13:42 ` Dr. H. Nikolaus Schaller
2013-10-10 18:58 ` Lars-Peter Clausen
2013-10-11 4:41 ` Tomi Valkeinen [this message]
2013-10-11 7:08 ` Lars-Peter Clausen
2013-10-11 7:42 ` Dr. H. Nikolaus Schaller
2013-10-11 8:17 ` Tomi Valkeinen
2013-10-11 8:59 ` Belisko Marek
2013-10-11 9:04 ` Tomi Valkeinen
2013-10-11 9:06 ` Lars-Peter Clausen
2013-10-11 9:50 ` Dr. H. Nikolaus Schaller
2013-10-11 10:09 ` Tomi Valkeinen
2013-10-11 11:03 ` Dr. H. Nikolaus Schaller
2013-10-11 7:29 ` Dr. H. Nikolaus Schaller
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=5257815F.5070803@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=hns@goldelico.com \
--cc=lars@metafoo.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=marek@goldelico.com \
--cc=plagnioj@jcrosoft.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