Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753169Ab2BPPNd (ORCPT ); Thu, 16 Feb 2012 10:13:33 -0500 Received: from iolanthe.rowland.org ([192.131.102.54]:43264 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753163Ab2BPPNb (ORCPT ); Thu, 16 Feb 2012 10:13:31 -0500 Date: Thu, 16 Feb 2012 10:13:30 -0500 (EST) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Zhang Rui cc: "Rafael J. Wysocki" , Lin Ming , Jeff Garzik , Tejun Heo , Len Brown , , , , Subject: Re: [RFC PATCH 2/6] ACPI: Reference devices in ACPI Power Resource In-Reply-To: <1329376686.28581.15.camel@rui.sh.intel.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1218 Lines: 27 On Thu, 16 Feb 2012, Zhang Rui wrote: > > I'm not exactly sure what you're trying to achieve and what you mean by > > "resume a device directly"? Do you want to run the device's resume > > callback at the time when another device is being resumed? > > > I mean, wakeup event is sent to ATA port, but our goal is to resume > ZPODD after receiving this wakeup event. > Ideally, it is ACPI that resumes ATA port. And then, the ATA port > runtime resumes ZPODD. But this does not look good to runtime resume a > child device in the parent's .runtime_resume callback. > So I introduced these two APIs so that an runtime_resume request can be > sent to ZPODD directly and the runtime PM core can resume all the > parents of ZPODD automatically. It's not clear what you're trying to achieve. Do you basically want the ZPODD always to be suspended and resumed along with the ATA port, or should it be possible to suspend the ZPODD while the port remains running? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/