All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tommaso Merciai <tommaso.merciai@amarulasolutions.com>
To: unlisted-recipients:; (no To-header on input)
Cc: tommaso.merciai@amarulasolutions.com,
	linuxfancy@googlegroups.com, linux-amarula@amarulasolutions.com,
	michael@amarulasolutions.com,
	Shunqian Zheng <zhengsq@rock-chips.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/4] media: i2c: ov5695: use regulator_bulk_enable/regulator_bulk disable instead of for loop
Date: Thu, 19 May 2022 09:51:14 +0200	[thread overview]
Message-ID: <20220519075117.1003520-2-tommaso.merciai@amarulasolutions.com> (raw)
In-Reply-To: <20220519075117.1003520-1-tommaso.merciai@amarulasolutions.com>

Enable regulator using regulator_bulk_enable/regulatore_bulk_disable
function in __ov5695_power_on/__ov5695_power_off function instead of for loop.
This reduce code size and make things more clear

Signed-off-by: Tommaso Merciai <tommaso.merciai@amarulasolutions.com>
Co-Developed-by: Michael Trimarchi <michael@amarulasolutions.com>
---
 drivers/media/i2c/ov5695.c | 25 +++++++------------------
 1 file changed, 7 insertions(+), 18 deletions(-)

diff --git a/drivers/media/i2c/ov5695.c b/drivers/media/i2c/ov5695.c
index 439385938a51..880b586e55fe 100644
--- a/drivers/media/i2c/ov5695.c
+++ b/drivers/media/i2c/ov5695.c
@@ -972,7 +972,7 @@ static int ov5695_s_stream(struct v4l2_subdev *sd, int on)
 
 static int __ov5695_power_on(struct ov5695 *ov5695)
 {
-	int i, ret;
+	int ret;
 	struct device *dev = &ov5695->client->dev;
 
 	ret = clk_prepare_enable(ov5695->xvclk);
@@ -987,13 +987,10 @@ static int __ov5695_power_on(struct ov5695 *ov5695)
 	 * The hardware requires the regulators to be powered on in order,
 	 * so enable them one by one.
 	 */
-	for (i = 0; i < OV5695_NUM_SUPPLIES; i++) {
-		ret = regulator_enable(ov5695->supplies[i].consumer);
-		if (ret) {
-			dev_err(dev, "Failed to enable %s: %d\n",
-				ov5695->supplies[i].supply, ret);
-			goto disable_reg_clk;
-		}
+	ret = regulator_bulk_enable(ARRAY_SIZE(ov5695->supplies), ov5695->supplies);
+	if (ret) {
+		dev_err(dev, "Failed to enable regulators %d\n", ret);
+		goto disable_reg_clk;
 	}
 
 	gpiod_set_value_cansleep(ov5695->reset_gpio, 0);
@@ -1003,8 +1000,7 @@ static int __ov5695_power_on(struct ov5695 *ov5695)
 	return 0;
 
 disable_reg_clk:
-	for (--i; i >= 0; i--)
-		regulator_disable(ov5695->supplies[i].consumer);
+	regulator_bulk_disable(ARRAY_SIZE(ov5695->supplies), ov5695->supplies);
 	clk_disable_unprepare(ov5695->xvclk);
 
 	return ret;
@@ -1012,8 +1008,6 @@ static int __ov5695_power_on(struct ov5695 *ov5695)
 
 static void __ov5695_power_off(struct ov5695 *ov5695)
 {
-	struct device *dev = &ov5695->client->dev;
-	int i, ret;
 
 	clk_disable_unprepare(ov5695->xvclk);
 	gpiod_set_value_cansleep(ov5695->reset_gpio, 1);
@@ -1022,12 +1016,7 @@ static void __ov5695_power_off(struct ov5695 *ov5695)
 	 * The hardware requires the regulators to be powered off in order,
 	 * so disable them one by one.
 	 */
-	for (i = OV5695_NUM_SUPPLIES - 1; i >= 0; i--) {
-		ret = regulator_disable(ov5695->supplies[i].consumer);
-		if (ret)
-			dev_err(dev, "Failed to disable %s: %d\n",
-				ov5695->supplies[i].supply, ret);
-	}
+	regulator_bulk_disable(ARRAY_SIZE(ov5695->supplies), ov5695->supplies);
 }
 
 static int __maybe_unused ov5695_runtime_resume(struct device *dev)
-- 
2.25.1


  reply	other threads:[~2022-05-19  7:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  7:51 [PATCH 0/4] arm64: dts: rockchip: px30: fix ov5695 camera probe Tommaso Merciai
2022-05-19  7:51 ` Tommaso Merciai [this message]
2022-05-31 13:14   ` [PATCH 1/4] media: i2c: ov5695: use regulator_bulk_enable/regulator_bulk disable instead of for loop Jacopo Mondi
2022-05-31 15:40     ` Tommaso Merciai
2022-05-31 15:50       ` Michael Nazzareno Trimarchi
2022-06-01  8:11         ` Jacopo Mondi
2022-06-01  8:39           ` Michael Nazzareno Trimarchi
2022-06-02  5:57             ` Michael Nazzareno Trimarchi
2022-06-09 10:11               ` Tommaso Merciai
2022-05-19  7:51 ` [PATCH 2/4] arm64: dts: rockchip: px30: max drive-strength for cif_clkout_m0 Tommaso Merciai
2022-05-19  7:51   ` Tommaso Merciai
2022-05-19  7:51   ` Tommaso Merciai
2022-05-23  8:17   ` Michael Nazzareno Trimarchi
2022-05-23  8:17     ` Michael Nazzareno Trimarchi
2022-05-23  8:17     ` Michael Nazzareno Trimarchi
2022-05-19  7:51 ` [PATCH 3/4] arm64: dts: rockchip: px30: add mux for mipi-pdn pad Tommaso Merciai
2022-05-19  7:51   ` Tommaso Merciai
2022-05-19  7:51   ` Tommaso Merciai
2022-05-23  8:18   ` Michael Nazzareno Trimarchi
2022-05-23  8:18     ` Michael Nazzareno Trimarchi
2022-05-23  8:18     ` Michael Nazzareno Trimarchi
2022-05-19  7:51 ` [PATCH 4/4] arm64: dts: rockchip: px30: use rk gpio naming convention into reset-gpios Tommaso Merciai
2022-05-19  7:51   ` Tommaso Merciai
2022-05-19  7:51   ` Tommaso Merciai
2022-05-23  8:16   ` Michael Nazzareno Trimarchi
2022-05-23  8:16     ` Michael Nazzareno Trimarchi
2022-05-23  8:16     ` Michael Nazzareno Trimarchi

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=20220519075117.1003520-2-tommaso.merciai@amarulasolutions.com \
    --to=tommaso.merciai@amarulasolutions.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linuxfancy@googlegroups.com \
    --cc=mchehab@kernel.org \
    --cc=michael@amarulasolutions.com \
    --cc=zhengsq@rock-chips.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.