[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1419614799-5770-1-git-send-email-gregory.clement@free-electrons.com>
Date: Fri, 26 Dec 2014 18:26:37 +0100
From: Gregory CLEMENT <gregory.clement@...e-electrons.com>
To: Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org
Cc: Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
Boris BREZILLON <boris.brezillon@...e-electrons.com>,
Lior Amsalem <alior@...vell.com>,
Tawfik Bayouk <tawfik@...vell.com>,
Nadav Haklai <nadavh@...vell.com>, linux-ide@...r.kernel.org,
Gregory CLEMENT <gregory.clement@...e-electrons.com>
Subject:
Subject: [PATCH 0/2] regulator: Add the device tree version to the regulator_get family
Hi,
Currently it is not possible to associate a regulator to a child node
which is not a device. The several ports of an ahci controller are
represented as subnodes but they are not created as devices. In order
to be able to associate each port with a regulator the framework API
needs to be extended.
The second patch adds the device tree version (of_) for each member of
the regulator_get family: normal, exclusive, optional and all of the
manageable version.The of_regulator_get* functions allow using a
device node to get the regulator instead using the device object.
The first patch is not related to the second one, but it is little
improvement.
Gregory
Gregory CLEMENT (2):
regulator: core: Add a sanity check on the regulator_ enable/disable
functions
regulator: core: Add the device tree version to the regulator_get
family
drivers/regulator/core.c | 127 +++++++++++++++++++++++++++++++++----
drivers/regulator/devres.c | 70 ++++++++++++++++++--
include/linux/regulator/consumer.h | 20 ++++++
3 files changed, 198 insertions(+), 19 deletions(-)
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists