lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 4 Jul 2012 12:56:37 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Linux PM list <linux-pm@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	Magnus Damm <magnus.damm@...il.com>,
	Arnd Bergmann <arnd@...db.de>,
	Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [RFD] PM: Device tree representation of power domains

On Tue, Jul 03, 2012 at 11:02:17PM +0200, Rafael J. Wysocki wrote:

> I actually don't have any ideas how to do that at the moment, but I wonder
> if anyone has already thought about it?

> For one, I don't think that representing a power domain as a platform device
> would be a good approach and I'm not sure how to represent the relationships
> between devices and the domains they belong to.

I guess the OMAP hwmod stuff is the closest thing we've got at the
minute (I don't recall seeing any other implementations in mainline) but
the hwmods themselves don't appear in the DTS right now.  They have a
ti,hwmods property on each device naming the hwmod it's in, something
like that seems like a reasonable approach, possibly a reference to
another DT node rather than or as well as a string?  That seems fairly
easy.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ