mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: Subhajit Ghosh <subhajit.ghosh@tweaklogic.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] iio: light: apds9306: fix max_scale_nano values
Date: Sat, 18 Jan 2025 12:24:55 +0000	[thread overview]
Message-ID: <20250118122455.54c1e96e@jic23-huawei> (raw)
In-Reply-To: <20250112-apds9306_nano_vals-v1-1-82fb145d0b16@gmail.com>

On Sun, 12 Jan 2025 01:08:11 +0100
Javier Carrasco <javier.carrasco.cruz@gmail.com> wrote:

> The two provided max_scale_nano values must be multiplied by 100 and 10
> respectively to achieve nano units. According to the comments:
> 
> Max scale for apds0306 is 16.326432 → the fractional part is 0.326432,
> which is 326432000 in NANO. The current value is 3264320.
> 
> Max scale for apds0306-065 is 14.09721 → the fractional part is 0.09712,
> which is 97120000 in NANO. The current value is 9712000.
> 
> Update max_scale_nano initialization to use the right NANO fractional
> parts.
> 
> Cc: stable@vger.kernel.org
> Fixes: 620d1e6c7a3f ("iio: light: Add support for APDS9306 Light Sensor")
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>

This just missed last pull request for this cycle.
I've locally advanced my fixes branch to include all the material that will
merge in next couple of weeks, but for now can't push it out without making
a mess of linux-next (it will be in wrong place in the sequence)

So applied, but you can't see it yet!

Jonathan

> ---
>  drivers/iio/light/apds9306.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/iio/light/apds9306.c b/drivers/iio/light/apds9306.c
> index 69a0d609cffc91cc3daba160f309f511270be385..5ed7e17f49e76206609aba83c85e8144c536d17d 100644
> --- a/drivers/iio/light/apds9306.c
> +++ b/drivers/iio/light/apds9306.c
> @@ -108,11 +108,11 @@ static const struct part_id_gts_multiplier apds9306_gts_mul[] = {
>  	{
>  		.part_id = 0xB1,
>  		.max_scale_int = 16,
> -		.max_scale_nano = 3264320,
> +		.max_scale_nano = 326432000,
>  	}, {
>  		.part_id = 0xB3,
>  		.max_scale_int = 14,
> -		.max_scale_nano = 9712000,
> +		.max_scale_nano = 97120000,
>  	},
>  };
>  
> 
> ---
> base-commit: 577a66e2e634f712384c57a98f504c44ea4b47da
> change-id: 20241218-apds9306_nano_vals-d880219a82f2
> 
> Best regards,


      parent reply	other threads:[~2025-01-18 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-12  0:08 Javier Carrasco
2025-01-16 11:34 ` Subhajit Ghosh
2025-01-18 12:24 ` Jonathan Cameron [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=20250118122455.54c1e96e@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=subhajit.ghosh@tweaklogic.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 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®