From: tomi.valkeinen@nokia.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] OMAP: use generic panel driver in board files
Date: Wed, 03 Nov 2010 17:08:51 +0200 [thread overview]
Message-ID: <1288796931.5614.199.camel@tubuntu> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC356087034BE1EB1A@dbde02.ent.ti.com>
On Wed, 2010-11-03 at 13:56 +0100, ext Taneja, Archit wrote:
> Hi,
>
> linux-omap-owner at vger.kernel.org wrote:
> > Introduce some fields in struct panel, which will be used to
> > match the right panel configurations in generic panel driver.
> >
> > Still keep sharp_ls_panel, since the sharp_ls_panel driver
> > contains blacklight control driver code which will be moved
> > out later. Then we can use generic driver for sharp_ls_panel.
> >
> > Signed-off-by: Bryan Wu <bryan.wu@canonical.com>
>
> [snip]
>
> > diff --git a/arch/arm/plat-omap/include/plat/display.h
> > b/arch/arm/plat-omap/include/plat/display.h
> > index c915a66..6e1fbbd 100644
> > --- a/arch/arm/plat-omap/include/plat/display.h
> > +++ b/arch/arm/plat-omap/include/plat/display.h
> > @@ -346,6 +346,24 @@ struct omap_overlay_manager {
> > int (*disable)(struct omap_overlay_manager *mgr); };
> >
> > +struct omap_display_panel {
> > + struct omap_video_timings timings;
> > +
> > + int acbi; /* ac-bias pin transitions per interrupt */ + /* Unit: line
> > clocks */ + int acb; /* ac-bias pin frequency */
> > +
> > + enum omap_panel_config config;
> > +
> > + int power_on_delay;
> > + int power_off_delay;
> > + /*
> > + * Used to match device to panel configuration
> > + * when use generic panel driver
> > + */
> > + const char *name;
> > +};
> > +
> > struct omap_dss_device {
> > struct device dev;
> >
> > @@ -395,15 +413,7 @@ struct omap_dss_device {
> > } venc;
> > } phy;
> >
> > - struct {
> > - struct omap_video_timings timings;
> > -
> > - int acbi; /* ac-bias pin transitions per
> > interrupt */
> > - /* Unit: line clocks */
> > - int acb; /* ac-bias pin frequency */
> > -
> > - enum omap_panel_config config;
> > - } panel;
> > + struct omap_display_panel panel;
> >
> > struct {
> > u8 pixel_size;
>
> I don't think that changing the omap_dss_device structure is the best way
> to go about this. Members like power_on_delay and power_off_delay may not
> be required by all types of panels. Same goes for the new "name" member since
> its only used by the dummy dpi panels.
>
> I think it would be better to go with the approach taken in panel-taal.c
> where a struct "panel_config" exists to take care of extra requirements.
>
> The omap_dss_device struct should contain only those members which would be
> needed by the interface driver files like dsi.c, dpi.c etc. The rest should be
> taken care of the panel drivers internally.
Yes, the configuration for the panel is panel driver specific features,
and should not be in the standard structs. No need to add anything to
display.h.
In fact, there are things in display.h that should be removed, and this
configurable panel driver could do that also. omap_dss_device contains
reset_gpio, max_backlight_level, platform_enable/disable and
set/get_backlight, which should actually be in panel spesific struct.
Tomi
next prev parent reply other threads:[~2010-11-03 15:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 20:39 [PATCH 0/3] OMAP: DSS2: introduce generic panel display driver Bryan Wu
2010-11-02 20:39 ` [PATCH 1/3] OMAP: DSS2: Add " Bryan Wu
2010-11-02 20:39 ` [PATCH 2/3] OMAP: DSS2: remove generic panel driver duplicated panel drivers Bryan Wu
2010-11-02 20:39 ` [PATCH 3/3] OMAP: use generic panel driver in board files Bryan Wu
2010-11-03 12:56 ` Taneja, Archit
2010-11-03 15:08 ` Tomi Valkeinen [this message]
2010-11-03 15:42 ` Bryan Wu
2010-11-03 12:59 ` [PATCH 0/3] OMAP: DSS2: introduce generic panel display driver Taneja, Archit
2010-11-03 16:21 ` Bryan Wu
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=1288796931.5614.199.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).