From: Rob Herring <robh@kernel.org>
To: Cristian Pop <cristian.pop@analog.com>
Cc: linux-iio@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, jic23@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: addac: one-bit-adc-dac yaml documentation
Date: Tue, 11 Jan 2022 16:02:57 -0600 [thread overview]
Message-ID: <Yd3+kSr5xtL53jUQ@robh.at.kernel.org> (raw)
In-Reply-To: <20220111115919.14645-1-cristian.pop@analog.com>
On Tue, Jan 11, 2022 at 01:59:18PM +0200, Cristian Pop wrote:
> This adds device tree bindings for the one-bit-adc-dac.
I have no idea what a one-bit-adc-dac is. Please describe or provide a
reference to what this h/w looks like.
>
> Signed-off-by: Cristian Pop <cristian.pop@analog.com>
> V1->V2
This belongs below the '---'
> - I am aware of the recommendation of rename/move this driver. Should we
> consider "drivers/io/gpio.c"?
> - Add .yaml file
> - Remove blank lines, remove unnecessary coma
> - Remove macros for channels
> - Check if channel is input for write_raw
> - Use labels instead of extend_name
> - Fix channel indexing
> - Use "sizeof(*channels)" in devm_kcalloc()
> - Remove assignment: " indio_dev->dev.parent = &pdev->dev;"
> - Remove "platform_set_drvdata"
> - Remove "adi" from compatible string since is not ADI specific driver.
> ---
> .../bindings/iio/addac/one-bit-adc-dac.yaml | 89 +++++++++++++++++++
> 1 file changed, 89 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/addac/one-bit-adc-dac.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/addac/one-bit-adc-dac.yaml b/Documentation/devicetree/bindings/iio/addac/one-bit-adc-dac.yaml
> new file mode 100644
> index 000000000000..dbed0f3b1ca4
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/addac/one-bit-adc-dac.yaml
> @@ -0,0 +1,89 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +# Copyright 2020 Analog Devices Inc.
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/addac/one-bit-adc-dac.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Analog Devices one bit ADC DAC driver
> +
> +maintainers:
> + - Cristian Pop <cristian.pop@analog.com>
> +
> +description: |
> + One bit ADC DAC driver
> +
> +properties:
> + compatible:
> + enum:
> + - adi,one-bit-adc-dac
> +
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> + in-gpios:
> + description: Input GPIOs
> +
> + out-gpios:
> + description: Output GPIOs
No constraints on how many GPIOs?
> +
> +required:
> + - compatible
> + - in-gpios
> + - out-gpios
> +
> +patternProperties:
> + "^channel@([0-9]|1[0-5])$":
> + type: object
> + description: |
> + Represents the external channels which are connected to the ADDAC.
> +
> + properties:
> + reg:
> + maxItems: 1
> + description: |
> + The channel number.
> +
> + label:
> + description: |
> + Unique name to identify which channel this is.
> +
> + required:
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + one-bit-adc-dac@0 {
> + compatible = "one-bit-adc-dac";
> +
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + in-gpios = <&gpio 17 0>, <&gpio 27 0>;
> + out-gpios = <&gpio 23 0>, <&gpio 24 0>;
> +
> + channel@0 {
> + reg = <0>;
What does '0' correspond to?
> + label = "i_17";
Why is this needed? 'label' is supposed to correspond to physical
labelling of ports. IOW, for identification by humans looking at the
device.
This all looks duplicated from information in in-gpios and out-gpios.
> + };
> +
> + channel@1 {
> + reg = <1>;
> + label = "i_27";
> + };
> +
> + channel@2 {
> + reg = <2>;
> + label = "o_23";
> + };
> +
> + channel@3 {
> + reg = <3>;
> + label = "o_24";
> + };
> + };
> --
> 2.17.1
>
>
next prev parent reply other threads:[~2022-01-11 22:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 11:59 [PATCH v2 1/2] dt-bindings: iio: addac: one-bit-adc-dac yaml documentation Cristian Pop
2022-01-11 11:59 ` [PATCH v2 2/2] one-bit-adc-dac: Add initial version of one bit ADC-DAC Cristian Pop
2022-01-12 15:23 ` Andy Shevchenko
2022-01-12 16:29 ` kernel test robot
2022-01-16 11:52 ` Jonathan Cameron
2022-01-18 17:06 ` Andy Shevchenko
2022-01-21 14:56 ` Jonathan Cameron
2022-01-19 9:38 ` Sa, Nuno
2022-01-21 10:24 ` Pop, Cristian
2022-01-21 14:54 ` Jonathan Cameron
2022-01-11 15:14 ` [PATCH v2 1/2] dt-bindings: iio: addac: one-bit-adc-dac yaml documentation Rob Herring
2022-01-11 22:02 ` Rob Herring [this message]
2022-01-16 11:30 ` 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=Yd3+kSr5xtL53jUQ@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=cristian.pop@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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 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.