From: Arnd Bergmann <arnd@arndb.de>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 1/1] smiapp: Implement power-on and power-off sequences without runtime PM
Date: Fri, 18 Nov 2016 17:09:01 +0100 [thread overview]
Message-ID: <3365592.8lQdWk1zFY@wuerfel> (raw)
In-Reply-To: <1479477016-28450-1-git-send-email-sakari.ailus@linux.intel.com>
On Friday, November 18, 2016 3:50:16 PM CET Sakari Ailus wrote:
> Power on the sensor when the module is loaded and power it off when it is
> removed.
>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
> Hi Arnd and others,
>
> The patch is tested with CONFIG_PM set, as the system does I was testing
> on did not boot with CONFIG_PM disabled. I'm not really too worried about
> this though, the patch is very simple.
>
> static struct smiapp_hwconfig *smiapp_get_hwconfig(struct device *dev)
> {
> struct smiapp_hwconfig *hwcfg;
> @@ -2915,7 +2906,11 @@ static int smiapp_probe(struct i2c_client *client,
>
> pm_runtime_enable(&client->dev);
>
> +#ifdef CONFIG_PM
> rval = pm_runtime_get_sync(&client->dev);
> +#else
> + rval = smiapp_power_on(&client->dev);
> +#endif
> if (rval < 0) {
> rval = -ENODEV;
> goto out_power_off;
I would suggest writing this as
if (IS_ENABLED(CONFIG_PM))
rval = pm_runtime_get_sync(&client->dev);
else
rval = smiapp_power_on(&client->dev);
though that is a purely cosmetic change.
I think you are missing one other warning: with CONFIG_PM=y and
CONFIG_PM_SLEEP=n, the smiapp_suspend/smiapp_resume functions
are now unused and need to be marked as __maybe_unused.
Arnd
next prev parent reply other threads:[~2016-11-18 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 13:50 [PATCH 1/1] smiapp: Implement power-on and power-off sequences without runtime PM Sakari Ailus
2016-11-18 16:09 ` Arnd Bergmann [this message]
2016-11-22 18:31 ` Laurent Pinchart
2016-11-22 20:58 ` Arnd Bergmann
2016-11-25 0:43 ` Laurent Pinchart
2016-11-25 2:15 ` Alan Stern
2016-11-25 7:48 ` Sakari Ailus
2016-11-25 15:21 ` Alan Stern
2016-11-25 19:34 ` Laurent Pinchart
2016-11-26 20:10 ` Alan Stern
2016-11-28 7:58 ` Laurent Pinchart
2016-11-28 15:45 ` Alan Stern
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=3365592.8lQdWk1zFY@wuerfel \
--to=arnd@arndb.de \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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