From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Oliver Neukum <oliver@neukum.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, Nicu Pavel <npavel@ituner.com>,
Jaya Kumar <jayakumar.lkml@gmail.com>,
"Rick L. Vinyard Jr." <rvinyard@cs.nmsu.edu>
Subject: Re: [PATCH 2/2] hid: add PM support to PicoLCD device
Date: Tue, 27 Apr 2010 22:16:48 +0200 [thread overview]
Message-ID: <20100427221648.39735c41@neptune.home> (raw)
In-Reply-To: <alpine.LNX.2.00.1004271525330.9849@pobox.suse.cz>
On Tue, 27 April 2010 Jiri Kosina <jkosina@suse.cz> wrote:
> On Sun, 25 Apr 2010, Bruno Prémont wrote:
>
> > Add PM support in order to turn off backlight on suspend, restore
> > it on resume and especially restore complete state on reset-resume.
> >
> > Signed-off-by: Bruno Prémont <bonbons@linux-vserver.org>
> > ---
> > drivers/hid/hid-picolcd.c | 61 +++++++++++++++++++++++++++++++++++++++++++++
> > 1 files changed, 61 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/hid/hid-picolcd.c b/drivers/hid/hid-picolcd.c
> > index aa6f2e1..c652390 100644
> > --- a/drivers/hid/hid-picolcd.c
> > +++ b/drivers/hid/hid-picolcd.c
> > @@ -852,6 +852,20 @@ static inline int picolcd_resume_backlight(struct picolcd_data *data)
> > return picolcd_set_brightness(data->backlight);
> > }
> >
> > +#ifdef CONFIG_PM
> > +static void picolcd_suspend_backlight(struct picolcd_data *data)
> > +{
> > + int bl_power = data->lcd_power;
> > + if (!data->backlight)
> > + return;
> > +
> > + data->backlight->props.power = FB_BLANK_POWERDOWN;
> > + picolcd_set_brightness(data->backlight);
> > + data->lcd_power = data->backlight->props.power = bl_power;
> > +}
> > +#else
> > +#define picolcd_suspend_backlight(a)
> > +#endif /* CONFIG_PM */
>
> Stylistic thing -- it would be nice if this was actually
>
> static inline void picolcd_suspend_backlight(struct picolcd_data *data)
> {
> return 0;
> }
>
> But why do you need to have it defined in !CONFIG_PM situation anyway?
> It's not used otherwise at all.
Yeah, I could drop the #else branch (of #ifconfig CONFIG_PM).
Is gcc quiet about defined but unused static inline functions?
It's in order to avoid those warnings that I used #define bla().
(same in other occasions of stubs returning void.
Might be I forgot the inline keyword for the case I got the warning
about defined but unused function. Will check tomorrow.
> > #else
> > static inline int picolcd_init_backlight(struct picolcd_data *data,
> > struct hid_report *report)
> > @@ -865,6 +879,7 @@ static inline int picolcd_resume_backlight(struct picolcd_data *data)
> > {
> > return 0;
> > }
> > +#define picolcd_suspend_backlight(a)
>
> Any why is it defined once more here?
Thats in the case where CONFIG_HID_PICOLCD_BACKLIGHT is not defined.
c.f. the #else at the beginning of this quote.
Thanks,
Bruno
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-27 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 19:40 [PATCH 1/2] hid: add suspend/resume hooks for hid drivers Bruno Prémont
2010-04-25 19:43 ` [PATCH 2/2] hid: add PM support to PicoLCD device Bruno Prémont
2010-04-27 13:28 ` Jiri Kosina
2010-04-27 20:16 ` Bruno Prémont [this message]
2010-04-27 20:57 ` Jiri Kosina
2010-05-02 14:05 ` Bruno Prémont
[not found] ` <20100502160505.4acc9f1c-hY15tx4IgV39zxVx7UNMDg@public.gmane.org>
2010-05-03 13:28 ` Jiri Kosina
[not found] ` <20100425214003.7e87c6a3-hY15tx4IgV39zxVx7UNMDg@public.gmane.org>
2010-04-27 13:25 ` [PATCH 1/2] hid: add suspend/resume hooks for hid drivers Jiri Kosina
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=20100427221648.39735c41@neptune.home \
--to=bonbons@linux-vserver.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jayakumar.lkml@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=npavel@ituner.com \
--cc=oliver@neukum.org \
--cc=rvinyard@cs.nmsu.edu \
/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).