[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1202161010500.1268-100000@iolanthe.rowland.org>
Date: Thu, 16 Feb 2012 10:13:30 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: Zhang Rui <rui.zhang@...el.com>
cc: "Rafael J. Wysocki" <rjw@...k.pl>, Lin Ming <ming.m.lin@...el.com>,
Jeff Garzik <jgarzik@...ox.com>, Tejun Heo <tj@...nel.org>,
Len Brown <lenb@...nel.org>, <linux-kernel@...r.kernel.org>,
<linux-ide@...r.kernel.org>, <linux-scsi@...r.kernel.org>,
<linux-pm@...r.kernel.org>
Subject: Re: [RFC PATCH 2/6] ACPI: Reference devices in ACPI Power Resource
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists