netdev - Re: [linux-pm] [Ipw2100-devel] [RFC] Runtime power management on ipw2100

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200702191308.49797.david-b@pacbell.net>
Date:	Mon, 19 Feb 2007 13:08:49 -0800
From:	David Brownell <david-b@...bell.net>
To:	linux-pm@...ts.osdl.org
Cc:	Zhu Yi <yi.zhu@...el.com>, Matthew Garrett <mjg59@...f.ucam.org>,
	ipw2100-devel@...ts.sourceforge.net, netdev@...r.kernel.org
Subject: Re: [linux-pm] [Ipw2100-devel] [RFC] Runtime power management on ipw2100

On Thursday 08 February 2007 1:01 am, Zhu Yi wrote:

> A generic requirement for dynamic power management is the hardware
> resource should not be touched when you put it in a low power state.

That is in no way a "generic" requirement.  It might apply specifically
to one ipw2100 low power state ... but "in general" devices may support
more than one low power state, with different levels of functionality.
Not all of those levels necessarily disallow touching the hardware.

> 	But I think
> freeing the irq handler before suspend should be the right way to go.

Some folk like that model a lot for shared IRQs.  It shouldn't
matter for non-sharable ones.

- Dave
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html