From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: [RFC][PATCH 0/14] PM / shmobile: Pass power domain information via DT (was: Re: [RFD] PM: Device tree representation of power domains) Date: Thu, 26 Jul 2012 23:34:11 +0200 Message-ID: <201207262334.11789.rjw@sisk.pl> References: <201207032302.17805.rjw@sisk.pl> <87vchb4ar8.fsf@ti.com> <20120726210952.GG4560@opensource.wolfsonmicro.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120726210952.GG4560@opensource.wolfsonmicro.com> Sender: linux-sh-owner@vger.kernel.org To: Mark Brown Cc: Kevin Hilman , Arnd Bergmann , devicetree-discuss@lists.ozlabs.org, Linux PM list , LKML , Matthew Garrett , Magnus Damm , Grant Likely , Linux-sh list , Benoit Cousson List-Id: devicetree@vger.kernel.org On Thursday, July 26, 2012, Mark Brown wrote: > On Wed, Jul 25, 2012 at 05:38:35PM -0700, Kevin Hilman wrote: > > > That being said, I'm not sure why ti,hwmods is being used as an example > > for powerdomains. hwmods describe the integration of SoC IP blocks > > (base addr, IRQ, DMA channel etc., which are being moved to DT) as well > > as a bunch of SoC specific PM register descriptions. This stuff is > > SoC-specific PM register layout, so being very SoC specific, it has the > > 'ti' prefix in the DT binding. > > I think the thing here is that one aspect of that SoC integration is > which power domain the blocks are in. Describing which power domain an > IP is in isn't a million miles away from describing which hwmod applies > to an IP. I agree.