From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id AF927B7BAA for ; Fri, 6 Nov 2009 07:24:52 +1100 (EST) Received: from az33smr01.freescale.net (az33smr01.freescale.net [10.64.34.199]) by az33egw02.freescale.net (8.14.3/az33egw02) with ESMTP id nA5KOn7F022617 for ; Thu, 5 Nov 2009 13:24:49 -0700 (MST) Received: from az33exm25.fsl.freescale.net (az33exm25.am.freescale.net [10.64.32.16]) by az33smr01.freescale.net (8.13.1/8.13.0) with ESMTP id nA5KS0Rm005180 for ; Thu, 5 Nov 2009 14:28:00 -0600 (CST) Message-ID: <4AF334AB.1030401@freescale.com> Date: Thu, 05 Nov 2009 14:25:15 -0600 From: Scott Wood MIME-Version: 1.0 To: avorontsov@ru.mvista.com Subject: Re: [PATCH 1/3] powerpc/83xx/suspend: Clear deep_sleeping after devices resume References: <20090923190041.GA18944@oksana.dev.rtsoft.ru> <20090923190113.GA19932@oksana.dev.rtsoft.ru> <043A102D-9F70-4287-B34E-17FF9AE90EE1@kernel.crashing.org> <4AF30406.3080101@freescale.com> <2F8E2E66-8398-4ACD-9697-6C2AB6E39CD3@kernel.crashing.org> <4AF32C0B.4010109@freescale.com> <7A8DBFC0-69D9-406B-B1AC-3EAC8EE26C58@kernel.crashing.org> <4AF32F82.8040801@freescale.com> <20091105200931.GA30577@oksana.dev.rtsoft.ru> In-Reply-To: <20091105200931.GA30577@oksana.dev.rtsoft.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Cc: linux-ppc list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Anton Vorontsov wrote: > On Thu, Nov 05, 2009 at 02:03:14PM -0600, Scott Wood wrote: >> Kumar Gala wrote: >>> On Nov 5, 2009, at 1:48 PM, Scott Wood wrote: >>>> As for patch 3, Ben objected to the sleep-nexus stuff on IRC. >>> Is sleep-nexus new? I thought we've had that for a bit. >> It's been around in a few dts files, but as was noted, nothing uses >> this stuff yet. > > So I should just drop the sleep-nexus changes? I can also > prepare a patch that removes sleep-nexus from 8313rdb.dts. > But how should we handle the sleep = <> properties then? We could still have some sort of nexus node that is off to the side (pointed to with sleep-parent) and not inserting itself into the hierarchy. Or, we could allow multiple nodes to refer to the same sleep ID, and use the ID rather than a node to tie things together. If we do that, we'll probably want a simple index rather than a set of bits in the sleep property, so it can correspond to some kernel object that has some bookeeping info. Perhaps we could tie into the clock bindings that were discussed on devtree-discuss in August. -Scott