From: Lars-Peter Clausen <lars@metafoo.de>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: "Dr. H. Nikolaus Schaller" <hns@goldelico.com>,
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: Thu, 10 Oct 2013 12:26:16 +0000 [thread overview]
Message-ID: <52569CE8.5070201@metafoo.de> (raw)
In-Reply-To: <525699EF.6090803@ti.com>
On 10/10/2013 02:13 PM, Tomi Valkeinen wrote:
> On 10/10/13 14:52, Dr. H. Nikolaus Schaller wrote:
>
>> Yes, I agree and I am willing to help if someone comes up with such a SoC.
>> At the moment we have connected it to the OMAP3 only.
>
> True, but even without that kind of SoC, SPI bitbanging should be
> handled by an SPI driver, not by the drivers that use the bus.
>
>> I.e. I want not to do a lot of work for others who we just guess about that they
>> might exist...
>
> Yep. It's fine for me, it's not that much extra code in the panel driver.
>
>>> The panel hardware has three wires, so the panel driver (if it does
>>> handle the bus by bitbanging) can only refer to three gpios.
>>
>> Hm. The panle hardware has 3 but the SoC (OMAP3) the driver
>> is running on has 4.
>
> Right, but this panel driver is a driver for the panel hardware. Not for
> the SoC, or the SoC+panel combination. So the panel driver must only use
> resources as seen by the panel hardware.
>
>>> So either
>>> the bus details should be hidden by using the normal spi framework, or
>>> if the driver does the bitbanging, use the gpios as specified in the
>>> panel spec. The panel driver cannot contain any board specific stuff.
>>
>> The bitbang driver shown below can handle either 3 or 4 gpios (except
>> for initialization).
>
> It's not a bitbang driver, it's a panel driver. And anyway, if I
> understood right, your use of 4 gpios was just a hack to try to make it
> look like a normal 4-wire SPI bus. What you really have is 3 wires, 3
> gpios. I don't see any reason to use 4 gpios, as two of them are the same.
>
> Hmm, how does it work anyway. Did I understand it right, the panel's
> 'DIN' pin is connected to two gpios on the SoC, and one of those gpios
> is set as output, and the other as input? So the SoC is always pulling
> that line up or down, and the panel is also pulling it up or down when
> it's sending data. I'm no HW guy but that sounds quite bad =).
>
> I've never written or studied a bitbanging driver, but shouldn't there
> be just one gpio used on the SoC for DIN, and it would be set to either
> output or input mode, depending on if we are reading or writing?
Back in the OpenMoko days we used the panel in normal 4-wire SPI mode with
the GPIO bitbang SPI master. The bitbang code in this driver also looks like
normal 4 wire.
- Lars
next prev parent reply other threads:[~2013-10-10 12:26 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 [this message]
2013-10-10 13:42 ` Dr. H. Nikolaus Schaller
2013-10-10 18:58 ` Lars-Peter Clausen
2013-10-11 4:41 ` Tomi Valkeinen
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=52569CE8.5070201@metafoo.de \
--to=lars@metafoo.de \
--cc=hns@goldelico.com \
--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 \
--cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).