From: Henry Chen <henryc.chen@mediatek.com>
To: Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Liam Girdwood <lgirdwood@gmail.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
Henry Chen <henryc.chen@mediatek.com>
Subject: [PATCH v2 2/3] regulator: of: Add support for parsing operation mode
Date: Mon, 23 May 2016 15:13:30 +0800 [thread overview]
Message-ID: <1463987611-32139-3-git-send-email-henryc.chen@mediatek.com> (raw)
In-Reply-To: <1463987611-32139-1-git-send-email-henryc.chen@mediatek.com>
Some regulators support their operating mode to be changed by consumers for
module specific purpose.
This patch adds support to parse those properties and fill the regulator
constraints so the regulator core can call the regualtor_set_mode to change
the modes.
Signed-off-by: Henry Chen <henryc.chen@mediatek.com>
---
drivers/regulator/of_regulator.c | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/drivers/regulator/of_regulator.c b/drivers/regulator/of_regulator.c
index 6b0aa80..7f8d82e 100644
--- a/drivers/regulator/of_regulator.c
+++ b/drivers/regulator/of_regulator.c
@@ -31,7 +31,7 @@ static void of_get_regulation_constraints(struct device_node *np,
struct regulation_constraints *constraints = &(*init_data)->constraints;
struct regulator_state *suspend_state;
struct device_node *suspend_np;
- int ret, i;
+ int ret, i, cnt;
u32 pval;
constraints->name = of_get_property(np, "regulator-name", NULL);
@@ -167,6 +167,19 @@ static void of_get_regulation_constraints(struct device_node *np,
suspend_state = NULL;
suspend_np = NULL;
}
+ cnt = of_property_count_elems_of_size(np,
+ "regulator-supported-modes",
+ sizeof(u32));
+ if (cnt > 0)
+ constraints->valid_ops_mask |= REGULATOR_CHANGE_MODE;
+
+ for (i = 0; i < cnt; i++) {
+ u32 mode;
+
+ of_property_read_u32_index(np, "regulator-supported-modes",
+ i, &mode);
+ constraints->valid_modes_mask |= (1 << mode);
+ }
}
/**
--
1.8.1.1.dirty
next prev parent reply other threads:[~2016-05-23 7:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 7:13 Add support for regulator operation mode of mt6397 Henry Chen
2016-05-23 7:13 ` [PATCH v2 1/3] regulator: DT: Add DT property for operation mode configuration Henry Chen
2016-05-23 10:47 ` Mark Rutland
2016-05-23 11:28 ` Mark Brown
2016-05-31 8:20 ` Fan Chen
2016-06-03 0:16 ` Mark Brown
2016-06-03 5:42 ` Fan Chen
2016-05-23 7:13 ` Henry Chen [this message]
2016-05-23 7:13 ` [PATCH v2 3/3] regulator: mt6397: Add buck change mode regulator interface for mt6397 Henry Chen
2016-05-23 11:29 ` Mark Brown
2016-05-23 17:50 ` Applied "regulator: mt6397: Add buck change mode regulator interface for mt6397" to the regulator tree Mark Brown
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=1463987611-32139-3-git-send-email-henryc.chen@mediatek.com \
--to=henryc.chen@mediatek.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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).