devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
	 Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Rishi Gupta <gupt21@gmail.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	 Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	 Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: [PATCH 4/7] iio: light: veml6030: make use of regmap_set_bits()
Date: Fri, 13 Sep 2024 15:18:59 +0200	[thread overview]
Message-ID: <20240913-veml6035-v1-4-0b09c0c90418@gmail.com> (raw)
In-Reply-To: <20240913-veml6035-v1-0-0b09c0c90418@gmail.com>

Instead of using regmap_update_bits() and passing val = 1, use
regmap_set_bits().

Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
---
 drivers/iio/light/veml6030.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/iio/light/veml6030.c b/drivers/iio/light/veml6030.c
index df2ba3078b91..5d4c2e35b987 100644
--- a/drivers/iio/light/veml6030.c
+++ b/drivers/iio/light/veml6030.c
@@ -149,8 +149,8 @@ static int veml6030_als_pwr_on(struct veml6030_data *data)
 
 static int veml6030_als_shut_down(struct veml6030_data *data)
 {
-	return regmap_update_bits(data->regmap, VEML6030_REG_ALS_CONF,
-				 VEML6030_ALS_SD, 1);
+	return regmap_set_bits(data->regmap, VEML6030_REG_ALS_CONF,
+				 VEML6030_ALS_SD);
 }
 
 static void veml6030_als_shut_down_action(void *data)

-- 
2.43.0


  parent reply	other threads:[~2024-09-13 13:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13 13:18 [PATCH 0/7] iio: light: veml6030: fix issues and add support for veml6035 Javier Carrasco
2024-09-13 13:18 ` [PATCH 1/7] dt-bindings: iio: light: veml6030: rename to add manufacturer Javier Carrasco
2024-09-13 16:53   ` Conor Dooley
2024-09-14 14:52     ` Jonathan Cameron
2024-09-13 13:18 ` [PATCH 2/7] dt-bindings: iio: light: veml6030: add veml6035 Javier Carrasco
2024-09-13 16:55   ` Conor Dooley
2024-09-13 13:18 ` [PATCH 3/7] iio: light: veml6030: fix IIO device retrieval from embedded device Javier Carrasco
2024-09-14 14:51   ` Jonathan Cameron
2024-09-13 13:18 ` Javier Carrasco [this message]
2024-09-14 14:54   ` [PATCH 4/7] iio: light: veml6030: make use of regmap_set_bits() Jonathan Cameron
2024-09-13 13:19 ` [PATCH 5/7] iio: light: veml6030: update sensor resolution Javier Carrasco
2024-09-14 14:57   ` Jonathan Cameron
2024-09-15  8:31     ` Javier Carrasco
2024-09-28 14:38       ` Jonathan Cameron
2024-09-13 13:19 ` [PATCH 6/7] iio: light: veml6030: add set up delay after any power on sequence Javier Carrasco
2024-09-14 14:59   ` Jonathan Cameron
2024-09-13 13:19 ` [PATCH 7/7] iio: light: veml6030: add support for veml6035 Javier Carrasco
2024-09-14 16:03   ` Jonathan Cameron
2024-09-16  6:19     ` Javier Carrasco
2024-09-28 14:40       ` Jonathan Cameron

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=20240913-veml6035-v1-4-0b09c0c90418@gmail.com \
    --to=javier.carrasco.cruz@gmail.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gupt21@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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).