From: Thomas Weber <weber@corscience.de>
To: Tomi Valkeinen <tomi.valkeinen@nokia.com>
Cc: ext Jaya Kumar <jayakumar.lkml@gmail.com>,
Thomas Weber <swirl@gmx.li>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND][PATCHv2 4/4] OMAP: DSS2: Add Innolux 7" display for
Date: Fri, 19 Feb 2010 12:57:08 +0000 [thread overview]
Message-ID: <4B7E8AA4.40307@corscience.de> (raw)
In-Reply-To: <1265988343.2433.312.camel@tubuntu.research.nokia.com>
Tomi Valkeinen wrote:
> On Fri, 2010-02-12 at 06:55 +0100, ext Jaya Kumar wrote:
>
>> On Fri, Feb 12, 2010 at 3:41 AM, Thomas Weber <swirl@gmx.li> wrote:
>>
>
> [snip]
>
>
>>> +
>>> +static struct omap_video_timings innolux_at_timings = {
>>> + .x_res = 800,
>>> + .y_res = 480,
>>> +
>>> + .pixel_clock = 40000,
>>> +
>>> + .hsw = 48,
>>> + .hfp = 1,
>>> + .hbp = 1,
>>> +
>>> + .vsw = 3,
>>> + .vfp = 12,
>>> + .vbp = 25,
>>> +};
>>> +
>>> +static int innolux_at_panel_probe(struct omap_dss_device *dssdev)
>>> +{
>>> + dssdev->panel.config = OMAP_DSS_LCD_TFT | OMAP_DSS_LCD_IVS |
>>> + OMAP_DSS_LCD_IHS;
>>> + dssdev->panel.acb = 0x28;
>>> + dssdev->panel.timings = innolux_at_timings;
>>> +
>>> + return 0;
>>> +}
>>> +
>>>
>> Hi Thomas, Tomi,
>>
>> Just curious, does this patch imply that code like this needs to be
>> written for every single LCD type and resolution that can be connected
>> to omap2? Maybe there is a better way, like a common table of timings
>> and values that can be selected with a module option or even
>> autodetected.
>>
>
> Yes, it is true that currently you need to write these for every LCD. I
> have been thinking this issue, and I think we can make a common driver.
>
> However, it's not just selecting timings, as LCDs can have also other
> characteristics than just the video timings. For example, some may have
> power on/off line, some reset enable/disable, some need 50ms after
> reset, some 80ms after reset etc.
>
> But if we manage to get a sane set of those settings into the table, we
> could perhaps cover most of the "dummy" LCDs with it.
>
> This change doesn't probably need any changes to the DSS core, only for
> the panel driver. Any takers for this task? =)
>
> Tomi
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
Hello,
sorry but I am not able to take the task.
Make it sense to rework this patch or do you want first the changes to
the panel driver?
Thomas
next prev parent reply other threads:[~2010-02-19 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 19:41 [RESEND][PATCHv2 4/4] OMAP: DSS2: Add Innolux 7" display for DEVKIT8000 Thomas Weber
2010-02-12 5:50 ` [RESEND][PATCHv2 4/4] OMAP: DSS2: Add Innolux 7" display for Hiremath, Vaibhav
2010-02-12 5:55 ` Jaya Kumar
2010-02-12 15:25 ` Tomi Valkeinen
2010-02-19 12:57 ` Thomas Weber [this message]
2010-02-23 11:54 ` 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=4B7E8AA4.40307@corscience.de \
--to=weber@corscience.de \
--cc=jayakumar.lkml@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=swirl@gmx.li \
--cc=tomi.valkeinen@nokia.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).