All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Antoni Pokusinski <apokusinski01@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	lars@metafoo.de, linux-kernel@vger.kernel.org,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: magnetometer: si7210: fix magnetic field measurement scale
Date: Sat, 8 Feb 2025 13:06:00 +0000	[thread overview]
Message-ID: <20250208130600.4bf562d7@jic23-huawei> (raw)
In-Reply-To: <20250204192454.55489311@jic23-huawei>

On Tue, 4 Feb 2025 19:24:54 +0000
Jonathan Cameron <jic23@kernel.org> wrote:

> On Mon, 3 Feb 2025 20:39:20 +0100
> Antoni Pokusinski <apokusinski01@gmail.com> wrote:
> 
> > On Mon, Feb 03, 2025 at 11:26:27AM +0200, Andy Shevchenko wrote:  
> > > On Sun, Feb 02, 2025 at 11:07:10AM +0100, Antoni Pokusinski wrote:    
> > > > Applying the current scale value to the raw magnetic field measurements
> > > > gives the result in mT.
> > > > 
> > > > Fix the scale by increasing it 10 times, so that the final result after
> > > > applying the scale is in Gauss.    
> > > 
> > > No objections against this change, just wondering since these are
> > > the ABI changes (correct?) how should we really handle them in case
> > > some of the user space stuff already relies on 'bad' values?
> > > 
> > > -- 
> > > With Best Regards,
> > > Andy Shevchenko
> > > 
> > >     
> > 
> > Just to clarify: yes, this patch makes the output values compliant to
> > ABI (Documentation/ABI/testing/sysfs-bus-iio). According to the ABI, the
> > output values for the magnetic field should be in Gauss, but during
> > the driver development I missed the fact that I return values in mT
> > instead... (1 Gauss = 0.1mT)
> > 
> > BTW I see that the patch cb29542a178f ("iio: magnetometer: si7210: add
> > driver for Si7210") is still on the "testing" branch only, so perhaps
> > it's still not too late to apply the fix?
> >   
> Ah. I'd not registered that.  Definitely makes life easier.
> This will just get queued up behind it and land upstream at the same
> time.
> 
> Jonathan
Applied.
> 
> > Kind regards,
> > Antoni
> > 
> >   
> 
> 


      reply	other threads:[~2025-02-08 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-02 10:07 [PATCH] iio: magnetometer: si7210: fix magnetic field measurement scale Antoni Pokusinski
2025-02-03  9:26 ` Andy Shevchenko
2025-02-03 15:27   ` Jonathan Cameron
2025-02-03 19:39   ` Antoni Pokusinski
2025-02-04 19:24     ` Jonathan Cameron
2025-02-08 13:06       ` 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=20250208130600.4bf562d7@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=apokusinski01@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@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 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.