From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 5/5] regulator: map consumer regulator based on device tree
Date: Thu, 13 Oct 2011 12:46:07 -0600 [thread overview]
Message-ID: <20111013184607.GQ18574@ponder.secretlab.ca> (raw)
In-Reply-To: <CACYZBRFmLEY_f1UwJa5U9uj8+NVA-WfUVkiuW1yKrpwnrA_00A@mail.gmail.com>
On Tue, Oct 11, 2011 at 12:38:53PM +0530, Nayak, Rajendra wrote:
> >
> >> + ? ? if (supply) {
> >> + ? ? ? ? ? ? struct regulator_dev *r;
> >> + ? ? ? ? ? ? struct device_node *node;
> >> +
> >> + ? ? ? ? ? ? /* first do a dt based lookup */
> >> + ? ? ? ? ? ? if (dev) {
> >> + ? ? ? ? ? ? ? ? ? ? node = of_get_regulator(dev, supply);
> >> + ? ? ? ? ? ? ? ? ? ? if (node)
> >> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? list_for_each_entry(r, ®ulator_list, list)
> >> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? if (node == r->dev.parent->of_node)
> >> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? goto found;
> >> ? ? ? ? ? ? ? }
> >>
> >> - ? ? ? ? ? ? if (!found) {
> >> - ? ? ? ? ? ? ? ? ? ? dev_err(dev, "Failed to find supply %s\n",
> >> - ? ? ? ? ? ? ? ? ? ? ? ? ? ? init_data->supply_regulator);
> >> - ? ? ? ? ? ? ? ? ? ? ret = -ENODEV;
> >> - ? ? ? ? ? ? ? ? ? ? goto scrub;
> >> - ? ? ? ? ? ? }
> >> + ? ? ? ? ? ? /* next try doing it non-dt way */
> >> + ? ? ? ? ? ? list_for_each_entry(r, ®ulator_list, list)
> >> + ? ? ? ? ? ? ? ? ? ? if (strcmp(rdev_get_name(r), supply) == 0)
> >> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? goto found;
> >>
> >> + ? ? ? ? ? ? dev_err(dev, "Failed to find supply %s\n", supply);
> >> + ? ? ? ? ? ? ret = -ENODEV;
> >> + ? ? ? ? ? ? goto scrub;
> >> +
> >> +found:
> >
> > This is all getting *really* complicated and illegible. ?I'm not sure
> > what the best way to structure is but erroring out early looks useful.
> >
>
> How about this updated patch?
>
> From f4c7d2b283740382c272c7971665375067d26dbe Mon Sep 17 00:00:00 2001
> From: Rajendra Nayak <rnayak@ti.com>
> Date: Thu, 22 Sep 2011 17:51:10 +0530
> Subject: [PATCH 5/5] regulator: map consumer regulator based on device tree
>
> Device nodes in DT can associate themselves with one or more
> regulators/supply by providing a list of phandles (to regulator nodes)
> and corresponding supply names.
>
> For Example:
> devicenode: node at 0x0 {
> ...
> ...
> vmmc-supply = <®ulator1>;
> vpll-supply = <®ulator1>;
> };
>
> The driver would then do a regulator_get(dev, "vmmc"); to get
> regulator1 and do a regulator_get(dev, "vpll"); to get
> regulator2.
>
> of_get_regulator() extracts the regulator node for a given
> device, based on the supply name.
>
> Use it to look up the regulator for a given consumer from device tree, during
> a regulator_get(). If not found fallback and lookup through
> the regulator_map_list instead.
>
> Also, since the regulator dt nodes can use the same binding to
> associate with a parent regulator/supply, allow the drivers to
> specify a supply_name, which can then be used to lookup dt
> to find the parent phandle.
>
> Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Acked-by: Grant Likely <grant.likely@secretlab.ca>
> ---
> drivers/regulator/core.c | 91 +++++++++++++++++++++++++++++++------
> include/linux/regulator/driver.h | 2 +
> 2 files changed, 78 insertions(+), 15 deletions(-)
>
> Index: linux/drivers/regulator/core.c
> ===================================================================
> --- linux.orig/drivers/regulator/core.c 2011-10-11 11:43:27.944140106 +0530
> +++ linux/drivers/regulator/core.c 2011-10-11 12:25:53.540418748 +0530
> @@ -25,9 +25,11 @@
> #include <linux/mutex.h>
> #include <linux/suspend.h>
> #include <linux/delay.h>
> +#include <linux/of.h>
> #include <linux/regulator/consumer.h>
> #include <linux/regulator/driver.h>
> #include <linux/regulator/machine.h>
> +#include <linux/regulator/of_regulator.h>
>
> #define CREATE_TRACE_POINTS
> #include <trace/events/regulator.h>
> @@ -131,6 +133,33 @@
> return NULL;
> }
>
> +/**
> + * of_get_regulator - get a regulator device node based on supply name
> + * @dev: Device pointer for the consumer (of regulator) device
> + * @supply: regulator supply name
> + *
> + * Extract the regulator device node corresponding to the supply name.
> + * retruns the device node corresponding to the regulator if found, else
> + * returns NULL.
> + */
> +static struct device_node *of_get_regulator(struct device *dev, const
> char *supply)
> +{
> + struct device_node *regnode = NULL;
> + char prop_name[32]; /* 32 is max size of property name */
> +
> + dev_dbg(dev, "Looking up %s-supply from device tree\n", supply);
> +
> + snprintf(prop_name, 32, "%s-supply", supply);
> + regnode = of_parse_phandle(dev->of_node, prop_name, 0);
> +
> + if (!regnode) {
> + pr_warn("%s: %s property in node %s references invalid phandle",
> + __func__, prop_name, dev->of_node->full_name);
> + return NULL;
> + }
> + return regnode;
> +}
> +
> /* Platform voltage constraint check */
> static int regulator_check_voltage(struct regulator_dev *rdev,
> int *min_uV, int *max_uV)
> @@ -1147,6 +1176,28 @@
> return rdev->desc->ops->enable_time(rdev);
> }
>
> +static struct regulator_dev *regulator_dev_lookup(struct device *dev,
> + const char *supply)
> +{
> + struct regulator_dev *r;
> + struct device_node *node;
> +
> + /* first do a dt based lookup */
> + if (dev && dev->of_node)
> + node = of_get_regulator(dev, supply);
> + if (node)
> + list_for_each_entry(r, ®ulator_list, list)
> + if (node == r->dev.parent->of_node)
> + return r;
> +
> + /* if not found, try doing it non-dt way */
> + list_for_each_entry(r, ®ulator_list, list)
> + if (strcmp(rdev_get_name(r), supply) == 0)
> + return r;
> +
> + return NULL;
> +}
> +
> /* Internal regulator request function */
> static struct regulator *_regulator_get(struct device *dev, const char *id,
> int exclusive)
> @@ -1155,6 +1206,7 @@
> struct regulator_map *map;
> struct regulator *regulator = ERR_PTR(-ENODEV);
> const char *devname = NULL;
> + struct device_node *node;
> int ret;
>
> if (id == NULL) {
> @@ -1167,6 +1219,10 @@
>
> mutex_lock(®ulator_list_mutex);
>
> + rdev = regulator_dev_lookup(dev, id);
> + if (rdev)
> + goto found;
> +
> list_for_each_entry(map, ®ulator_map_list, list) {
> /* If the mapping has a device set up it must match */
> if (map->dev_name &&
> @@ -2579,6 +2635,7 @@
> static atomic_t regulator_no = ATOMIC_INIT(0);
> struct regulator_dev *rdev;
> int ret, i;
> + const char *supply;
>
> if (regulator_desc == NULL)
> return ERR_PTR(-EINVAL);
> @@ -2653,21 +2710,18 @@
> if (ret < 0)
> goto scrub;
>
> - if (init_data->supply_regulator) {
> + if (init_data->supply_regulator)
> + supply = init_data->supply_regulator;
> + else if (regulator_desc->supply_name);
> + supply = regulator_desc->supply_name;
> +
> + if (supply) {
> struct regulator_dev *r;
> - int found = 0;
>
> - list_for_each_entry(r, ®ulator_list, list) {
> - if (strcmp(rdev_get_name(r),
> - init_data->supply_regulator) == 0) {
> - found = 1;
> - break;
> - }
> - }
> + r = regulator_dev_lookup(dev, supply);
>
> - if (!found) {
> - dev_err(dev, "Failed to find supply %s\n",
> - init_data->supply_regulator);
> + if (!r) {
> + dev_err(dev, "Failed to find supply %s\n", supply);
> ret = -ENODEV;
> goto scrub;
> }
> Index: linux/include/linux/regulator/driver.h
> ===================================================================
> --- linux.orig/include/linux/regulator/driver.h 2011-10-11
> 11:43:27.936139476 +0530
> +++ linux/include/linux/regulator/driver.h 2011-10-11 11:43:43.485351850 +0530
> @@ -153,6 +153,7 @@
> * this type.
> *
> * @name: Identifying name for the regulator.
> + * @supply_name: Identifying the regulator supply
> * @id: Numerical identifier for the regulator.
> * @n_voltages: Number of selectors available for ops.list_voltage().
> * @ops: Regulator operations table.
> @@ -162,6 +163,7 @@
> */
> struct regulator_desc {
> const char *name;
> + const char *supply_name;
> int id;
> unsigned n_voltages;
> struct regulator_ops *ops;
next prev parent reply other threads:[~2011-10-13 18:46 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 16:19 [PATCH v2 0/5] Device tree support for regulators Rajendra Nayak
2011-10-10 16:19 ` [PATCH v2 1/5] regulator: twl: Remove hardcoded board constraints from driver Rajendra Nayak
2011-10-10 16:25 ` Mark Brown
2011-10-10 16:34 ` Rajendra Nayak
2011-10-10 16:19 ` [PATCH v2 2/5] dt: add empty dt helpers for non-dt build Rajendra Nayak
2011-10-13 18:32 ` Grant Likely
2011-10-10 16:19 ` [PATCH v2 3/5] regulator: helper routine to extract regulator_init_data Rajendra Nayak
2011-10-10 17:22 ` Mark Brown
2011-10-11 5:59 ` Rajendra Nayak
2011-10-13 18:38 ` Grant Likely
2011-10-13 22:12 ` Mark Brown
2011-10-13 18:40 ` Grant Likely
2011-10-16 14:55 ` Shawn Guo
2011-10-17 4:17 ` Rajendra Nayak
2011-10-18 11:58 ` Shawn Guo
2011-10-18 16:00 ` Mark Brown
2011-10-19 5:33 ` Shawn Guo
2011-10-19 14:47 ` Mark Brown
2011-10-19 15:04 ` Shawn Guo
2011-10-19 15:10 ` Mark Brown
2011-10-20 3:42 ` Rajendra Nayak
2011-10-20 9:41 ` Mark Brown
2011-10-20 12:10 ` Rajendra Nayak
2011-10-20 16:27 ` Tony Lindgren
2011-10-20 16:40 ` Mark Brown
2011-10-20 17:05 ` Tony Lindgren
2011-10-20 17:22 ` Tony Lindgren
2011-10-20 19:57 ` Mark Brown
2011-10-20 20:10 ` Tony Lindgren
2011-10-20 21:42 ` Mark Brown
2011-10-20 22:09 ` Tony Lindgren
2011-10-24 9:07 ` Grant Likely
2011-10-20 19:56 ` Mark Brown
2011-10-18 13:20 ` Shawn Guo
2011-10-19 11:35 ` Rajendra Nayak
2011-10-19 14:42 ` Shawn Guo
2011-10-19 14:50 ` Mark Brown
2011-10-20 5:18 ` Rajendra Nayak
2011-10-20 6:14 ` Shawn Guo
2011-10-20 12:09 ` Rajendra Nayak
2011-10-21 8:23 ` Shawn Guo
2011-10-21 8:41 ` Rajendra Nayak
2011-10-21 11:58 ` Shawn Guo
2011-10-24 6:02 ` Rajendra Nayak
2011-10-24 7:34 ` Mark Brown
2011-10-24 8:17 ` Grant Likely
2011-10-24 8:53 ` Rajendra Nayak
2011-10-24 9:19 ` Mark Brown
2011-10-24 10:05 ` Rajendra Nayak
2011-10-24 9:23 ` Shawn Guo
2011-10-24 9:02 ` Shawn Guo
2011-10-24 8:56 ` Rajendra Nayak
2011-10-24 9:11 ` Shawn Guo
2011-10-24 9:13 ` Rajendra Nayak
2011-10-24 13:47 ` Shawn Guo
2011-10-25 6:00 ` Rajendra Nayak
2011-10-25 6:26 ` Rajendra Nayak
2011-10-25 6:52 ` Shawn Guo
2011-10-25 6:56 ` Rajendra Nayak
2011-10-25 7:20 ` Shawn Guo
2011-10-25 7:13 ` Rajendra Nayak
2011-10-25 7:42 ` Shawn Guo
2011-10-24 11:35 ` Grant Likely
2011-10-24 9:24 ` Grant Likely
2011-10-24 9:39 ` Mark Brown
2011-10-24 13:04 ` Shawn Guo
2011-10-24 13:06 ` Mark Brown
2011-10-24 13:40 ` Shawn Guo
2011-10-24 13:49 ` Mark Brown
2011-10-24 14:47 ` Shawn Guo
2011-10-25 7:11 ` Mark Brown
2011-10-24 13:59 ` Grant Likely
2011-10-24 14:51 ` Shawn Guo
2011-10-24 14:56 ` Grant Likely
2011-10-24 15:51 ` Shawn Guo
2011-10-24 22:21 ` Grant Likely
2011-10-25 6:10 ` Rajendra Nayak
2011-10-25 7:08 ` Shawn Guo
2011-10-25 7:01 ` Rajendra Nayak
2011-10-25 7:28 ` Shawn Guo
2011-10-10 16:19 ` [PATCH v2 4/5] regulator: adapt fixed regulator driver to dt Rajendra Nayak
2011-10-13 18:43 ` Grant Likely
2011-10-10 16:19 ` [PATCH v2 5/5] regulator: map consumer regulator based on device tree Rajendra Nayak
2011-10-10 17:35 ` Mark Brown
2011-10-11 5:49 ` Rajendra Nayak
2011-10-11 7:08 ` Nayak, Rajendra
2011-10-13 16:52 ` Mark Brown
2011-10-13 18:46 ` Grant Likely [this message]
2011-10-18 13:33 ` Shawn Guo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111013184607.GQ18574@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).