From: "Rob Herring (Arm)" <robh@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: linux-kernel@vger.kernel.org, "Nuno Sá" <nuno.sa@analog.com>,
linux-doc@vger.kernel.org, "Jonathan Cameron" <jic23@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
devicetree@vger.kernel.org, "Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org,
"Conor Dooley" <conor.dooley@microchip.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Michael Hennerich" <michael.hennerich@analog.com>
Subject: Re: [PATCH v4 1/3] dt-bindings: iio: adc: add AD4695 and similar ADCs
Date: Thu, 11 Jul 2024 14:32:47 -0600 [thread overview]
Message-ID: <172072996727.2951364.2243340017408650155.robh@kernel.org> (raw)
In-Reply-To: <20240711-iio-adc-ad4695-v4-1-c31621113b57@baylibre.com>
On Thu, 11 Jul 2024 14:15:41 -0500, David Lechner wrote:
> Add device tree bindings for AD4695 and similar ADCs.
>
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
> ---
>
> Note, this may trigger a DT build warning "common-mode-channel: missing
> type definition" if the builder doesn't include the recently added
> common-mode-channel property [1]. This should be safe to ignore (passes
> make dt_binding_check locally).
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/commit/?h=testing&id=d86deaec1c5b0fb60c3619e8d2ae7a1d722fd2ad
>
> v4 changes:
> * Picked up Conor's reviewed-by tag.
>
> v3 changes:
> * Change interrupts to be per pin instead of per signal.
> * Drop diff-channels and single-channel properties.
> * Odd numbered pins added to common-mode-channel property enum.
> * REFGND and COM values changes to avoid confusion with pin numbers.
> * Add inX-supply properties for odd numbed input pins.
>
> v2 changes:
> * Drop *-wlcsp compatible strings
> * Don't use fallback compatible strings
> * Reword supply descriptions
> * Use standard channel properties instead of adi,pin-pairing
> * Fix unnecessary | character
> * Fix missing blank line
> * Add header file with common mode channel macros
> ---
> .../devicetree/bindings/iio/adc/adi,ad4695.yaml | 256 +++++++++++++++++++++
> MAINTAINERS | 10 +
> include/dt-bindings/iio/adi,ad4695.h | 9 +
> 3 files changed, 275 insertions(+)
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/adi,ad4695.yaml: common-mode-channel: missing type definition
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20240711-iio-adc-ad4695-v4-1-c31621113b57@baylibre.com
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
next prev parent reply other threads:[~2024-07-11 20:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 19:15 [PATCH v4 0/3] iio: adc: ad4695: new driver for AD4695 and similar ADCs David Lechner
2024-07-11 19:15 ` [PATCH v4 1/3] dt-bindings: iio: adc: add " David Lechner
2024-07-11 20:32 ` Rob Herring (Arm) [this message]
2024-08-08 18:10 ` Rob Herring
2024-07-11 19:15 ` [PATCH v4 2/3] iio: adc: ad4695: Add driver for " David Lechner
2024-07-12 11:20 ` Nuno Sá
2024-07-20 10:46 ` Jonathan Cameron
2024-07-11 19:15 ` [PATCH v4 3/3] Documentation: iio: Document ad4695 driver David Lechner
2024-07-20 10:48 ` [PATCH v4 0/3] iio: adc: ad4695: new driver for AD4695 and similar ADCs 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=172072996727.2951364.2243340017408650155.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=nuno.sa@analog.com \
/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