From: Jonathan Albrieux <jonathan.albrieux@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: ~postmarketos/upstreaming@lists.sr.ht, daniel.baluta@gmail.com,
Jonathan Albrieux <jonathan.albrieux@gmail.com>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS), Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org (open list:IIO SUBSYSTEM AND DRIVERS),
Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Subject: [PATCH v4 0/5] iio: imu: bmi160: added regulator and mount-matrix support
Date: Mon, 25 May 2020 18:45:59 +0200 [thread overview]
Message-ID: <20200525164615.14962-1-jonathan.albrieux@gmail.com> (raw)
v4:
- add maintainer
- clean up of documentation
- added case concerning the need to add regulators, see [PATCH v4 4/5]
v3:
- separate typo fix into another patch
- clean up of documentation
- clean up of patch messages
https://lore.kernel.org/linux-iio/20200520194656.16218-1-jonathan.albrieux@gmail.com/
v2:
- fixed missing description for iio: imu: bmi160: added regulator
support
https://lore.kernel.org/linux-iio/20200519075111.6356-1-jonathan.albrieux@gmail.com/
v1:
- initial patch submission
https://lore.kernel.org/linux-iio/20200518133358.18978-1-jonathan.albrieux@gmail.com/
Convert txt format documentation to yaml.
Add documentation about vdd-supply, vddio-supply and mount-matrix.
Add vdd-supply and vddio-supply support.
Add mount-matrix binding support. As chip could have different
orientations a mount matrix support is needed to correctly translate
these differences.
Jonathan Albrieux (5):
dt-bindings: iio: imu: bmi160: convert format to yaml, add maintainer
dt-bindings: iio: imu: bmi160: add regulators and mount-matrix
iio: imu: bmi160: fix typo
iio: imu: bmi160: added regulator support
iio: imu: bmi160: added mount-matrix support
.../devicetree/bindings/iio/imu/bmi160.txt | 37 --------
.../bindings/iio/imu/bosch,bmi160.yaml | 91 +++++++++++++++++++
drivers/iio/imu/bmi160/bmi160.h | 3 +
drivers/iio/imu/bmi160/bmi160_core.c | 46 +++++++++-
4 files changed, 139 insertions(+), 38 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/iio/imu/bmi160.txt
create mode 100644 Documentation/devicetree/bindings/iio/imu/bosch,bmi160.yaml
--
2.17.1
next reply other threads:[~2020-05-25 16:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 16:45 Jonathan Albrieux [this message]
2020-05-25 16:46 ` [PATCH v4 1/5] dt-bindings: iio: imu: bmi160: convert format to yaml, add maintainer Jonathan Albrieux
2020-05-29 17:08 ` Rob Herring
2020-05-31 14:02 ` Jonathan Cameron
2020-05-25 16:46 ` [PATCH v4 2/5] dt-bindings: iio: imu: bmi160: add regulators and mount-matrix Jonathan Albrieux
2020-05-29 17:09 ` Rob Herring
2020-05-31 14:05 ` Jonathan Cameron
2020-05-25 16:46 ` [PATCH v4 3/5] iio: imu: bmi160: fix typo Jonathan Albrieux
2020-05-31 14:27 ` Jonathan Cameron
2020-05-25 16:46 ` [PATCH v4 4/5] iio: imu: bmi160: added regulator support Jonathan Albrieux
2020-05-31 14:28 ` Jonathan Cameron
2020-05-25 16:46 ` [PATCH v4 5/5] iio: imu: bmi160: added mount-matrix support Jonathan Albrieux
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=20200525164615.14962-1-jonathan.albrieux@gmail.com \
--to=jonathan.albrieux@gmail.com \
--cc=daniel.baluta@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--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).