On Fri, Aug 24, 2012 at 01:16:34PM -0700, Tony Lindgren wrote:
* Mark Brown broo...@opensource.wolfsonmicro.com [120821 11:09]:
The board shouldn't have to define the regulators, the regulator driver
really ought to be able to figure out that they're there by itself if
there's no
* Mark Brown broo...@opensource.wolfsonmicro.com [120821 11:09]:
On Tue, Aug 21, 2012 at 12:05:15PM -0600, Stephen Warren wrote:
On 08/21/2012 10:38 AM, Mark Brown wrote:
This isn't the general view for the regualtor API - we generally
want all regulators to be registered in order to
Add device tree data for tps65910 regulator by adding all tps65910
regulator nodes. Regulator is initialized based on compatiable
name provided in tps65910 DT file.
All tps65910 PMIC regulator device tree nodes are placed in a
seperate device tree include file (tps65910.dtsi). This patch
was
On 08/21/2012 05:17 AM, AnilKumar Ch wrote:
Add device tree data for tps65910 regulator by adding all tps65910
regulator nodes. Regulator is initialized based on compatiable
name provided in tps65910 DT file.
All tps65910 PMIC regulator device tree nodes are placed in a
seperate device tree
On Tue, Aug 21, 2012 at 09:48:21AM -0600, Stephen Warren wrote:
This .dtsi file adds a node for every single regulator within the
TPS65910, which in turn means that of_regulator_match() will find a node
for every regulator, and in turn every regulator will be registered. On
some boards, not
On 08/21/2012 10:38 AM, Mark Brown wrote:
On Tue, Aug 21, 2012 at 09:48:21AM -0600, Stephen Warren wrote:
This .dtsi file adds a node for every single regulator within
the TPS65910, which in turn means that of_regulator_match() will
find a node for every regulator, and in turn every
On Tue, Aug 21, 2012 at 12:05:15PM -0600, Stephen Warren wrote:
On 08/21/2012 10:38 AM, Mark Brown wrote:
This isn't the general view for the regualtor API - we generally
want all regulators to be registered in order to allow us to see
what's going on with things even if we've not figured
