From: Michael Frank <mhf@linuxmail.org>
To: linux-kernel@vger.kernel.org
Cc: Wolfgang Glas <wolfgang.glas@ev-i.at>,
swsusp-devel@lists.sourceforge.net
Subject: Fwd: [Swsusp-devel] Kernel 2.6 pm_send_all() issues.
Date: Tue, 10 Feb 2004 23:43:06 +0800 [thread overview]
Message-ID: <200402102343.06896.mhf@linuxmail.org> (raw)
This question is probably better suited for LKML.
---------- Forwarded Message ----------
Subject: [Swsusp-devel] Kernel 2.6 pm_send_all() issues.
Date: Tuesday 10 February 2004 04:06
From: Wolfgang Glas <wolfgang.glas@ev-i.at>
To: swsusp-devel@lists.sourceforge.net
Coming back to an earlier post, which states, that NVidia suspend/resume under
2.6.x could be resurrected, if drivers_suspend() and drivers_resume() in
swsusp.c are tuned in a way, that pm_send_all() is called, I want to direct
the following question to more eligible persons in this list:
I inspected NVidia's driver and I found out, that it's implemented as a
character device and hence does not implement the suspend/resume kernel
driver interface, which has been introduced in linux-2.6. But nevertheless
this driver has the ability to register its own power management handler
through pm_register(), an interface already present in linux-2.4 and still
used in some 20 drivers present in the linux-2.6.1 code base, most notable
some audio driver and some irda drivers.
Diving further into the code, I recognized, that the kernel function
ppm_send_all(), which calls all handlers registered through pm_register() is
never called inside of swsusp2.c
So, what I want to ask is, whether the pm_register/pm_send/pm_send_all
interface is simply deprecated and the NVidia driver (and other drivers,
which use pm_register) should be reeingineered in order to use the
resume/suspend interface of linux-2.6. Or should we try to modify swsusp2.c
in a way, that it additionally calls pm_send_all for these drivers?
TIA,
Wolfgang
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
swsusp-devel mailing list
swsusp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/swsusp-devel
-------------------------------------------------------
next reply other threads:[~2004-02-10 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 15:43 Michael Frank [this message]
2004-02-11 5:23 ` Fwd: [Swsusp-devel] Kernel 2.6 pm_send_all() issues Benjamin Herrenschmidt
2004-02-11 6:46 ` Stephen Hemminger
2004-02-12 18:49 ` Nils Rennebarth
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=200402102343.06896.mhf@linuxmail.org \
--to=mhf@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swsusp-devel@lists.sourceforge.net \
--cc=wolfgang.glas@ev-i.at \
/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