From: j.w.r.degoede@hhs.nl (Hans de Goede)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] PATCH: hwmon-abituguru-suspend-resume.patch
Date: Mon, 28 Aug 2006 09:42:44 +0000 [thread overview]
Message-ID: <44F2BA94.7010907@hhs.nl> (raw)
In-Reply-To: <44DB2470.3050507@hhs.nl>
Jean Delvare wrote:
> Hi Hans,
>
>> This patch contains rudimentary suspend / resume support for the uguru,
>> this protects the uguru and the driver against suspend / resume cycles,
>> so there is no reason to unload the driver in your suspend / resume scripts.
>>
>> I'm not sure if this is needed, does the sysfs code itself guarantee
>> that no sysfs attr read/write calls are in progress before starting a
>> resume, if it does then this patch most likely isn't needed. Except for
>> protecting against this, it also checks the uguru is still in ready
>> status after a resume, but that seems to be unnescesarry (as it seems
>> that the uguru always is still ready after the resume).
>
> I've noticed that most drivers take care to exclude the suspend/resume
> functions when CONFIG_PM is disabled. I agree it shouldn't matter much
> for the abituguru driver, as ACPI implies CONFIG_PM and I don't think
> anyone would run these boards with ACPI support. But in an attempt to
> make things as good as possible (in case others copy that code for
> other hwmon driver), what about stacking the following patch on top of
> yours?
>
>
> Only include suspend/resume functions when CONFIG_PM is set.
>
> Signed-off-by: Jean Delvare <khali at linux-fr.org>
> ---
> drivers/hwmon/abituguru.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> --- linux-2.6.18-rc5.orig/drivers/hwmon/abituguru.c 2006-08-28 11:09:39.000000000 +0200
> +++ linux-2.6.18-rc5/drivers/hwmon/abituguru.c 2006-08-28 11:31:26.000000000 +0200
> @@ -1354,6 +1354,7 @@
> return NULL;
> }
>
> +#ifdef CONFIG_PM
> static int abituguru_suspend(struct platform_device *pdev, pm_message_t state)
> {
> struct abituguru_data *data = platform_get_drvdata(pdev);
> @@ -1372,6 +1373,10 @@
> mutex_unlock(&data->update_lock);
> return 0;
> }
> +#else
> +#define abituguru_suspend NULL
> +#define abituguru_resume NULL
> +#endif /* CONFIG_PM */
>
> static struct platform_driver abituguru_driver = {
> .driver = {
>
> Thanks,
Looks good, feel free to apply it I'll apply it locally too.
Regards,
Hans
next prev parent reply other threads:[~2006-08-28 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 12:20 [lm-sensors] PATCH: hwmon-abituguru-suspend-resume.patch Hans de Goede
2006-08-21 12:34 ` Jean Delvare
2006-08-24 11:29 ` Hans de Goede
2006-08-24 21:15 ` Jean Delvare
2006-08-28 9:39 ` Jean Delvare
2006-08-28 9:42 ` Hans de Goede [this message]
2006-08-28 9:48 ` Jean Delvare
2006-08-28 9:53 ` Hans de Goede
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=44F2BA94.7010907@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.