From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: [PATCH 0/6] dt-bindings: Add some missing IIO related binding docs.
Date: Thu, 1 Apr 2021 18:41:06 +0100 [thread overview]
Message-ID: <20210401174112.320497-1-jic23@kernel.org> (raw)
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
First of what will probably be one of several sets to slowly but surely
add yaml binding docs for all the defacto bindings hiding in IIO
drivers. Ultimate I'd like to clear the backlog of these and so go
forward with full documenation, but there may be some cases we just decide
are too complex to bother. The fsl,mma955x parts are ignored (for now) on
that basis (I think we have all the other accelerometers covered now)
Some of these date back to board file days and some were added by people
only interested in ACPI, but all can be instantiated from dt-bindings.
A few may simply have slipped through the net during review.
Testing done with hacked up qemu when anything was non trivial.
Jonathan Cameron (6):
dt-bindings:iio:accel:adis16201 and adis16209 bindings
dt-bindings:iio:accel:bosch,bma220 device tree binding documentation
dt-bindings:iio:accel:fsl,mma7455 binding doc
dt-bindings:trivial-devices: Add memsic,mxc4005/mxc6255/mxc6655
entries
dt-bindings:trivial-devices: Add sensortek,stk8312 and
sensortek,s8ba50
dt-bindings:iio:adc:adi,ad7298 document bindings
.../bindings/iio/accel/adi,adis16201.yaml | 55 +++++++++++++
.../bindings/iio/accel/bosch,bma220.yaml | 50 +++++++++++
.../bindings/iio/accel/fsl,mma7455.yaml | 82 +++++++++++++++++++
.../bindings/iio/adc/adi,ad7298.yaml | 48 +++++++++++
.../devicetree/bindings/trivial-devices.yaml | 10 +++
5 files changed, 245 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/accel/adi,adis16201.yaml
create mode 100644 Documentation/devicetree/bindings/iio/accel/bosch,bma220.yaml
create mode 100644 Documentation/devicetree/bindings/iio/accel/fsl,mma7455.yaml
create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7298.yaml
--
2.31.1
next reply other threads:[~2021-04-01 17:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 17:41 Jonathan Cameron [this message]
2021-04-01 17:41 ` [PATCH 1/6] dt-bindings:iio:accel:adis16201 and adis16209 bindings Jonathan Cameron
2021-04-09 14:32 ` Rob Herring
2021-04-01 17:41 ` [PATCH 2/6] dt-bindings:iio:accel:bosch,bma220 device tree binding documentation Jonathan Cameron
2021-04-09 14:33 ` Rob Herring
2021-04-01 17:41 ` [PATCH 3/6] dt-bindings:iio:accel:fsl,mma7455 binding doc Jonathan Cameron
2021-04-09 14:34 ` Rob Herring
2021-04-01 17:41 ` [PATCH 4/6] dt-bindings:trivial-devices: Add memsic,mxc4005/mxc6255/mxc6655 entries Jonathan Cameron
2021-04-09 14:35 ` Rob Herring
2021-04-01 17:41 ` [PATCH 5/6] dt-bindings:trivial-devices: Add sensortek,stk8312 and sensortek,s8ba50 Jonathan Cameron
2021-04-09 14:35 ` Rob Herring
2021-04-01 17:41 ` [PATCH 6/6] dt-bindings:iio:adc:adi,ad7298 document bindings Jonathan Cameron
2021-04-09 14:37 ` Rob Herring
2021-04-24 17:18 ` [PATCH 0/6] dt-bindings: Add some missing IIO related binding docs Jonathan Cameron
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=20210401174112.320497-1-jic23@kernel.org \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=robh+dt@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).