From: Stephan Gerhold <stephan@gerhold.net>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Peter Meerwald <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
Bastien Nocera <hadess@hadess.net>,
Hans de Goede <hdegoede@redhat.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
~postmarketos/upstreaming@lists.sr.ht,
Stephan Gerhold <stephan@gerhold.net>
Subject: [PATCH v2 5/9] dt-bindings: iio: accel: bma255: Document bosch,bma253
Date: Thu, 10 Jun 2021 14:21:22 +0200 [thread overview]
Message-ID: <20210610122126.50504-6-stephan@gerhold.net> (raw)
In-Reply-To: <20210610122126.50504-1-stephan@gerhold.net>
BMA253 is mostly like BMA255 that is already supported by the
bmc150-accel driver. Document an extra bosch,bma253 compatible for it.
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
---
Documentation/devicetree/bindings/iio/accel/bosch,bma255.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/iio/accel/bosch,bma255.yaml b/Documentation/devicetree/bindings/iio/accel/bosch,bma255.yaml
index c2efbb813ca2..8afb0fe8ef5c 100644
--- a/Documentation/devicetree/bindings/iio/accel/bosch,bma255.yaml
+++ b/Documentation/devicetree/bindings/iio/accel/bosch,bma255.yaml
@@ -18,6 +18,7 @@ properties:
enum:
- bosch,bmc150_accel
- bosch,bmi055_accel
+ - bosch,bma253
- bosch,bma255
- bosch,bma250e
- bosch,bma222
--
2.32.0
next prev parent reply other threads:[~2021-06-10 12:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 12:21 [PATCH v2 0/9] iio: accel: bmc150: Add support for BMA253/BMA254 Stephan Gerhold
2021-06-10 12:21 ` [PATCH v2 1/9] iio: accel: bmc150: Fix bma222 scale unit Stephan Gerhold
2021-06-10 12:21 ` [PATCH v2 2/9] iio: accel: bmc150: Drop misleading/duplicate chip identifiers Stephan Gerhold
2021-06-10 12:21 ` [PATCH v2 3/9] iio: accel: bmc150: Drop duplicated documentation of supported chips Stephan Gerhold
2021-06-10 12:45 ` Andy Shevchenko
2021-06-10 12:48 ` Stephan Gerhold
2021-06-10 12:21 ` [PATCH v2 4/9] iio: accel: bmc150: Sort all chip names alphabetically / by chip ID Stephan Gerhold
2021-06-10 12:50 ` Andy Shevchenko
2021-06-10 13:00 ` Stephan Gerhold
2021-06-10 12:21 ` Stephan Gerhold [this message]
2021-06-10 12:21 ` [PATCH v2 6/9] iio: accel: bmc150: Add device IDs for BMA253 Stephan Gerhold
2021-06-10 12:51 ` Andy Shevchenko
2021-06-10 13:02 ` Stephan Gerhold
2021-06-10 12:21 ` [PATCH v2 7/9] dt-bindings: iio: bma255: Allow multiple interrupts Stephan Gerhold
2021-06-10 12:21 ` [PATCH v2 8/9] dt-bindings: iio: accel: bma180/bma255: Move bma254 to bma255 schema Stephan Gerhold
2021-06-10 12:21 ` [PATCH v2 9/9] iio: accel: bma180/bmc150: Move BMA254 to bmc150-accel driver Stephan Gerhold
2021-06-10 12:54 ` Andy Shevchenko
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=20210610122126.50504-6-stephan@gerhold.net \
--to=stephan@gerhold.net \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hadess@hadess.net \
--cc=hdegoede@redhat.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@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 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.