From: Stefan Agner <stefan@agner.ch>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: devicetree@vger.kernel.org, linux@arm.linux.org.uk,
swarren@wwwdotorg.org, linux-kernel@vger.kernel.org,
marcel@ziswiler.com, Philipp Zabel <p.zabel@pengutronix.de>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/3] drm/panel: add support for EDT panels
Date: Thu, 15 May 2014 11:36:33 +0200 [thread overview]
Message-ID: <90bb509e9aa9c705790e2e0574d77b9f@agner.ch> (raw)
In-Reply-To: <20140515090814.GB6434@ulmo>
Am 2014-05-15 11:08, schrieb Thierry Reding:
> On Thu, May 15, 2014 at 10:27:29AM +0200, Philipp Zabel wrote:
>> The ETM0700G0DH6 Datasheet lists 2 lines as the typical vsync pulse
>> width, 525 lines as the vertical period, and 35 lines as the vsync -de
>> time, which is vsync len + back porch.
>> So vertical timings 480 + 10 + 2 + 33 = 525 should be valid for the
>> ET0700G0DH6 panel:
>
> Shouldn't that work with 480 + 8 + 2 + 35 too? It seems to me that it
> should still be safe for that panel. Similarily I'd expect your timings
> to work on the ET070080DH6.
Am 2014-05-15 11:12, schrieb Thierry Reding:
> Okay, so that means that the panel works for you with the same timings
> that Philipp has in the ETM0700G0DH6 patch? If so then I definitely
> think we should be sharing the timings in the driver by making the two
> compatible entries point to the same driver data.
FWIW, I checked and it works with both timings. And I bet it is really
the same panel its just a different touch on top.
> Irrespective of that they both seem to have different capabilities so
> two compatible values should be fine. However for the purpose of the
> simple panel driver they could be made to share the same timings if it
> works for both panels and devices.
>
> As for the touch panel on the ETM0700G0DH6, do you happen to know how
> that's usually connected? I suspect it needs external hardware to
> capture the YU, XL, YD and XR pins and turn that into raw coordinates
> and pen down interrupts.
For Colibri Evaluation Board, those pins are routed to the generic
4-wire pins of the Colibri SO-DIMM. On the Colibri T30 module, those
pins are connected to a STMPE811. I also added that to the device tree
once, however it does not work properly atm, I need to debug this and
will send a patch at a later time.
--
Stefan
next prev parent reply other threads:[~2014-05-15 9:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 21:45 [PATCH v2 0/4] ARM: tegra: initial support for Colibri T30 stefan
2014-05-14 21:45 ` [PATCH v2 2/3] drm/panel: add support for EDT panels stefan
[not found] ` <35c081171a3d9a9401767601c02a12e266b37dd0.1400103181.git.stefan-XLVq0VzYD2Y@public.gmane.org>
2014-05-15 7:51 ` Thierry Reding
2014-05-15 8:24 ` Stefan Agner
2014-05-15 9:12 ` Thierry Reding
2014-05-15 9:35 ` Philipp Zabel
[not found] ` <1400146519.4102.30.camel-+qGW7pzALmz7o/J7KWpOmN53zsg1cpMQ@public.gmane.org>
2014-05-15 9:39 ` Stefan Agner
2014-05-15 8:27 ` Philipp Zabel
[not found] ` <1400142449.4102.16.camel-+qGW7pzALmz7o/J7KWpOmN53zsg1cpMQ@public.gmane.org>
2014-05-15 9:08 ` Thierry Reding
2014-05-15 9:30 ` Philipp Zabel
2014-05-15 9:36 ` Stefan Agner [this message]
[not found] ` <cover.1400103181.git.stefan-XLVq0VzYD2Y@public.gmane.org>
2014-05-14 21:45 ` [PATCH v2 1/3] ARM: tegra: enable MCP251x CAN controller and DS1307 RTC stefan-XLVq0VzYD2Y
[not found] ` <4cc13e0aba03a5b2d3e5f4049d252956342b1dad.1400103181.git.stefan-XLVq0VzYD2Y@public.gmane.org>
2014-05-15 18:15 ` Stephen Warren
2014-05-14 21:45 ` [PATCH v2 3/3] ARM: tegra: initial add of Colibri T30 stefan-XLVq0VzYD2Y
[not found] ` <a8f01e573dcb7d563833ddcda30567e8ac7626ed.1400103181.git.stefan-XLVq0VzYD2Y@public.gmane.org>
2014-05-15 18:37 ` Stephen Warren
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=90bb509e9aa9c705790e2e0574d77b9f@agner.ch \
--to=stefan@agner.ch \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marcel@ziswiler.com \
--cc=p.zabel@pengutronix.de \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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).