From: Archit Taneja <a0393947@ti.com>
To: Jassi Brar <jaswinder.singh@linaro.org>
Cc: Raphael Assenat <raph@8d.com>,
linux-omap@vger.kernel.org,
Tomi Valkeinen <tomi.valkeinen@ti.com>
Subject: Re: [PATCH] OMAPDSS: Add timings for ChiMei G121S1-L01/L02 and G121X1-L01 LCD displays
Date: Fri, 20 Jul 2012 13:41:51 +0530 [thread overview]
Message-ID: <500912C7.8080204@ti.com> (raw)
In-Reply-To: <CAJe_ZhfoYoFd1AkFmb0E7=iSvZeAQRmSFONCW7jE8psCMDQ3Hg@mail.gmail.com>
Hi,
On Tuesday 17 July 2012 09:57 PM, Jassi Brar wrote:
> [CC'ing OMAPDSS matinainer]
>
> On 17 July 2012 19:31, Raphael Assenat <raph@8d.com> wrote:
>> Add timings for ChiMei G121S1-L01/L02 and G121X1-L01 LCD displays.
>>
> Display panels are board specific and there is no limit to the number
> of panels that could be connected to omap dss.
> Does it make sense to get panel params via DT? Or at least have them
> come from board file? (esp when there is hardly a panel shared by two
> boards, and some panels aren't even used by any board in mainline)
>
A panel specific param should stay in the panel driver, it's something
which is specific to the panel and not the platform it is in, things
like the gpio reset number, i2c connections with the panel etc would
make sense to come via DT/board file.
It's true that currently omap platforms don't share the same panels, but
there is no stopping us to do that. We could remove the default panel
and attach a new one, even though we won't upstream non default panels
in the DT/board file, it would be always easier to make this change in
software if most of the panel specific info stays in the panel driver.
Also, 2 platforms of different SoC's may use the same panel. Currently
the panel drivers are SoC specific, but there is work being done between
different display maintainers so that the same panel driver works across
different SoCs.
Archit
next prev parent reply other threads:[~2012-07-20 8:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 14:01 [PATCH] OMAPDSS: Add timings for ChiMei G121S1-L01/L02 and G121X1-L01 LCD displays Raphael Assenat
2012-07-17 16:27 ` Jassi Brar
2012-07-20 8:11 ` Archit Taneja [this message]
2012-07-20 12:13 ` Jassi Brar
2012-07-20 12:44 ` Archit Taneja
2012-07-20 15:38 ` Jassi Brar
2012-07-31 7:51 ` Tomi Valkeinen
2012-07-31 8:03 ` Jassi Brar
2012-07-31 8:14 ` Tomi Valkeinen
2012-07-31 8:27 ` Jassi Brar
2012-07-31 8:42 ` Tomi Valkeinen
2012-07-31 8:57 ` Jassi Brar
2012-07-31 9:57 ` Tomi Valkeinen
2012-07-31 18:14 ` Jassi Brar
2012-08-15 9:31 ` Tomi Valkeinen
2012-08-15 15:26 ` Raphaël Assénat
2012-08-21 10:49 ` Tomi Valkeinen
2012-08-21 14:29 ` Raphaël Assénat
2012-08-24 8:38 ` Tomi Valkeinen
2012-08-24 13:50 ` Raphaël Assénat
2012-08-24 15:00 ` 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=500912C7.8080204@ti.com \
--to=a0393947@ti.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=raph@8d.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).