From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754177Ab2HANzf (ORCPT ); Wed, 1 Aug 2012 09:55:35 -0400 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:51998 "EHLO opensource.wolfsonmicro.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753480Ab2HANzd (ORCPT ); Wed, 1 Aug 2012 09:55:33 -0400 Date: Wed, 1 Aug 2012 14:55:31 +0100 From: Mark Brown To: Thierry Reding Cc: Alex Courbot , Stephen Warren , Stephen Warren , Simon Glass , Grant Likely , Rob Herring , Greg Kroah-Hartman , Arnd Bergmann , "linux-tegra@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-fbdev@vger.kernel.org" , "devicetree-discuss@lists.ozlabs.org" Subject: Re: [RFC][PATCH v3 1/3] runtime interpreted power sequences Message-ID: <20120801135531.GW11892@opensource.wolfsonmicro.com> References: <5017B434.2010706@nvidia.com> <20120731105640.GD16155@avionic-0098.adnet.avionic-design.de> <20120731141328.GS4468@opensource.wolfsonmicro.com> <20120731142216.GA19591@avionic-0098.adnet.avionic-design.de> <20120731142607.GV4468@opensource.wolfsonmicro.com> <20120731143235.GA21126@avionic-0098.adnet.avionic-design.de> <20120731153941.GF4468@opensource.wolfsonmicro.com> <20120801074113.GF29673@avionic-0098.adnet.avionic-design.de> <20120801132651.GU11892@opensource.wolfsonmicro.com> <20120801133814.GA19771@avionic-0098.adnet.avionic-design.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120801133814.GA19771@avionic-0098.adnet.avionic-design.de> X-Cookie: Caution: Keep out of reach of children. User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 01, 2012 at 03:38:14PM +0200, Thierry Reding wrote: > On Wed, Aug 01, 2012 at 02:26:51PM +0100, Mark Brown wrote: > > This is why __devinit data will only be discarded when this is not > > possible. > That's exactly my point. But I seem to have miserably failed to get that > across. =) We must be talking at cross purposes then. What I'm saying is that the framework shouldn't rely on platform data and should assume that the kernel might be configured so it can be discarded (by copying most likely).