From: "Nuno Sá" <nuno.sa@analog.com>
To: Alexander Sarmanow <as@discnull.de>
Cc: Jonathan Cameron <jic23@kernel.org>,
David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>,
Parthiban Nallathambi <pn@denx.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] iio: light: vcnl4035: Fix reversed ALS mode bit
Date: Mon, 12 Oct 2026 16:51:05 +0100 [thread overview]
Message-ID: <as0B1EnPqfwRO1D-@nsa> (raw)
In-Reply-To: <20261012144315.1678195-1-as@discnull.de>
On Mon, Oct 12, 2026 at 04:43:15PM +0200, Alexander Sarmanow wrote:
> According to the datasheet (table 2) the ALS_SD bit behaves the opposite
> way the current ALS mode defines are set, writing 0 powers the sensor
> and writing 1 shuts it down.
>
> The current driver thinks the ALS is up while it's actually shut down
> and it's down when the systems powers it up.
>
> Fixes: 55707294c4eb ("iio: light: Add support for vishay vcnl4035")
> Cc: stable@vger.kernel.org
> Signed-off-by: Alexander Sarmanow <as@discnull.de>
> ---
Reviewed-by: Nuno Sá <nuno.sa@analog.com>
> Tested on a Raspberry Pi 3B+ with a VCNL4035 on I2C, running Raspberry
> Pi OS downstream kernel 6.18.50. Checked with i2cget that bit 0 of the
> config register 0x00 is 0 while PM runtime resume and 1 once it's
> runtime suspended. Also builds cleanly against iio/testing.
>
> drivers/iio/light/vcnl4035.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/light/vcnl4035.c b/drivers/iio/light/vcnl4035.c
> index ce1bd42b0c7c..f1cc75245001 100644
> --- a/drivers/iio/light/vcnl4035.c
> +++ b/drivers/iio/light/vcnl4035.c
> @@ -44,8 +44,8 @@
> #define VCNL4035_DEV_ID_MASK GENMASK(7, 0)
>
> /* Default values */
> -#define VCNL4035_MODE_ALS_ENABLE BIT(0)
> -#define VCNL4035_MODE_ALS_DISABLE 0x00
> +#define VCNL4035_MODE_ALS_ENABLE 0x00
> +#define VCNL4035_MODE_ALS_DISABLE BIT(0)
> #define VCNL4035_MODE_ALS_INT_ENABLE BIT(1)
> #define VCNL4035_MODE_ALS_INT_DISABLE 0
> #define VCNL4035_DEV_ID_VAL 0x80
>
> base-commit: a22dc7ebb21a6bd4c8b63bc2c1dd46a24945aae7
>
> Best regards,
> Alexander
> --
> 2.47.3
>
prev parent reply other threads:[~2026-10-12 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 14:43 Alexander Sarmanow
2026-10-12 15:51 ` Nuno Sá [this message]
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=as0B1EnPqfwRO1D-@nsa \
--to=nuno.sa@analog.com \
--cc=andy@kernel.org \
--cc=as@discnull.de \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pn@denx.de \
--cc=stable@vger.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
all inboxes | Powered by JetHome®