linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakob Hauser <jahau@rocketmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-iio@vger.kernel.org, phone-devel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	Jakob Hauser <jahau@rocketmail.com>
Subject: [PATCH 0/7] Add support for magnetometer Yamaha YAS537
Date: Thu,  9 Jun 2022 01:36:18 +0200	[thread overview]
Message-ID: <cover.1654727058.git.jahau@rocketmail.com> (raw)
In-Reply-To: cover.1654727058.git.jahau.ref@rocketmail.com

This patchset adds YAS537 variant to the already existing driver for
Yamaha YAS magnetometers.

Patches 1-4 applies corrections that popped up when working on this.
Patches 5-6 are preparations for adding YAS537.
Patch 7 finally adds the YAS537 variant.

Jakob Hauser (7):
  iio: magnetometer: yas530: Change range of data in volatile register
  iio: magnetometer: yas530: Correct scaling of magnetic axes
  iio: magnetometer: yas530: Correct temperature handling
  iio: magnetometer: yas530: Change data type of hard_offsets to signed
  iio: magnetometer: yas530: Change data type of calibration
    coefficients
  iio: magnetometer: yas530: Remove redundant defaults on switch devid
  iio: magnetometer: yas530: Add YAS537 variant

 drivers/iio/magnetometer/Kconfig         |   4 +-
 drivers/iio/magnetometer/yamaha-yas530.c | 814 +++++++++++++++++++----
 2 files changed, 698 insertions(+), 120 deletions(-)

-- 
2.35.1


       reply	other threads:[~2022-06-08 23:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1654727058.git.jahau.ref@rocketmail.com>
2022-06-08 23:36 ` Jakob Hauser [this message]
2022-06-08 23:38   ` [PATCH 1/7] iio: magnetometer: yas530: Change range of data in volatile register Jakob Hauser
2022-06-09  8:50     ` Linus Walleij
2022-06-08 23:38   ` [PATCH 2/7] iio: magnetometer: yas530: Correct scaling of magnetic axes Jakob Hauser
2022-06-09  8:52     ` Linus Walleij
2022-06-08 23:38   ` [PATCH 3/7] iio: magnetometer: yas530: Correct temperature handling Jakob Hauser
2022-06-09  8:53     ` Linus Walleij
2022-06-08 23:38   ` [PATCH 4/7] iio: magnetometer: yas530: Change data type of hard_offsets to signed Jakob Hauser
2022-06-09  8:54     ` Linus Walleij
2022-06-10 14:22     ` Andy Shevchenko
2022-06-08 23:38   ` [PATCH 5/7] iio: magnetometer: yas530: Change data type of calibration coefficients Jakob Hauser
2022-06-09  8:55     ` Linus Walleij
2022-06-08 23:38   ` [PATCH 6/7] iio: magnetometer: yas530: Remove redundant defaults on switch devid Jakob Hauser
2022-06-09  8:55     ` Linus Walleij
2022-06-10 14:24     ` Andy Shevchenko
2022-06-08 23:38   ` [PATCH 7/7] iio: magnetometer: yas530: Add YAS537 variant Jakob Hauser
2022-06-09  8:56     ` Linus Walleij
2022-06-10 14:31     ` Andy Shevchenko
2022-06-10 23:57       ` Jakob Hauser
2022-06-11 10:56         ` Andy Shevchenko
2022-06-11 14:00           ` Jakob Hauser
2022-06-11 20:22             ` Andy Shevchenko
2022-06-11 21:19               ` Jakob Hauser

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=cover.1654727058.git.jahau@rocketmail.com \
    --to=jahau@rocketmail.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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).