From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] commands: regulator: add support for enabling/disabling regulators
Date: Wed, 5 Jan 2022 10:14:24 +0100 [thread overview]
Message-ID: <20220105091423.GQ6003@pengutronix.de> (raw)
In-Reply-To: <20220103120336.1729791-1-a.fatoum@pengutronix.de>
On Mon, Jan 03, 2022 at 01:03:36PM +0100, Ahmad Fatoum wrote:
> For testing regulator drivers, it can be handy to enable/disable them
> from the shell prompt. Extend the regulator command to support this.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> commands/regulator.c | 38 +++++++++++++++++++++++++++++++++++---
> drivers/regulator/core.c | 8 ++++++++
> include/regulator.h | 1 +
> 3 files changed, 44 insertions(+), 3 deletions(-)
>
> diff --git a/commands/regulator.c b/commands/regulator.c
> index 3e2595f8bfc1..e6b2f4852db4 100644
> --- a/commands/regulator.c
> +++ b/commands/regulator.c
> @@ -6,16 +6,48 @@
> #include <common.h>
> #include <command.h>
> #include <regulator.h>
> +#include <getopt.h>
>
> static int do_regulator(int argc, char *argv[])
> {
> - regulators_print();
> + struct regulator *chosen;
> + int opt, ret;
> +
> + while ((opt = getopt(argc, argv, "e:d:")) > 0) {
> + switch (opt) {
> + case 'e':
> + case 'd':
> + chosen = regulator_get_name(optarg);
> + if (IS_ERR_OR_NULL(chosen)) {
> + printf("regulator not found\n");
> + return COMMAND_ERROR;
> + }
> +
> + ret = opt == 'e' ? regulator_enable(chosen)
> + : regulator_disable(chosen);
> + regulator_put(chosen);
> + return ret;
The barebox regulator core distinguishes between struct regulator and
struct regulator_internal. regulator_internal represents the physical
regulator whereas regulator is allocated for each consumer. If the
regulator core were a bit more sophisticated then a regulator would
have it's own enable count and you would be warned when a regulators
enable count goes below zero.
I agree that controlling regulators on the command line would be useful,
but I also don't want to block extending the regulator core in such a
way.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2022-01-05 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 12:03 Ahmad Fatoum
2022-01-05 9:14 ` Sascha Hauer [this message]
2022-01-05 9:21 ` Ahmad Fatoum
2023-11-22 18:39 ` Ahmad Fatoum
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=20220105091423.GQ6003@pengutronix.de \
--to=sha@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@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