On Fri, Oct 11, 2013 at 04:33:33PM -0600, Stephen Warren wrote:
> On 10/07/2013 02:34 AM, Thierry Reding wrote:
> > Add a driver for simple panels. Such panels can have a regulator that
> > provides the supply voltage and a separate GPIO to enable the panel.
> > Optionally the panels can have a backlight associated with them so it
> > can be enabled or disabled according to the panel's power management
> > mode.
> >
> > Support is added for three panels: An AU Optronics 10.1" WSVGA, a
> > Chunghwa Picture Tubes 10.1" WXGA and a Panasonic 10.1 WUXGA TFT LCD
> > panel.
>
> > .../devicetree/bindings/panel/auo,b101aw03.txt | 7 +
> > .../bindings/panel/chunghwa,claa101wb03.txt | 7 +
> > .../bindings/panel/panasonic,vvx10f004b00.txt | 7 +
> > .../devicetree/bindings/panel/simple-panel.txt | 21 ++
>
> Since this patch defines new DT bindings, it should also be sent to the
> DT binding maintainers and DT mailing list.
I Cc'ed at least the DT mailing list. The get_maintainer.pl generated
list was pretty large, and I keep getting different feedback about
whether it's a good idea to Cc individual people or just the relevant
mailing lists. In this case I assumed that all DT binding maintainers
would be reading the DT mailing list and therefore see the patches. I
can change my habit though if you prefer to get an extra copy.
One slight inconvenience with large series like this is that a lot of
work is required to handcraft an appropriate list of people and lists
to send the patches to. Furthermore I personally like receiving whole
patch series because it gives me full context, but other people seem
to want only the patches that they need to worry about. So what I
usually do is handcraft a list of people I want to send patches to
and use it for the whole series. If that list grows too large, I'll
usually trim it down to include only lists. Having to handcraft lists
for each individual patch doesn't sound that useful to me.
> > diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c
>
> > +static int panel_simple_remove(struct platform_device *pdev)
> > +{
> > + struct panel_simple *panel = platform_get_drvdata(pdev);
> > +
> > + if (gpio_is_valid(panel->enable_gpio)) {
> > + if (panel->enable_gpio_flags & GPIO_ACTIVE_LOW)
> > + gpio_set_value(panel->enable_gpio, 1);
> > + else
> > + gpio_set_value(panel->enable_gpio, 0);
> > +
> > + gpio_free(panel->enable_gpio);
> > + }
> > +
> > + regulator_disable(panel->supply);
>
> Can you just call panel_simple_disable() to do the HW cleanup, and just
> do resource cleanup here?
Yes, I can.
Thanks,
Thierry
Attachment:
pgpbQlQI34xeB.pgp
Description: PGP signature
