All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] PATCH: hwmon-abituguru-suspend-resume.patch
Date: Mon, 21 Aug 2006 12:34:17 +0000	[thread overview]
Message-ID: <20060821143417.cec8280a.khali@linux-fr.org> (raw)
In-Reply-To: <44DB2470.3050507@hhs.nl>

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.

Good question, I really don't know. If sysfs doesn't guarantee it, then
we should do something similar for all hardware monitoring drivers,
it's simple enough.

Maybe you can raise the question on LKML, or maybe linux-pm-devel
(doesn't seem too active though) or otherwise ask anyone with more
power management knowledge than I do?

> 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).

Well this patch shouldn't harm, even if it doesn't do anything
useful ;) so I guess I can take it.

> @@ -1336,6 +1380,8 @@
>  	},
>  	.probe	= abituguru_probe,
>  	.remove	= __devexit_p(abituguru_remove),
> +	.suspend = abituguru_suspend,
> +	.resume = abituguru_resume
>  };

This makes the alignment a bit shaky, tabs and spaces mixed... I'll fix
it.

Thanks,
-- 
Jean Delvare


  reply	other threads:[~2006-08-21 12:34 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 [this message]
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
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=20060821143417.cec8280a.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --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.