devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emil Gedenryd <Emil.Gedenryd@axis.com>
To: "jic23@kernel.org" <jic23@kernel.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dannenberg@ti.com" <dannenberg@ti.com>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	Kernel <Kernel@axis.com>
Subject: Re: [PATCH 1/3] iio: light: opt3001: add missing full-scale range value
Date: Mon, 9 Sep 2024 07:15:07 +0000	[thread overview]
Message-ID: <a9021ca8ec6b52cbbac744ccced14aea605a1da4.camel@axis.com> (raw)
In-Reply-To: <20240907182824.56396b0a@jic23-huawei>

On Sat, 2024-09-07 at 18:28 +0100, Jonathan Cameron wrote:
> On Thu, 5 Sep 2024 12:20:45 +0200
> Emil Gedenryd <emil.gedenryd@axis.com> wrote:
> 
> > The opt3001 driver uses predetermined full-scale range values to
> > determine what exponent to use for event trigger threshold values.
> > The problem is that one of the values specified in the datasheet is
> > missing from the implementation, causing a big gap in settable values.
> > 
> > Add missing full-scale range array value.
> > 
> > Signed-off-by: Emil Gedenryd <emil.gedenryd@axis.com>
> I assume this has more of an impact in that if you write values beyond this one
> the index will be off by one and the value written to the register
> will be incorrect?
> 
> Please clarify if that is the case and also add a fixes tag
> to the commit that introduced this bug.
> 
> Thanks,
> 
> Jonathan
Hi Jonathan,
You are correct regarding the behaviour. Thanks for the suggestion 
on how to clarify the message, I'll update it as well as add a fixes 
tag when I submit a new version either later today or tomorrow.

Best regards,
Emil
> 
> > ---
> >  drivers/iio/light/opt3001.c | 4 ++++
> >  1 file changed, 4 insertions(+)
> > 
> > diff --git a/drivers/iio/light/opt3001.c b/drivers/iio/light/opt3001.c
> > index 887c4b776a86..176e54bb48c3 100644
> > --- a/drivers/iio/light/opt3001.c
> > +++ b/drivers/iio/light/opt3001.c
> > @@ -138,6 +138,10 @@ static const struct opt3001_scale opt3001_scales[] = {
> >  		.val = 20966,
> >  		.val2 = 400000,
> >  	},
> > +	{
> > +		.val = 41932,
> > +		.val2 = 800000,
> > +	},
> >  	{
> >  		.val = 83865,
> >  		.val2 = 600000,
> > 
> 


  reply	other threads:[~2024-09-09  7:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 10:20 [PATCH 0/3] iio: light: opt3001: add support for TI's opt3002 light sensor Emil Gedenryd
2024-09-05 10:20 ` [PATCH 1/3] iio: light: opt3001: add missing full-scale range value Emil Gedenryd
2024-09-07 17:28   ` Jonathan Cameron
2024-09-09  7:15     ` Emil Gedenryd [this message]
2024-09-05 10:20 ` [PATCH 2/3] iio: light: opt3001: add support for TI's opt3002 light sensor Emil Gedenryd
2024-09-05 10:37   ` Krzysztof Kozlowski
2024-09-06 21:32   ` kernel test robot
2024-09-07 17:35   ` Jonathan Cameron
2024-09-09  7:54     ` Emil Gedenryd
2024-09-09 19:13       ` Jonathan Cameron
2024-09-13  7:18         ` Emil Gedenryd
2024-09-05 10:20 ` [PATCH 3/3] dt-bindings: iio: light: opt3001: add compatible for opt3002 Emil Gedenryd
2024-09-05 10:38   ` Krzysztof Kozlowski
2024-09-05 11:11   ` Rob Herring (Arm)
2024-09-05 10:38 ` [PATCH 0/3] iio: light: opt3001: add support for TI's opt3002 light sensor Krzysztof Kozlowski
2024-09-05 10:55   ` Emil Gedenryd

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=a9021ca8ec6b52cbbac744ccced14aea605a1da4.camel@axis.com \
    --to=emil.gedenryd@axis.com \
    --cc=Kernel@axis.com \
    --cc=conor+dt@kernel.org \
    --cc=dannenberg@ti.com \
    --cc=devicetree@vger.kernel.org \
    --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).