[PATCH 0/2] iio: Add support for TI ADS1X18 ADCs

[PATCH 0/2] iio: Add support for TI ADS1X18 ADCs

[Kurt Borja]

Hi,

This series adds a new driver for TI ADS1X18 SPI devices.

This is my first time contributing to the IIO subsystem and making
dt-bindings documentation, so (don't) go easy on me :p.

As explained in Patch 2 changelog, the DRDY interrupt line is shared
with the MOSI pin. This awkward quirk is also found on some Analog
Devices sigma-delta SPI ADCs, so the interrupt and trigger design is
inspired by those.

Thank you in advance for your reviews.

Signed-off-by: Kurt Borja <kuurtb@gmail.com>
---
Kurt Borja (2):
      dt-bindings: iio: adc: Add TI ADS1018/ADS1118
      iio: adc: Add ti-ads1x18 driver

 .../devicetree/bindings/iio/adc/ti,ads1118.yaml    | 132 +++
 MAINTAINERS                                        |   7 +
 drivers/iio/adc/Kconfig                            |  12 +
 drivers/iio/adc/Makefile                           |   1 +
 drivers/iio/adc/ti-ads1x18.c                       | 919 +++++++++++++++++++++
 5 files changed, 1071 insertions(+)
---
base-commit: f9e05791642810a0cf6237d39fafd6fec5e0b4bb
change-id: 20251012-ads1x18-0d0779d06690

-- 
 ~ Kurt

[PATCH 1/2] dt-bindings: iio: adc: Add TI ADS1018/ADS1118

[Kurt Borja]

Add documentation for Texas Instruments ADS1018 and ADS1118
analog-to-digital converters.

Signed-off-by: Kurt Borja <kuurtb@gmail.com>
---
 .../devicetree/bindings/iio/adc/ti,ads1118.yaml    | 132 +++++++++++++++++++++
 1 file changed, 132 insertions(+)

diff --git a/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml b/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml
new file mode 100644
index 000000000000..eb7228ed6ddb
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml
@@ -0,0 +1,132 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/adc/ti,ads1118.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: TI ADS1018/ADS1118 SPI analog to digital converter
+
+maintainers:
+  - Kurt Borja <kuurtb@gmail.com>
+
+description: |
+  The ADS1018/ADS1118 is a precision, low-power, 12-bit or 16-bit, noise-free,
+  analog-to-digital converter (ADC). It integrates a programmable gain amplifier
+  (PGA), voltage reference, oscillator and high-accuracy temperature sensor.
+
+  Datasheets:
+    - ADS1018: https://www.ti.com/lit/ds/symlink/ads1018.pdf
+    - ADS1118: https://www.ti.com/lit/ds/symlink/ads1118.pdf
+
+properties:
+  compatible:
+    enum:
+      - ti,ads1018
+      - ti,ads1118
+
+  reg:
+    maxitems: 1
+
+  interrupts:
+    description: DOUT/DRDY (Data Out/Data Ready) line.
+    maxitems: 1
+
+  drdy-gpios:
+    description:
+      Extra GPIO line connected to DOUT/DRDY (Data Out/Data Ready). This allows
+      distinguishing between latched and real DRDY IRQs.
+    maxitems: 1
+
+  '#address-cells':
+    const: 1
+
+  '#size-cells':
+    const: 0
+
+  '#io-channel-cells':
+    const: 1
+
+required:
+  - compatible
+  - reg
+  - drdy-gpios
+  - '#address-cells'
+  - '#size-cells'
+
+patternProperties:
+  "^channel@[0-7]$":
+    type: object
+    $ref: /schemas/iio/adc/adc.yaml#
+    description: Properties for a single ADC channel.
+
+    properties:
+      reg:
+        minimum: 0
+        maximum: 7
+        description: The channel index (0-7).
+
+      ti,gain:
+        $ref: /schemas/types.yaml#/definitions/uint32
+        minimum: 0
+        maximum: 5
+        description:
+          Programmable gain amplifier configuration, as described in the PGA
+          Config Register Field description. If not present, the default is
+          used.
+
+      ti,datarate:
+        $ref: /schemas/types.yaml#/definitions/uint32
+        minimum: 0
+        maximum: 7
+        description:
+          Data rate configuration, as described in the DR Config Register Field
+          description. If not present, the default is used.
+
+    required:
+      - reg
+
+    additionalProperties: false
+
+allOf:
+  - $ref: /schemas/spi/spi-peripheral-props.yaml#
+
+  - if:
+    properties:
+      compatible:
+        contains:
+          const: ti,ads1018
+    then:
+      patternProperties:
+        "^channel@[0-7]$":
+          properties:
+            ti,datarate:
+              maximum: 6
+
+unevaluatedProperties: false
+
+examples:
+  - |
+    spi0 {
+        #address-cells = <1>;
+        #size-cells = <0>;
+
+        ads1118@0 {
+            compatible = "ti,ads1118";
+            reg = <0>;
+
+            #address-cells = <1>;
+            #size-cells = <0>;
+
+            spi-max-frequency = <4000000>;
+            spi-cpha;
+
+            interrupts-extended = <&gpio 14 IRQ_TYPE_EDGE_FALLING>;
+            drdy-gpios = <&gpio 14 GPIO_ACTIVE_LOW>;
+
+            channel@4 {
+                reg = <4>;
+                ti,gain = <0>;
+                ti,datarate = <7>;
+            };
+        };
+    };

-- 
2.52.0

Re: [PATCH 1/2] dt-bindings: iio: adc: Add TI ADS1018/ADS1118

[Rob Herring (Arm)]

On Fri, 21 Nov 2025 12:16:14 -0500, Kurt Borja wrote:
> Add documentation for Texas Instruments ADS1018 and ADS1118
> analog-to-digital converters.
> 
> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
> ---
>  .../devicetree/bindings/iio/adc/ti,ads1118.yaml    | 132 +++++++++++++++++++++
>  1 file changed, 132 insertions(+)
> 

My bot found errors running 'make dt_binding_check' on your patch:

yamllint warnings/errors:
./Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml:93:8: [error] empty value in block mapping (empty-values)

dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml: ignoring, error in schema: allOf: 1: if
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml: properties:reg: 'anyOf' conditional failed, one must be fixed:
	'maxitems' is not one of ['$ref', 'additionalItems', 'additionalProperties', 'allOf', 'anyOf', 'const', 'contains', 'default', 'dependencies', 'dependentRequired', 'dependentSchemas', 'deprecated', 'description', 'else', 'enum', 'exclusiveMaximum', 'exclusiveMinimum', 'items', 'if', 'minItems', 'minimum', 'maxItems', 'maximum', 'multipleOf', 'not', 'oneOf', 'pattern', 'patternProperties', 'properties', 'required', 'then', 'typeSize', 'unevaluatedProperties', 'uniqueItems']
	'type' was expected
	from schema $id: http://devicetree.org/meta-schemas/keywords.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml: properties:drdy-gpios: 'anyOf' conditional failed, one must be fixed:
	'maxitems' is not one of ['$ref', 'additionalItems', 'additionalProperties', 'allOf', 'anyOf', 'const', 'contains', 'default', 'dependencies', 'dependentRequired', 'dependentSchemas', 'deprecated', 'description', 'else', 'enum', 'exclusiveMaximum', 'exclusiveMinimum', 'items', 'if', 'minItems', 'minimum', 'maxItems', 'maximum', 'multipleOf', 'not', 'oneOf', 'pattern', 'patternProperties', 'properties', 'required', 'then', 'typeSize', 'unevaluatedProperties', 'uniqueItems']
	'type' was expected
	from schema $id: http://devicetree.org/meta-schemas/keywords.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml: properties:interrupts: 'anyOf' conditional failed, one must be fixed:
	'maxitems' is not one of ['$ref', 'additionalItems', 'additionalProperties', 'allOf', 'anyOf', 'const', 'contains', 'default', 'dependencies', 'dependentRequired', 'dependentSchemas', 'deprecated', 'description', 'else', 'enum', 'exclusiveMaximum', 'exclusiveMinimum', 'items', 'if', 'minItems', 'minimum', 'maxItems', 'maximum', 'multipleOf', 'not', 'oneOf', 'pattern', 'patternProperties', 'properties', 'required', 'then', 'typeSize', 'unevaluatedProperties', 'uniqueItems']
	'type' was expected
	from schema $id: http://devicetree.org/meta-schemas/keywords.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml: properties:reg: 'anyOf' conditional failed, one must be fixed:
	'maxItems' is a required property
		hint: Only "maxItems" is required for a single entry if there are no constraints defined for the values.
	'maxitems' is not one of ['maxItems', 'description', 'deprecated']
		hint: Only "maxItems" is required for a single entry if there are no constraints defined for the values.
	Additional properties are not allowed ('maxitems' was unexpected)
		hint: Arrays must be described with a combination of minItems/maxItems/items
	'maxitems' is not one of ['description', 'deprecated', 'const', 'enum', 'minimum', 'maximum', 'multipleOf', 'default', '$ref', 'oneOf']
	hint: cell array properties must define how many entries and what the entries are when there is more than one entry.
	from schema $id: http://devicetree.org/meta-schemas/cell.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml: properties:drdy-gpios: 'anyOf' conditional failed, one must be fixed:
	'maxItems' is a required property
		hint: Only "maxItems" is required for a single entry if there are no constraints defined for the values.
	'maxitems' is not one of ['maxItems', 'description', 'deprecated']
		hint: Only "maxItems" is required for a single entry if there are no constraints defined for the values.
	Additional properties are not allowed ('maxitems' was unexpected)
		hint: Arrays must be described with a combination of minItems/maxItems/items
	'maxitems' is not one of ['description', 'deprecated', 'const', 'enum', 'minimum', 'maximum', 'multipleOf', 'default', '$ref', 'oneOf']
	hint: cell array properties must define how many entries and what the entries are when there is more than one entry.
	from schema $id: http://devicetree.org/meta-schemas/cell.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml: properties:interrupts: 'anyOf' conditional failed, one must be fixed:
	'maxItems' is a required property
		hint: Only "maxItems" is required for a single entry if there are no constraints defined for the values.
	'maxitems' is not one of ['maxItems', 'description', 'deprecated']
		hint: Only "maxItems" is required for a single entry if there are no constraints defined for the values.
	Additional properties are not allowed ('maxitems' was unexpected)
		hint: Arrays must be described with a combination of minItems/maxItems/items
	'maxitems' is not one of ['description', 'deprecated', 'const', 'enum', 'minimum', 'maximum', 'multipleOf', 'default', '$ref', 'oneOf']
	hint: cell array properties must define how many entries and what the entries are when there is more than one entry.
	from schema $id: http://devicetree.org/meta-schemas/cell.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml: allOf:1:if: None is not of type 'object', 'boolean'
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml: allOf:1:if: None is not of type 'object', 'boolean'
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml: allOf:1:if: None is not of type 'object', 'boolean'
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml: allOf:1:if: None is not of type 'object', 'boolean'
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml: allOf:1:if: None is not of type 'object', 'boolean'
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml: allOf:1:if: None is not of type 'object', 'boolean'
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml: allOf:1:if: None is not of type 'object', 'boolean'
Traceback (most recent call last):
  File "/usr/local/bin/dt-doc-validate", line 8, in <module>
    sys.exit(main())
             ~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/dtschema/doc_validate.py", line 66, in main
    ret |= check_doc(f)
           ~~~~~~~~~^^^
  File "/usr/local/lib/python3.13/dist-packages/dtschema/doc_validate.py", line 37, in check_doc
    dtsch.check_schema_refs()
    ~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/dist-packages/dtschema/schema.py", line 241, in check_schema_refs
    self._check_schema_refs(resolver, self)
    ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/dist-packages/dtschema/schema.py", line 212, in _check_schema_refs
    self._check_schema_refs(resolver, v, parent=k, is_common=is_common,
    ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                            has_constraint=has_constraint)
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/dist-packages/dtschema/schema.py", line 212, in _check_schema_refs
    self._check_schema_refs(resolver, v, parent=k, is_common=is_common,
    ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                            has_constraint=has_constraint)
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/dist-packages/dtschema/schema.py", line 203, in _check_schema_refs
    ref_sch = resolver.lookup(schema['$ref']).contents
              ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/dist-packages/referencing/_core.py", line 682, in lookup
    retrieved = self._registry.get_or_retrieve(uri)
  File "/usr/local/lib/python3.13/dist-packages/referencing/_core.py", line 422, in get_or_retrieve
    registry = self.crawl()
  File "/usr/local/lib/python3.13/dist-packages/referencing/_core.py", line 500, in crawl
    id = resource.id()
  File "/usr/local/lib/python3.13/dist-packages/referencing/_core.py", line 231, in id
    id = self._specification.id_of(self.contents)
  File "/usr/local/lib/python3.13/dist-packages/referencing/jsonschema.py", line 50, in _dollar_id
    return contents.get("$id")
           ^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'get'
Lexical error: Documentation/devicetree/bindings/iio/adc/ti,ads1118.example.dts:32.49-70 Unexpected 'IRQ_TYPE_EDGE_FALLING'
Lexical error: Documentation/devicetree/bindings/iio/adc/ti,ads1118.example.dts:33.40-55 Unexpected 'GPIO_ACTIVE_LOW'
FATAL ERROR: Syntax error parsing input tree
make[2]: *** [scripts/Makefile.dtbs:132: Documentation/devicetree/bindings/iio/adc/ti,ads1118.example.dtb] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [/builds/robherring/dt-review-ci/linux/Makefile:1525: dt_binding_check] Error 2
make: *** [Makefile:248: __sub-make] Error 2

doc reference errors (make refcheckdocs):

See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20251121-ads1x18-v1-1-86db080fc9a4@gmail.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.

Re: [PATCH 1/2] dt-bindings: iio: adc: Add TI ADS1018/ADS1118

[Krzysztof Kozlowski]

On 21/11/2025 18:16, Kurt Borja wrote:
> Add documentation for Texas Instruments ADS1018 and ADS1118
> analog-to-digital converters.
> 
> Signed-off-by: Kurt Borja <kuurtb@gmail.com>

You did not test it before sending, so no full review but few nits to
save you one round of reviews:

> ---
>  .../devicetree/bindings/iio/adc/ti,ads1118.yaml    | 132 +++++++++++++++++++++
>  1 file changed, 132 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml b/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml
> new file mode 100644
> index 000000000000..eb7228ed6ddb
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml
> @@ -0,0 +1,132 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/adc/ti,ads1118.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: TI ADS1018/ADS1118 SPI analog to digital converter
> +
> +maintainers:
> +  - Kurt Borja <kuurtb@gmail.com>
> +
> +description: |
> +  The ADS1018/ADS1118 is a precision, low-power, 12-bit or 16-bit, noise-free,
> +  analog-to-digital converter (ADC). It integrates a programmable gain amplifier
> +  (PGA), voltage reference, oscillator and high-accuracy temperature sensor.
> +
> +  Datasheets:
> +    - ADS1018: https://www.ti.com/lit/ds/symlink/ads1018.pdf
> +    - ADS1118: https://www.ti.com/lit/ds/symlink/ads1118.pdf
> +
> +properties:
> +  compatible:
> +    enum:
> +      - ti,ads1018
> +      - ti,ads1118
> +
> +  reg:
> +    maxitems: 1
> +
> +  interrupts:
> +    description: DOUT/DRDY (Data Out/Data Ready) line.
> +    maxitems: 1
> +
> +  drdy-gpios:
> +    description:
> +      Extra GPIO line connected to DOUT/DRDY (Data Out/Data Ready). This allows
> +      distinguishing between latched and real DRDY IRQs.

I have feeling that you miss proper handling of IRQs (e.g. active level)
on your board.

> +    maxitems: 1
> +
> +  '#address-cells':
> +    const: 1
> +
> +  '#size-cells':
> +    const: 0
> +
> +  '#io-channel-cells':
> +    const: 1
> +
> +required:

This goes after patternProperties.

> +  - compatible
> +  - reg
> +  - drdy-gpios
> +  - '#address-cells'
> +  - '#size-cells'
> +
> +patternProperties:
> +  "^channel@[0-7]$":
> +    type: object
> +    $ref: /schemas/iio/adc/adc.yaml#
> +    description: Properties for a single ADC channel.
> +
> +    properties:
> +      reg:
> +        minimum: 0
> +        maximum: 7
> +        description: The channel index (0-7).
> +
> +      ti,gain:

Use common property units.

https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/property-units.yaml

> +        $ref: /schemas/types.yaml#/definitions/uint32
> +        minimum: 0
> +        maximum: 5
> +        description:
> +          Programmable gain amplifier configuration, as described in the PGA
> +          Config Register Field description. If not present, the default is
> +          used.
> +
> +      ti,datarate:

Use common property units.

> +        $ref: /schemas/types.yaml#/definitions/uint32
> +        minimum: 0
> +        maximum: 7
> +        description:
> +          Data rate configuration, as described in the DR Config Register Field
> +          description. If not present, the default is used.

default:

> +
> +    required:
> +      - reg
> +
> +    additionalProperties: false
> +
> +allOf:
> +  - $ref: /schemas/spi/spi-peripheral-props.yaml#
> +
> +  - if:
> +    properties:
> +      compatible:
> +        contains:
> +          const: ti,ads1018
> +    then:
> +      patternProperties:
> +        "^channel@[0-7]$":
> +          properties:
> +            ti,datarate:
> +              maximum: 6
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    spi0 {

spi

> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        ads1118@0 {


Node names should be generic. See also an explanation and list of
examples (not exhaustive) in DT specification:
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
If you cannot find a name matching your device, please check in kernel
sources for similar cases or you can grow the spec (via pull request to
DT spec repo).

e.g. adc


> +            compatible = "ti,ads1118";
Best regards,
Krzysztof

Re: [PATCH 1/2] dt-bindings: iio: adc: Add TI ADS1018/ADS1118

[Kurt Borja]

Hi Krzysztof,

On Fri Nov 21, 2025 at 2:10 PM -05, Krzysztof Kozlowski wrote:
> On 21/11/2025 18:16, Kurt Borja wrote:
>> Add documentation for Texas Instruments ADS1018 and ADS1118
>> analog-to-digital converters.
>> 
>> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
>
> You did not test it before sending, so no full review but few nits to
> save you one round of reviews:

My bad! I will fix the errors. Thanks!

>
>> ---
>>  .../devicetree/bindings/iio/adc/ti,ads1118.yaml    | 132 +++++++++++++++++++++
>>  1 file changed, 132 insertions(+)
>> 
>> diff --git a/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml b/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml
>> new file mode 100644
>> index 000000000000..eb7228ed6ddb
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml
>> @@ -0,0 +1,132 @@
>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/iio/adc/ti,ads1118.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: TI ADS1018/ADS1118 SPI analog to digital converter
>> +
>> +maintainers:
>> +  - Kurt Borja <kuurtb@gmail.com>
>> +
>> +description: |
>> +  The ADS1018/ADS1118 is a precision, low-power, 12-bit or 16-bit, noise-free,
>> +  analog-to-digital converter (ADC). It integrates a programmable gain amplifier
>> +  (PGA), voltage reference, oscillator and high-accuracy temperature sensor.
>> +
>> +  Datasheets:
>> +    - ADS1018: https://www.ti.com/lit/ds/symlink/ads1018.pdf
>> +    - ADS1118: https://www.ti.com/lit/ds/symlink/ads1118.pdf
>> +
>> +properties:
>> +  compatible:
>> +    enum:
>> +      - ti,ads1018
>> +      - ti,ads1118
>> +
>> +  reg:
>> +    maxitems: 1
>> +
>> +  interrupts:
>> +    description: DOUT/DRDY (Data Out/Data Ready) line.
>> +    maxitems: 1
>> +
>> +  drdy-gpios:
>> +    description:
>> +      Extra GPIO line connected to DOUT/DRDY (Data Out/Data Ready). This allows
>> +      distinguishing between latched and real DRDY IRQs.
>
> I have feeling that you miss proper handling of IRQs (e.g. active level)
> on your board.

Can you elaborate? Should I specify active level here?

>
>> +    maxitems: 1
>> +
>> +  '#address-cells':
>> +    const: 1
>> +
>> +  '#size-cells':
>> +    const: 0
>> +
>> +  '#io-channel-cells':
>> +    const: 1
>> +
>> +required:
>
> This goes after patternProperties.
>
>> +  - compatible
>> +  - reg
>> +  - drdy-gpios
>> +  - '#address-cells'
>> +  - '#size-cells'
>> +
>> +patternProperties:
>> +  "^channel@[0-7]$":
>> +    type: object
>> +    $ref: /schemas/iio/adc/adc.yaml#
>> +    description: Properties for a single ADC channel.
>> +
>> +    properties:
>> +      reg:
>> +        minimum: 0
>> +        maximum: 7
>> +        description: The channel index (0-7).
>> +
>> +      ti,gain:
>
> Use common property units.
>
> https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/property-units.yaml
>
>> +        $ref: /schemas/types.yaml#/definitions/uint32
>> +        minimum: 0
>> +        maximum: 5
>> +        description:
>> +          Programmable gain amplifier configuration, as described in the PGA
>> +          Config Register Field description. If not present, the default is
>> +          used.
>> +
>> +      ti,datarate:
>
> Use common property units.
>
>> +        $ref: /schemas/types.yaml#/definitions/uint32
>> +        minimum: 0
>> +        maximum: 7
>> +        description:
>> +          Data rate configuration, as described in the DR Config Register Field
>> +          description. If not present, the default is used.
>
> default:
>
>> +
>> +    required:
>> +      - reg
>> +
>> +    additionalProperties: false
>> +
>> +allOf:
>> +  - $ref: /schemas/spi/spi-peripheral-props.yaml#
>> +
>> +  - if:
>> +    properties:
>> +      compatible:
>> +        contains:
>> +          const: ti,ads1018
>> +    then:
>> +      patternProperties:
>> +        "^channel@[0-7]$":
>> +          properties:
>> +            ti,datarate:
>> +              maximum: 6
>> +
>> +unevaluatedProperties: false
>> +
>> +examples:
>> +  - |
>> +    spi0 {
>
> spi
>
>> +        #address-cells = <1>;
>> +        #size-cells = <0>;
>> +
>> +        ads1118@0 {
>
>
> Node names should be generic. See also an explanation and list of
> examples (not exhaustive) in DT specification:
> https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
> If you cannot find a name matching your device, please check in kernel
> sources for similar cases or you can grow the spec (via pull request to
> DT spec repo).
>
> e.g. adc
>
>
>> +            compatible = "ti,ads1118";
> Best regards,
> Krzysztof

Ack for the rest. Thank you!


-- 
 ~ Kurt

Re: [PATCH 1/2] dt-bindings: iio: adc: Add TI ADS1018/ADS1118

[David Lechner]

On 11/21/25 2:56 PM, Kurt Borja wrote:
> Hi Krzysztof,
> 
> On Fri Nov 21, 2025 at 2:10 PM -05, Krzysztof Kozlowski wrote:
>> On 21/11/2025 18:16, Kurt Borja wrote:
>>> Add documentation for Texas Instruments ADS1018 and ADS1118
>>> analog-to-digital converters.
>>>
>>> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
>>
>> You did not test it before sending, so no full review but few nits to
>> save you one round of reviews:
> 
> My bad! I will fix the errors. Thanks!
> 

...

>>> +  interrupts:
>>> +    description: DOUT/DRDY (Data Out/Data Ready) line.
>>> +    maxitems: 1
>>> +
>>> +  drdy-gpios:
>>> +    description:
>>> +      Extra GPIO line connected to DOUT/DRDY (Data Out/Data Ready). This allows
>>> +      distinguishing between latched and real DRDY IRQs.
>>
>> I have feeling that you miss proper handling of IRQs (e.g. active level)
>> on your board.
> 
> Can you elaborate? Should I specify active level here?
> 
>>
The problem is not about the levels. It is rather that the behavior of the
interrupt when disabled/masked is different on different interrupt controllers.

On some controllers, if an event happens while disabled/masked, it "remembers"
that and will trigger the interrupt as soon as it is enabled even if the
condition doesn't exist anymore. Not a great hardware design IMHO, but there
is real hardware that does this.

I think a better wording would be to leave out "latched" and say that
it is needed to be able to distinguish between an interrupt triggered
by the DRDY signal vs. an interrupt triggered by SPI data.

Re: [PATCH 1/2] dt-bindings: iio: adc: Add TI ADS1018/ADS1118

[Kurt Borja]

On Fri Nov 21, 2025 at 5:40 PM -05, David Lechner wrote:
> On 11/21/25 2:56 PM, Kurt Borja wrote:
>> Hi Krzysztof,
>> 
>> On Fri Nov 21, 2025 at 2:10 PM -05, Krzysztof Kozlowski wrote:
>>> On 21/11/2025 18:16, Kurt Borja wrote:
>>>> Add documentation for Texas Instruments ADS1018 and ADS1118
>>>> analog-to-digital converters.
>>>>
>>>> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
>>>
>>> You did not test it before sending, so no full review but few nits to
>>> save you one round of reviews:
>> 
>> My bad! I will fix the errors. Thanks!
>> 
>
> ...
>
>>>> +  interrupts:
>>>> +    description: DOUT/DRDY (Data Out/Data Ready) line.
>>>> +    maxitems: 1
>>>> +
>>>> +  drdy-gpios:
>>>> +    description:
>>>> +      Extra GPIO line connected to DOUT/DRDY (Data Out/Data Ready). This allows
>>>> +      distinguishing between latched and real DRDY IRQs.
>>>
>>> I have feeling that you miss proper handling of IRQs (e.g. active level)
>>> on your board.
>> 
>> Can you elaborate? Should I specify active level here?
>> 
>>>
> The problem is not about the levels. It is rather that the behavior of the
> interrupt when disabled/masked is different on different interrupt controllers.
>
> On some controllers, if an event happens while disabled/masked, it "remembers"
> that and will trigger the interrupt as soon as it is enabled even if the
> condition doesn't exist anymore. Not a great hardware design IMHO, but there
> is real hardware that does this.

I can attest to that. My hardware (RPI 5) does this haha.

>
> I think a better wording would be to leave out "latched" and say that
> it is needed to be able to distinguish between an interrupt triggered
> by the DRDY signal vs. an interrupt triggered by SPI data.

I'll take this wording, thanks.


-- 
 ~ Kurt

Re: [PATCH 1/2] dt-bindings: iio: adc: Add TI ADS1018/ADS1118

[Krzysztof Kozlowski]

On 21/11/2025 23:40, David Lechner wrote:
> On 11/21/25 2:56 PM, Kurt Borja wrote:
>> Hi Krzysztof,
>>
>> On Fri Nov 21, 2025 at 2:10 PM -05, Krzysztof Kozlowski wrote:
>>> On 21/11/2025 18:16, Kurt Borja wrote:
>>>> Add documentation for Texas Instruments ADS1018 and ADS1118
>>>> analog-to-digital converters.
>>>>
>>>> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
>>>
>>> You did not test it before sending, so no full review but few nits to
>>> save you one round of reviews:
>>
>> My bad! I will fix the errors. Thanks!
>>
> 
> ...
> 
>>>> +  interrupts:
>>>> +    description: DOUT/DRDY (Data Out/Data Ready) line.
>>>> +    maxitems: 1
>>>> +
>>>> +  drdy-gpios:
>>>> +    description:
>>>> +      Extra GPIO line connected to DOUT/DRDY (Data Out/Data Ready). This allows
>>>> +      distinguishing between latched and real DRDY IRQs.
>>>
>>> I have feeling that you miss proper handling of IRQs (e.g. active level)
>>> on your board.
>>
>> Can you elaborate? Should I specify active level here?
>>
>>>
> The problem is not about the levels. It is rather that the behavior of the
> interrupt when disabled/masked is different on different interrupt controllers.
> 
> On some controllers, if an event happens while disabled/masked, it "remembers"
> that and will trigger the interrupt as soon as it is enabled even if the
> condition doesn't exist anymore. Not a great hardware design IMHO, but there
> is real hardware that does this.

Isn't it misconfiguration of trigger as I said before? It should be for
example edge, instead of level?

Best regards,
Krzysztof

Re: [PATCH 1/2] dt-bindings: iio: adc: Add TI ADS1018/ADS1118

[David Lechner]

On 11/22/25 3:34 AM, Krzysztof Kozlowski wrote:
> On 21/11/2025 23:40, David Lechner wrote:
>> On 11/21/25 2:56 PM, Kurt Borja wrote:
>>> Hi Krzysztof,
>>>
>>> On Fri Nov 21, 2025 at 2:10 PM -05, Krzysztof Kozlowski wrote:
>>>> On 21/11/2025 18:16, Kurt Borja wrote:
>>>>> Add documentation for Texas Instruments ADS1018 and ADS1118
>>>>> analog-to-digital converters.
>>>>>
>>>>> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
>>>>
>>>> You did not test it before sending, so no full review but few nits to
>>>> save you one round of reviews:
>>>
>>> My bad! I will fix the errors. Thanks!
>>>
>>
>> ...
>>
>>>>> +  interrupts:
>>>>> +    description: DOUT/DRDY (Data Out/Data Ready) line.
>>>>> +    maxitems: 1
>>>>> +
>>>>> +  drdy-gpios:
>>>>> +    description:
>>>>> +      Extra GPIO line connected to DOUT/DRDY (Data Out/Data Ready). This allows
>>>>> +      distinguishing between latched and real DRDY IRQs.
>>>>
>>>> I have feeling that you miss proper handling of IRQs (e.g. active level)
>>>> on your board.
>>>
>>> Can you elaborate? Should I specify active level here?
>>>
>>>>
>> The problem is not about the levels. It is rather that the behavior of the
>> interrupt when disabled/masked is different on different interrupt controllers.
>>
>> On some controllers, if an event happens while disabled/masked, it "remembers"
>> that and will trigger the interrupt as soon as it is enabled even if the
>> condition doesn't exist anymore. Not a great hardware design IMHO, but there
>> is real hardware that does this.
> 
> Isn't it misconfiguration of trigger as I said before? It should be for
> example edge, instead of level?
> 
> Best regards,
> Krzysztof

No. It it still works like this for edge triggers.

Re: [PATCH 1/2] dt-bindings: iio: adc: Add TI ADS1018/ADS1118

[Krzysztof Kozlowski]

On 22/11/2025 16:09, David Lechner wrote:
>>> ...
>>>
>>>>>> +  interrupts:
>>>>>> +    description: DOUT/DRDY (Data Out/Data Ready) line.
>>>>>> +    maxitems: 1
>>>>>> +
>>>>>> +  drdy-gpios:
>>>>>> +    description:
>>>>>> +      Extra GPIO line connected to DOUT/DRDY (Data Out/Data Ready). This allows
>>>>>> +      distinguishing between latched and real DRDY IRQs.
>>>>>
>>>>> I have feeling that you miss proper handling of IRQs (e.g. active level)
>>>>> on your board.
>>>>
>>>> Can you elaborate? Should I specify active level here?
>>>>
>>>>>
>>> The problem is not about the levels. It is rather that the behavior of the
>>> interrupt when disabled/masked is different on different interrupt controllers.
>>>
>>> On some controllers, if an event happens while disabled/masked, it "remembers"
>>> that and will trigger the interrupt as soon as it is enabled even if the
>>> condition doesn't exist anymore. Not a great hardware design IMHO, but there
>>> is real hardware that does this.
>>
>> Isn't it misconfiguration of trigger as I said before? It should be for
>> example edge, instead of level?
>>
>> Best regards,
>> Krzysztof
> 
> No. It it still works like this for edge triggers.

OK, I still have doubts because it feels like we are adding workaround
for controller issues in device bindings. I don't recall how this was
solved (or if it was at all) in other cases, so fine for now for me.


Best regards,
Krzysztof

Re: [PATCH 1/2] dt-bindings: iio: adc: Add TI ADS1018/ADS1118

[David Lechner]

On 11/21/25 11:16 AM, Kurt Borja wrote:
> Add documentation for Texas Instruments ADS1018 and ADS1118
> analog-to-digital converters.
> 
> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
> ---
>  .../devicetree/bindings/iio/adc/ti,ads1118.yaml    | 132 +++++++++++++++++++++
>  1 file changed, 132 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml b/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml
> new file mode 100644
> index 000000000000..eb7228ed6ddb
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml

I like to make the file name match the lowest number. That way it matches
the first item in the compatible list.

> @@ -0,0 +1,132 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)

Better to be specific with GPL-2.0-only or GPL-2.0-or-later (your choice).

> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/adc/ti,ads1118.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: TI ADS1018/ADS1118 SPI analog to digital converter
> +
> +maintainers:
> +  - Kurt Borja <kuurtb@gmail.com>
> +
> +description: |
> +  The ADS1018/ADS1118 is a precision, low-power, 12-bit or 16-bit, noise-free,
> +  analog-to-digital converter (ADC). It integrates a programmable gain amplifier
> +  (PGA), voltage reference, oscillator and high-accuracy temperature sensor.
> +
> +  Datasheets:
> +    - ADS1018: https://www.ti.com/lit/ds/symlink/ads1018.pdf
> +    - ADS1118: https://www.ti.com/lit/ds/symlink/ads1118.pdf
> +
> +properties:
> +  compatible:
> +    enum:
> +      - ti,ads1018
> +      - ti,ads1118
> +
> +  reg:
> +    maxitems: 1

We know the max SCLK rate from the datasheet, so we can add:

spi-max-frequency:
  maximum: 4000000

And we need to explicitly mention this one (it isn't part of
spi-peripheral-props.yaml but rather comes from spi-controller.yaml):

spi-cpha: true

> +
> +  interrupts:
> +    description: DOUT/DRDY (Data Out/Data Ready) line.
> +    maxitems: 1
> +
> +  drdy-gpios:
> +    description:
> +      Extra GPIO line connected to DOUT/DRDY (Data Out/Data Ready). This allows
> +      distinguishing between latched and real DRDY IRQs.
> +    maxitems: 1
> +
> +  '#address-cells':
> +    const: 1
> +
> +  '#size-cells':
> +    const: 0
> +
> +  '#io-channel-cells':
> +    const: 1
> +

All chips need power, so we should have:

vdd-supply: true

and make it required.

> +required:
> +  - compatible
> +  - reg
> +  - drdy-gpios

The chip can be used without needing the DRDY signal, so drdy-gpios and
interrupts should not be required.

> +  - '#address-cells'
> +  - '#size-cells'
> +
> +patternProperties:
> +  "^channel@[0-7]$":
> +    type: object
> +    $ref: /schemas/iio/adc/adc.yaml#
> +    description: Properties for a single ADC channel.
> +
> +    properties:
> +      reg:
> +        minimum: 0
> +        maximum: 7
> +        description: The channel index (0-7).
> +
> +      ti,gain:
> +        $ref: /schemas/types.yaml#/definitions/uint32
> +        minimum: 0
> +        maximum: 5
> +        description:
> +          Programmable gain amplifier configuration, as described in the PGA
> +          Config Register Field description. If not present, the default is
> +          used.

The gain is programmable, so normally, we would set that by writing
to the in_voltageY_scale attribute rather than hard-coding it in the
devicetree.

> +
> +      ti,datarate:
> +        $ref: /schemas/types.yaml#/definitions/uint32
> +        minimum: 0
> +        maximum: 7
> +        description:
> +          Data rate configuration, as described in the DR Config Register Field
> +          description. If not present, the default is used.

Likewise, the data rate should be set at runtime using a
sampling_frequency attribute rather than being hard-coded
in the devicetree.

> +
> +    required:
> +      - reg
> +
> +    additionalProperties: false
> +
So we shouldn't need explicit channel properties at this time.

Re: [PATCH 1/2] dt-bindings: iio: adc: Add TI ADS1018/ADS1118

[Kurt Borja]

On Fri Nov 21, 2025 at 5:32 PM -05, David Lechner wrote:
> On 11/21/25 11:16 AM, Kurt Borja wrote:
>> Add documentation for Texas Instruments ADS1018 and ADS1118
>> analog-to-digital converters.
>> 
>> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
>> ---
>>  .../devicetree/bindings/iio/adc/ti,ads1118.yaml    | 132 +++++++++++++++++++++
>>  1 file changed, 132 insertions(+)
>> 
>> diff --git a/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml b/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml
>> new file mode 100644
>> index 000000000000..eb7228ed6ddb
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml
>
> I like to make the file name match the lowest number. That way it matches
> the first item in the compatible list.
>
>> @@ -0,0 +1,132 @@
>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>
> Better to be specific with GPL-2.0-only or GPL-2.0-or-later (your choice).

I will go for GPL-2.0-only on both files.

>
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/iio/adc/ti,ads1118.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: TI ADS1018/ADS1118 SPI analog to digital converter
>> +
>> +maintainers:
>> +  - Kurt Borja <kuurtb@gmail.com>
>> +
>> +description: |
>> +  The ADS1018/ADS1118 is a precision, low-power, 12-bit or 16-bit, noise-free,
>> +  analog-to-digital converter (ADC). It integrates a programmable gain amplifier
>> +  (PGA), voltage reference, oscillator and high-accuracy temperature sensor.
>> +
>> +  Datasheets:
>> +    - ADS1018: https://www.ti.com/lit/ds/symlink/ads1018.pdf
>> +    - ADS1118: https://www.ti.com/lit/ds/symlink/ads1118.pdf
>> +
>> +properties:
>> +  compatible:
>> +    enum:
>> +      - ti,ads1018
>> +      - ti,ads1118
>> +
>> +  reg:
>> +    maxitems: 1
>
> We know the max SCLK rate from the datasheet, so we can add:
>
> spi-max-frequency:
>   maximum: 4000000
>
> And we need to explicitly mention this one (it isn't part of
> spi-peripheral-props.yaml but rather comes from spi-controller.yaml):
>
> spi-cpha: true
>
>> +
>> +  interrupts:
>> +    description: DOUT/DRDY (Data Out/Data Ready) line.
>> +    maxitems: 1
>> +
>> +  drdy-gpios:
>> +    description:
>> +      Extra GPIO line connected to DOUT/DRDY (Data Out/Data Ready). This allows
>> +      distinguishing between latched and real DRDY IRQs.
>> +    maxitems: 1
>> +
>> +  '#address-cells':
>> +    const: 1
>> +
>> +  '#size-cells':
>> +    const: 0
>> +
>> +  '#io-channel-cells':
>> +    const: 1
>> +
>
> All chips need power, so we should have:
>
> vdd-supply: true
>
> and make it required.
>
>> +required:
>> +  - compatible
>> +  - reg
>> +  - drdy-gpios
>
> The chip can be used without needing the DRDY signal, so drdy-gpios and
> interrupts should not be required.
>
>> +  - '#address-cells'
>> +  - '#size-cells'
>> +
>> +patternProperties:
>> +  "^channel@[0-7]$":
>> +    type: object
>> +    $ref: /schemas/iio/adc/adc.yaml#
>> +    description: Properties for a single ADC channel.
>> +
>> +    properties:
>> +      reg:
>> +        minimum: 0
>> +        maximum: 7
>> +        description: The channel index (0-7).
>> +
>> +      ti,gain:
>> +        $ref: /schemas/types.yaml#/definitions/uint32
>> +        minimum: 0
>> +        maximum: 5
>> +        description:
>> +          Programmable gain amplifier configuration, as described in the PGA
>> +          Config Register Field description. If not present, the default is
>> +          used.
>
> The gain is programmable, so normally, we would set that by writing
> to the in_voltageY_scale attribute rather than hard-coding it in the
> devicetree.
>
>> +
>> +      ti,datarate:
>> +        $ref: /schemas/types.yaml#/definitions/uint32
>> +        minimum: 0
>> +        maximum: 7
>> +        description:
>> +          Data rate configuration, as described in the DR Config Register Field
>> +          description. If not present, the default is used.
>
> Likewise, the data rate should be set at runtime using a
> sampling_frequency attribute rather than being hard-coded
> in the devicetree.

I actually took this approach from ti-ads1015. I was debating this
myself.

I'll gladly drop these.

>
>> +
>> +    required:
>> +      - reg
>> +
>> +    additionalProperties: false
>> +
> So we shouldn't need explicit channel properties at this time.

Ack for the rest of comments.


-- 
 ~ Kurt

[PATCH 2/2] iio: adc: Add ti-ads1x18 driver

[Kurt Borja]

Add ti-ads1x18 driver for Texas Instruments ADS1018 and ADS1118 SPI
analog-to-digital converters.

These devices support a data-ready IRQ, which is shared with the MOSI
line. Due to this peculiarity, interrupt and IIO trigger design is
heavily inspired in ad_sigma_delta drivers. The IRQ is only enabled when
waiting for data and an additional GPIO is needed to check if it isn't a
latched pending interrupt.

Signed-off-by: Kurt Borja <kuurtb@gmail.com>
---
 MAINTAINERS                  |   7 +
 drivers/iio/adc/Kconfig      |  12 +
 drivers/iio/adc/Makefile     |   1 +
 drivers/iio/adc/ti-ads1x18.c | 919 +++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 939 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 31d98efb1ad1..f9f0983d5d6f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -25646,6 +25646,13 @@ S:	Maintained
 F:	Documentation/devicetree/bindings/iio/adc/ti,ads1119.yaml
 F:	drivers/iio/adc/ti-ads1119.c
 
+TI ADS1X18 ADC DRIVER
+M:	Kurt Borja <kuurtb@gmail.com>
+L:	linux-iio@vger.kernel.org
+S:	Maintained
+F:	Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml
+F:	drivers/iio/adc/ti-ads1x18.c
+
 TI ADS7924 ADC DRIVER
 M:	Hugo Villeneuve <hvilleneuve@dimonoff.com>
 L:	linux-iio@vger.kernel.org
diff --git a/drivers/iio/adc/Kconfig b/drivers/iio/adc/Kconfig
index 58da8255525e..0d3229a67af8 100644
--- a/drivers/iio/adc/Kconfig
+++ b/drivers/iio/adc/Kconfig
@@ -1686,6 +1686,18 @@ config TI_ADS1119
          This driver can also be built as a module. If so, the module will be
          called ti-ads1119.
 
+config TI_ADS1X18
+       tristate "Texas Instruments ADS1119 ADC"
+       depends on SPI
+       select IIO_BUFFER
+       select IIO_TRIGGERED_BUFFER
+       help
+         If you say yes here you get support for Texas Instruments ADS1X18
+         ADC chips.
+
+         This driver can also be built as a module. If so, the module will be
+         called ti-ads1x18.
+
 config TI_ADS124S08
 	tristate "Texas Instruments ADS124S08"
 	depends on SPI
diff --git a/drivers/iio/adc/Makefile b/drivers/iio/adc/Makefile
index 7cc8f9a12f76..ab3b52307482 100644
--- a/drivers/iio/adc/Makefile
+++ b/drivers/iio/adc/Makefile
@@ -147,6 +147,7 @@ obj-$(CONFIG_TI_ADC161S626) += ti-adc161s626.o
 obj-$(CONFIG_TI_ADS1015) += ti-ads1015.o
 obj-$(CONFIG_TI_ADS1100) += ti-ads1100.o
 obj-$(CONFIG_TI_ADS1119) += ti-ads1119.o
+obj-$(CONFIG_TI_ADS1X18) += ti-ads1x18.o
 obj-$(CONFIG_TI_ADS124S08) += ti-ads124s08.o
 obj-$(CONFIG_TI_ADS1298) += ti-ads1298.o
 obj-$(CONFIG_TI_ADS131E08) += ti-ads131e08.o
diff --git a/drivers/iio/adc/ti-ads1x18.c b/drivers/iio/adc/ti-ads1x18.c
new file mode 100644
index 000000000000..1bf4fe34a825
--- /dev/null
+++ b/drivers/iio/adc/ti-ads1x18.c
@@ -0,0 +1,919 @@
+// SPDX-License-Identifier: GPL-2.0-only
+/*
+ * Texas Instruments ADS1X18 ADC driver
+ *
+ * Copyright (C) 2025 Kurt Borja <kuurtb@gmail.com>
+ */
+
+#include <linux/array_size.h>
+#include <linux/bitfield.h>
+#include <linux/bits.h>
+#include <linux/bitmap.h>
+#include <linux/byteorder/generic.h>
+#include <linux/cleanup.h>
+#include <linux/completion.h>
+#include <linux/dev_printk.h>
+#include <linux/device.h>
+#include <linux/device/devres.h>
+#include <linux/errno.h>
+#include <linux/find.h>
+#include <linux/gfp_types.h>
+#include <linux/gpio/consumer.h>
+#include <linux/interrupt.h>
+#include <linux/jiffies.h>
+#include <linux/module.h>
+#include <linux/mod_devicetable.h>
+#include <linux/mutex.h>
+#include <linux/pm.h>
+#include <linux/regmap.h>
+#include <linux/spinlock.h>
+#include <linux/spi/spi.h>
+#include <linux/units.h>
+
+#include <linux/iio/buffer.h>
+#include <linux/iio/iio.h>
+#include <linux/iio/trigger.h>
+#include <linux/iio/triggered_buffer.h>
+#include <linux/iio/trigger_consumer.h>
+
+#define ADS1X18_CFG_DEFAULT		0x058b
+
+#define ADS1X18_CFG_OS_TRIG		BIT_U16(15)
+#define ADS1X18_CFG_TS_MODE_EN		BIT_U16(4)
+#define ADS1X18_CFG_PULL_UP		BIT_U16(3)
+#define ADS1X18_CFG_NOP			BIT_U16(1)
+#define ADS1X18_CFG_VALID		(ADS1X18_CFG_PULL_UP | ADS1X18_CFG_NOP)
+
+#define ADS1X18_CFG_MUX_MASK		GENMASK_U16(14, 12)
+#define ADS1X18_AIN0_AIN1_ADDR		0
+#define ADS1X18_AIN0_AIN3_ADDR		1
+#define ADS1X18_AIN1_AIN3_ADDR		2
+#define ADS1X18_AIN2_AIN3_ADDR		3
+#define ADS1X18_AIN0_GND_ADDR		4
+#define ADS1X18_AIN1_GND_ADDR		5
+#define ADS1X18_AIN2_GND_ADDR		6
+#define ADS1X18_AIN3_GND_ADDR		7
+#define ADS1X18_TEMP_ADDR		8
+#define ADS1X18_TIMESTAMP_ADDR		9
+
+#define ADS1X18_CFG_PGA_MASK		GENMASK_U16(11, 9)
+#define ADS1X18_PGA_MODE_0		0
+#define ADS1X18_PGA_MODE_1		1
+#define ADS1X18_PGA_MODE_2		2
+#define ADS1X18_PGA_MODE_3		3
+#define ADS1X18_PGA_MODE_4		4
+#define ADS1X18_PGA_MODE_5		5
+#define ADS1X18_PGA_DEFAULT		ADS1X18_PGA_MODE_2
+
+#define ADS1X18_CFG_MODE_MASK		GENMASK_U16(8, 8)
+#define ADS1X18_MODE_CONTINUOUS		0
+#define ADS1X18_MODE_ONESHOT		1
+
+#define ADS1X18_CFG_DRATE_MASK		GENMASK_U16(7, 5)
+#define ADS1X18_DRATE_MODE_0		0
+#define ADS1X18_DRATE_MODE_1		1
+#define ADS1X18_DRATE_MODE_2		2
+#define ADS1X18_DRATE_MODE_3		3
+#define ADS1X18_DRATE_MODE_4		4
+#define ADS1X18_DRATE_MODE_5		5
+#define ADS1X18_DRATE_MODE_6		6
+#define ADS1X18_DRATE_MODE_7		7
+#define ADS1X18_DRATE_DEFAULT		ADS1X18_DRATE_MODE_4
+
+#define ADS1X18_MAX_ADC_ADDR		7
+#define ADS1X18_MAX_CHANNELS		9
+
+struct ads1x18_chan_data {
+	unsigned int pga_mode:3;
+	unsigned int drate_mode:3;
+};
+
+struct ads1x18_chip_info {
+	const char *name;
+
+	const struct iio_chan_spec *channels;
+	unsigned long channels_sz;
+
+	const int *sps_table;
+	unsigned long sps_table_sz;
+	const int (*fsr_table)[2];
+	unsigned long fsr_table_sz;
+	const int temp_scale[2];
+};
+
+struct ads1x18 {
+	struct spi_device *spi;
+	struct iio_dev *indio_dev;
+	struct iio_trigger *indio_trig;
+
+	struct gpio_desc *drdy_gpiod;
+	int drdy_irq;
+
+	u16 tx_buf[2] __aligned(IIO_DMA_MINALIGN);
+	u16 rx_buf[2];
+	struct spi_transfer xfer;
+	struct spi_message message;
+	struct completion data_ready;
+	struct mutex msg_lock; /* Protects message transfers */
+
+	unsigned int restore_mode:1;
+
+	unsigned long bufidx_to_addr[ADS1X18_MAX_CHANNELS];
+	struct ads1x18_chan_data channels[ADS1X18_MAX_CHANNELS];
+
+	const struct ads1x18_chip_info *chip_info;
+};
+
+#define ADS1X18_VOLT_CHANNEL(_addr, _chan, _chan2, _diff, _realbits) {		\
+	.type = IIO_VOLTAGE,							\
+	.channel = _chan,							\
+	.channel2 = _chan2,							\
+	.address = _addr,							\
+	.scan_type = {								\
+		.sign = 's',							\
+		.realbits = _realbits,						\
+		.storagebits = 16,						\
+		.shift = 16 - _realbits,					\
+	},									\
+	.info_mask_separate = BIT(IIO_CHAN_INFO_RAW) |				\
+			      BIT(IIO_CHAN_INFO_SCALE) |			\
+			      BIT(IIO_CHAN_INFO_SAMP_FREQ),			\
+	.info_mask_shared_by_type_available = BIT(IIO_CHAN_INFO_SCALE),		\
+	.info_mask_shared_by_all_available = BIT(IIO_CHAN_INFO_SAMP_FREQ),	\
+	.modified = _diff,							\
+	.indexed = true,							\
+	.differential = _diff,							\
+}
+
+#define ADS1X18_TEMP_CHANNEL(_realbits)	{					\
+	.type = IIO_TEMP,							\
+	.channel = 0,								\
+	.address = ADS1X18_TEMP_ADDR,						\
+	.scan_type = {								\
+		.sign = 's',							\
+		.realbits = _realbits,						\
+		.storagebits = 16,						\
+		.shift = 16 - _realbits,					\
+	},									\
+	.info_mask_separate = BIT(IIO_CHAN_INFO_RAW) |				\
+			      BIT(IIO_CHAN_INFO_SCALE) |			\
+			      BIT(IIO_CHAN_INFO_SAMP_FREQ),			\
+	.info_mask_shared_by_all_available = BIT(IIO_CHAN_INFO_SAMP_FREQ),	\
+}
+
+static const struct iio_chan_spec ads1118_iio_channels[] = {
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_AIN1_ADDR, 0, 1, true, 16),
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_AIN3_ADDR, 0, 3, true, 16),
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN1_AIN3_ADDR, 1, 3, true, 16),
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN2_AIN3_ADDR, 2, 3, true, 16),
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_GND_ADDR, 0, 0, false, 16),
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN1_GND_ADDR, 1, 0, false, 16),
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN2_GND_ADDR, 2, 0, false, 16),
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN3_GND_ADDR, 3, 0, false, 16),
+	ADS1X18_TEMP_CHANNEL(14),
+	IIO_CHAN_SOFT_TIMESTAMP(ADS1X18_TIMESTAMP_ADDR),
+};
+
+static const struct iio_chan_spec ads1018_iio_channels[] = {
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_AIN1_ADDR, 0, 1, true, 12),
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_AIN3_ADDR, 0, 3, true, 12),
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN1_AIN3_ADDR, 1, 3, true, 12),
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN2_AIN3_ADDR, 2, 3, true, 12),
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_GND_ADDR, 0, 0, false, 12),
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN1_GND_ADDR, 1, 0, false, 12),
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN2_GND_ADDR, 2, 0, false, 12),
+	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN3_GND_ADDR, 3, 0, false, 12),
+	ADS1X18_TEMP_CHANNEL(12),
+	IIO_CHAN_SOFT_TIMESTAMP(ADS1X18_TIMESTAMP_ADDR),
+};
+
+static unsigned int ads1x18_get_drate_mode(struct ads1x18 *ads1x18,
+					   unsigned int address)
+{
+	return ads1x18->channels[address].drate_mode;
+}
+
+static unsigned int ads1x18_get_pga_mode(struct ads1x18 *ads1x18,
+					 unsigned int address)
+{
+	return ads1x18->channels[address].pga_mode;
+}
+
+static void ads1x18_set_drate_mode(struct ads1x18 *ads1x18, unsigned int address,
+				   unsigned int val)
+{
+	ads1x18->channels[address].drate_mode = val;
+}
+
+static void ads1x18_set_pga_mode(struct ads1x18 *ads1x18, unsigned int address,
+				 unsigned int val)
+{
+	ads1x18->channels[address].pga_mode = val;
+}
+
+static unsigned long ads1x18_calc_timeout(struct ads1x18 *ads1x18,
+					  unsigned int drate_mode)
+{
+	const struct ads1x18_chip_info *chip_info = ads1x18->chip_info;
+	unsigned long timeout;
+	unsigned int sps;
+
+	sps = chip_info->sps_table[drate_mode];
+	timeout = DIV_ROUND_UP(MICROHZ_PER_HZ, sps);
+
+	return usecs_to_jiffies(timeout * 2);
+}
+
+static int __ads1x18_read_conver(struct ads1x18 *ads1x18, u16 *cnv)
+{
+	int ret;
+
+	ads1x18->tx_buf[0] = 0;
+	ads1x18->tx_buf[1] = 0;
+	ret = spi_sync_locked(ads1x18->spi, &ads1x18->message);
+	if (ret)
+		return ret;
+
+	*cnv = be16_to_cpu(ads1x18->rx_buf[0]);
+
+	return 0;
+}
+
+static int __ads1x18_write_config(struct ads1x18 *ads1x18, u16 cfg)
+{
+	ads1x18->tx_buf[0] = cpu_to_be16(cfg);
+	ads1x18->tx_buf[1] = 0;
+
+	return spi_sync_locked(ads1x18->spi, &ads1x18->message);
+}
+
+static int ads1x18_read_conver(struct ads1x18 *ads1x18, u16 *cnv)
+{
+	int ret;
+
+	spi_bus_lock(ads1x18->spi->controller);
+	ret = __ads1x18_read_conver(ads1x18, cnv);
+	spi_bus_unlock(ads1x18->spi->controller);
+
+	return ret;
+}
+
+static int ads1x18_write_config(struct ads1x18 *ads1x18, u16 cfg)
+{
+	int ret;
+
+	spi_bus_lock(ads1x18->spi->controller);
+	ret = __ads1x18_write_config(ads1x18, cfg);
+	spi_bus_unlock(ads1x18->spi->controller);
+
+	return ret;
+}
+
+static int ads1x18_oneshot(struct ads1x18 *ads1x18,
+			   struct iio_chan_spec const *chan, int *val)
+{
+	unsigned int drate = ads1x18_get_drate_mode(ads1x18, chan->address);
+	unsigned int pga = ads1x18_get_pga_mode(ads1x18, chan->address);
+	unsigned long timeout = ads1x18_calc_timeout(ads1x18, drate);
+	u16 cnv, cfg = 0;
+	int ret;
+
+	reinit_completion(&ads1x18->data_ready);
+
+	cfg |= ADS1X18_CFG_VALID;
+	cfg |= ADS1X18_CFG_OS_TRIG;
+	cfg |= FIELD_PREP(ADS1X18_CFG_MUX_MASK, chan->address);
+	cfg |= FIELD_PREP(ADS1X18_CFG_PGA_MASK, pga);
+	cfg |= FIELD_PREP(ADS1X18_CFG_MODE_MASK, ADS1X18_MODE_ONESHOT);
+	cfg |= FIELD_PREP(ADS1X18_CFG_DRATE_MASK, drate);
+	if (chan->type == IIO_TEMP)
+		cfg |= ADS1X18_CFG_TS_MODE_EN;
+
+	ret = __ads1x18_write_config(ads1x18, cfg);
+	if (ret)
+		return ret;
+	enable_irq(ads1x18->drdy_irq);
+
+	if (!wait_for_completion_timeout(&ads1x18->data_ready, timeout)) {
+		disable_irq(ads1x18->drdy_irq);
+		return -ETIMEDOUT;
+	}
+	disable_irq(ads1x18->drdy_irq);
+
+	ret = __ads1x18_read_conver(ads1x18, &cnv);
+	if (ret)
+		return ret;
+
+	cnv >>= chan->scan_type.shift;
+	*val = sign_extend32(cnv, chan->scan_type.realbits - 1);
+
+	return ret;
+}
+
+static int
+ads1x18_read_raw(struct iio_dev *indio_dev, struct iio_chan_spec const *chan,
+		 int *val, int *val2, long mask)
+{
+	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
+	struct ads1x18_chan_data *chan_info = &ads1x18->channels[chan->address];
+	const struct ads1x18_chip_info *chip_info = ads1x18->chip_info;
+	int ret;
+
+	guard(mutex)(&ads1x18->msg_lock);
+
+	switch (mask) {
+	case IIO_CHAN_INFO_RAW:
+		if (!iio_device_claim_direct(indio_dev))
+			return -EBUSY;
+		/* CS needs to remain asserted until dataready IRQ */
+		spi_bus_lock(ads1x18->spi->controller);
+
+		ret = ads1x18_oneshot(ads1x18, chan, val);
+
+		spi_bus_unlock(ads1x18->spi->controller);
+		iio_device_release_direct(indio_dev);
+
+		if (ret)
+			return ret;
+
+		return IIO_VAL_INT;
+
+	case IIO_CHAN_INFO_SCALE:
+		switch (chan->type) {
+		case IIO_VOLTAGE:
+			*val = chip_info->fsr_table[chan_info->pga_mode][0];
+			*val2 = chip_info->fsr_table[chan_info->pga_mode][1];
+			return IIO_VAL_INT_PLUS_NANO;
+
+		case IIO_TEMP:
+			*val = chip_info->temp_scale[0];
+			*val2 = chip_info->temp_scale[1];
+			return IIO_VAL_INT_PLUS_MICRO;
+
+		default:
+			return -EOPNOTSUPP;
+		}
+
+	case IIO_CHAN_INFO_SAMP_FREQ:
+		*val = chip_info->sps_table[chan_info->drate_mode];
+		return IIO_VAL_INT;
+
+	default:
+		return -EOPNOTSUPP;
+	}
+}
+
+static int
+ads1x18_read_avail(struct iio_dev *indio_dev, struct iio_chan_spec const *chan,
+		   const int **vals, int *type, int *length, long mask)
+{
+	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
+
+	switch (mask) {
+	case IIO_CHAN_INFO_SCALE:
+		*type = IIO_VAL_INT_PLUS_NANO;
+		*vals = (const int *)ads1x18->chip_info->fsr_table;
+		*length = ads1x18->chip_info->fsr_table_sz * 2;
+		return IIO_AVAIL_LIST;
+
+	case IIO_CHAN_INFO_SAMP_FREQ:
+		*type = IIO_VAL_INT;
+		*vals = ads1x18->chip_info->sps_table;
+		*length = ads1x18->chip_info->sps_table_sz;
+		return IIO_AVAIL_LIST;
+
+	default:
+		return -EOPNOTSUPP;
+	}
+}
+
+static int
+ads1x18_write_raw(struct iio_dev *indio_dev, struct iio_chan_spec const *chan,
+		  int val, int val2, long mask)
+{
+	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
+	const struct ads1x18_chip_info *info = ads1x18->chip_info;
+	unsigned int i = 0;
+
+	guard(mutex)(&ads1x18->msg_lock);
+
+	switch (mask) {
+	case IIO_CHAN_INFO_SCALE:
+		for (; i < info->fsr_table_sz; i++) {
+			if (val != info->fsr_table[i][0] ||
+			    val2 != info->fsr_table[i][1])
+				continue;
+
+			ads1x18_set_pga_mode(ads1x18, chan->address, i);
+			return 0;
+		}
+
+		return -EINVAL;
+
+	case IIO_CHAN_INFO_SAMP_FREQ:
+		for (; i < info->sps_table_sz; i++) {
+			if (val != info->sps_table[i])
+				continue;
+
+			ads1x18_set_drate_mode(ads1x18, chan->address, i);
+			return 0;
+		}
+
+		return -EINVAL;
+
+	default:
+		return -EOPNOTSUPP;
+	}
+}
+
+static int
+ads1x18_write_raw_get_fmt(struct iio_dev *indio_dev,
+			  struct iio_chan_spec const *chan, long mask)
+{
+	switch (mask) {
+	case IIO_CHAN_INFO_SCALE:
+		return IIO_VAL_INT_PLUS_NANO;
+	default:
+		return IIO_VAL_INT_PLUS_MICRO;
+	}
+}
+
+static const struct iio_info ads1x18_iio_info = {
+	.read_raw = ads1x18_read_raw,
+	.read_avail = ads1x18_read_avail,
+	.write_raw = ads1x18_write_raw,
+	.write_raw_get_fmt = ads1x18_write_raw_get_fmt,
+};
+
+static int ads1x18_set_trigger_state(struct iio_trigger *trig, bool state)
+{
+	struct ads1x18 *ads1x18 = iio_trigger_get_drvdata(trig);
+	u16 cnv;
+
+	guard(mutex)(&ads1x18->msg_lock);
+
+	/*
+	 * We need to lock the SPI bus when enabling the trigger to prevent
+	 * another device from taking the CS and DOUT/DRDY lines.
+	 */
+
+	if (state) {
+		spi_bus_lock(ads1x18->spi->controller);
+		enable_irq(ads1x18->drdy_irq);
+
+		/*
+		 * Read once to ensure we are holding the CS line after locking
+		 */
+		return __ads1x18_read_conver(ads1x18, &cnv);
+	}
+
+	disable_irq(ads1x18->drdy_irq);
+	spi_bus_unlock(ads1x18->spi->controller);
+
+	return 0;
+}
+
+static const struct iio_trigger_ops ads1x18_trigger_ops = {
+	.set_trigger_state = ads1x18_set_trigger_state,
+	.validate_device = iio_trigger_validate_own_device,
+};
+
+static int ads1x18_buffer_preenable(struct iio_dev *indio_dev)
+{
+	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
+	unsigned int pga, drate, addr, idx;
+	u16 cfg = 0;
+
+	guard(mutex)(&ads1x18->msg_lock);
+
+	idx = find_first_bit(indio_dev->active_scan_mask,
+			     iio_get_masklength(indio_dev));
+	addr = ads1x18->bufidx_to_addr[idx];
+	pga = ads1x18_get_pga_mode(ads1x18, addr);
+	drate = ads1x18_get_drate_mode(ads1x18, addr);
+
+	cfg |= ADS1X18_CFG_VALID;
+	cfg |= FIELD_PREP(ADS1X18_CFG_MUX_MASK, addr);
+	cfg |= FIELD_PREP(ADS1X18_CFG_PGA_MASK, pga);
+	cfg |= FIELD_PREP(ADS1X18_CFG_MODE_MASK, ADS1X18_MODE_CONTINUOUS);
+	cfg |= FIELD_PREP(ADS1X18_CFG_DRATE_MASK, drate);
+	if (addr == ADS1X18_TEMP_ADDR)
+		cfg |= ADS1X18_CFG_TS_MODE_EN;
+
+	return ads1x18_write_config(ads1x18, cfg);
+}
+
+static int ads1x18_buffer_postdisable(struct iio_dev *indio_dev)
+{
+	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
+
+	guard(mutex)(&ads1x18->msg_lock);
+
+	return ads1x18_write_config(ads1x18, ADS1X18_CFG_DEFAULT);
+}
+
+static bool ads1x18_validate_scan_mask(struct iio_dev *indio_dev,
+				       const unsigned long *mask)
+{
+	return bitmap_weight(mask, iio_get_masklength(indio_dev)) == 1;
+}
+
+static const struct iio_buffer_setup_ops ads1x18_buffer_ops = {
+	.preenable = ads1x18_buffer_preenable,
+	.postdisable = ads1x18_buffer_postdisable,
+	.validate_scan_mask = ads1x18_validate_scan_mask,
+};
+
+static irqreturn_t ads1x18_irq_handler(int irq, void *dev_id)
+{
+	struct ads1x18 *ads1x18 = dev_id;
+
+	/*
+	 * We need to check if the "drdy" pin is actually active or if it's a
+	 * latched pending interrupt.
+	 */
+	if (!gpiod_get_value(ads1x18->drdy_gpiod))
+		return IRQ_HANDLED;
+
+	complete(&ads1x18->data_ready);
+	iio_trigger_poll(ads1x18->indio_trig);
+
+	return IRQ_HANDLED;
+}
+
+static int ads1x18_interrupt_init(struct ads1x18 *ads1x18)
+{
+	const struct ads1x18_chip_info *info = ads1x18->chip_info;
+	struct spi_device *spi = ads1x18->spi;
+
+	ads1x18->drdy_gpiod = devm_gpiod_get(&spi->dev, "drdy", GPIOD_IN);
+	if (IS_ERR(ads1x18->drdy_gpiod))
+		return dev_err_probe(&spi->dev, PTR_ERR(ads1x18->drdy_gpiod),
+				     "Failed to get 'drdy' GPIO.\n");
+
+	ads1x18->drdy_irq = gpiod_to_irq(ads1x18->drdy_gpiod);
+	if (ads1x18->drdy_irq < 0)
+		return dev_err_probe(&spi->dev, ads1x18->drdy_irq,
+				     "Failed to get 'drdy IRQ.\n'");
+
+	/*
+	 * The "data-ready" IRQ line is shared with the MOSI pin, thus we need
+	 * to keep it disabled until we actually request data.
+	 */
+	return devm_request_irq(&spi->dev, ads1x18->drdy_irq,
+				ads1x18_irq_handler, IRQF_NO_AUTOEN,
+				info->name, ads1x18);
+}
+
+static irqreturn_t ads1x18_trigger_handler(int irq, void *p)
+{
+	struct iio_poll_func *pf = p;
+	struct iio_dev *indio_dev = pf->indio_dev;
+	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
+	struct {
+		u16 conv;
+		aligned_s64 ts;
+	} scan;
+	int ret;
+
+	guard(mutex)(&ads1x18->msg_lock);
+
+	if (iio_trigger_using_own(indio_dev)) {
+		disable_irq(ads1x18->drdy_irq);
+		ret = __ads1x18_read_conver(ads1x18, &scan.conv);
+		enable_irq(ads1x18->drdy_irq);
+	} else {
+		ret = ads1x18_read_conver(ads1x18, &scan.conv);
+	}
+
+	if (ret)
+		return IRQ_HANDLED;
+
+	ret = iio_push_to_buffers_with_ts(indio_dev, &scan, sizeof(scan),
+					  pf->timestamp);
+	if (!ret)
+		iio_trigger_notify_done(ads1x18->indio_trig);
+
+	return IRQ_HANDLED;
+}
+
+static int ads1x18_triggered_buffer_init(struct ads1x18 *ads1x18)
+{
+	struct iio_dev *indio_dev = ads1x18->indio_dev;
+	struct spi_device *spi = ads1x18->spi;
+	int ret;
+
+	ads1x18->indio_trig = devm_iio_trigger_alloc(&spi->dev, "%s-dev%d-drdy",
+						     indio_dev->name,
+						     iio_device_id(indio_dev));
+	if (!ads1x18->indio_trig)
+		return -ENOMEM;
+
+	iio_trigger_set_drvdata(ads1x18->indio_trig, ads1x18);
+	ads1x18->indio_trig->ops = &ads1x18_trigger_ops;
+
+	ret = devm_iio_trigger_register(&spi->dev, ads1x18->indio_trig);
+	if (ret)
+		return ret;
+
+	return devm_iio_triggered_buffer_setup(&spi->dev, indio_dev,
+					       iio_pollfunc_store_time,
+					       ads1x18_trigger_handler,
+					       &ads1x18_buffer_ops);
+}
+
+static int ads1x18_message_init(struct ads1x18 *ads1x18)
+{
+	struct spi_device *spi = ads1x18->spi;
+
+	/*
+	 * We need to keep CS asserted to catch "data-ready" interrupts.
+	 * Otherwise the DOUT/DRDY line enters a Hi-Z state and it can't be
+	 * driven by the ADC.
+	 */
+	ads1x18->xfer.cs_change = 1;
+	ads1x18->xfer.tx_buf = ads1x18->tx_buf;
+	ads1x18->xfer.rx_buf = ads1x18->rx_buf;
+	ads1x18->xfer.len = sizeof(ads1x18->tx_buf);
+	spi_message_init_no_memset(&ads1x18->message);
+	spi_message_add_tail(&ads1x18->xfer, &ads1x18->message);
+
+	return devm_spi_optimize_message(&spi->dev, spi, &ads1x18->message);
+}
+
+static int ads1x18_fill_properties(struct ads1x18 *ads1x18,
+				   struct fwnode_handle *handle,
+				   struct iio_chan_spec *chan)
+{
+	const struct ads1x18_chip_info *info = ads1x18->chip_info;
+	struct ads1x18_chan_data *chan_data;
+	u32 val, reg;
+	int ret;
+
+	ret = fwnode_property_read_u32(handle, "reg", &reg);
+	if (ret)
+		return ret;
+	if (reg > ADS1X18_MAX_ADC_ADDR)
+		return dev_err_probe(&ads1x18->spi->dev, -ENXIO,
+				     "%s: Invalid channel address %u.\n",
+				     fwnode_get_name(handle), reg);
+
+	*chan = info->channels[reg];
+
+	chan_data = &ads1x18->channels[reg];
+	chan_data->pga_mode = ADS1X18_PGA_DEFAULT;
+	chan_data->drate_mode = ADS1X18_DRATE_DEFAULT;
+
+	if (fwnode_property_present(handle, "ti,gain")) {
+		ret = fwnode_property_read_u32(handle, "ti,gain", &val);
+		if (ret)
+			return ret;
+		if (val >= info->fsr_table_sz)
+			return dev_err_probe(&ads1x18->spi->dev, -ENXIO,
+					     "%s: ti,gain not in range.",
+					     fwnode_get_name(handle));
+
+		chan_data->pga_mode = val;
+	}
+
+	if (fwnode_property_present(handle, "ti,datarate")) {
+		ret = fwnode_property_read_u32(handle, "ti,datarate", &val);
+		if (ret)
+			return ret;
+		if (val >= info->sps_table_sz)
+			return dev_err_probe(&ads1x18->spi->dev, -ENXIO,
+					     "%s: ti,datarate not in range.",
+					     fwnode_get_name(handle));
+
+		chan_data->drate_mode = val;
+	}
+
+	return 0;
+}
+
+static int ads1x18_channels_init(struct ads1x18 *ads1x18,
+				 const struct ads1x18_chip_info *info,
+				 struct iio_chan_spec **cs)
+{
+	struct device *dev = &ads1x18->spi->dev;
+	struct iio_chan_spec *channels;
+	int ret, nchans, index = 0;
+
+	nchans = device_get_named_child_node_count(dev, "channel");
+	if (!nchans)
+		return dev_err_probe(dev, -ENODEV,
+				     "No ADC channels described.\n");
+
+	channels = devm_kcalloc(dev, nchans + 2, sizeof(*channels), GFP_KERNEL);
+	if (!channels)
+		return -ENOMEM;
+
+	device_for_each_named_child_node_scoped(dev, child, "channel") {
+		ret = ads1x18_fill_properties(ads1x18, child, &channels[index]);
+		if (ret)
+			return ret;
+
+		channels[index].scan_index = index;
+		ads1x18->bufidx_to_addr[index] = channels[index].address;
+		index++;
+	}
+
+	ads1x18->channels[ADS1X18_TEMP_ADDR].drate_mode = ADS1X18_DRATE_DEFAULT;
+	channels[index] = info->channels[ADS1X18_TEMP_ADDR];
+	channels[index].scan_index = index;
+	ads1x18->bufidx_to_addr[index] = channels[index].address;
+	index++;
+
+	channels[index] = info->channels[ADS1X18_TIMESTAMP_ADDR];
+	ads1x18->bufidx_to_addr[index] = channels[index].address;
+
+	*cs = channels;
+
+	return index;
+}
+
+static int ads1x18_spi_probe(struct spi_device *spi)
+{
+	const struct ads1x18_chip_info *info = spi_get_device_match_data(spi);
+	struct iio_chan_spec *channels;
+	struct iio_dev *indio_dev;
+	struct ads1x18 *ads1x18;
+	int num_channels, ret;
+
+	indio_dev = devm_iio_device_alloc(&spi->dev, sizeof(*ads1x18));
+	if (!indio_dev)
+		return -ENOMEM;
+
+	ads1x18 = iio_priv(indio_dev);
+	ads1x18->spi = spi;
+	ads1x18->indio_dev = indio_dev;
+	ads1x18->chip_info = info;
+	mutex_init(&ads1x18->msg_lock);
+	init_completion(&ads1x18->data_ready);
+	spi_set_drvdata(spi, ads1x18);
+
+	num_channels = ads1x18_channels_init(ads1x18, info, &channels);
+	if (num_channels < 0)
+		return num_channels;
+	indio_dev->modes = INDIO_DIRECT_MODE;
+	indio_dev->name = info->name;
+	indio_dev->info = &ads1x18_iio_info;
+	indio_dev->channels = channels;
+	indio_dev->num_channels = num_channels;
+
+	ret = ads1x18_message_init(ads1x18);
+	if (ret)
+		return ret;
+
+	ret = ads1x18_triggered_buffer_init(ads1x18);
+	if (ret)
+		return ret;
+
+	ret = ads1x18_interrupt_init(ads1x18);
+	if (ret)
+		return ret;
+
+	return devm_iio_device_register(&spi->dev, indio_dev);
+}
+
+static int ads1x18_suspend(struct device *dev)
+{
+	struct ads1x18 *ads1x18 = dev_get_drvdata(dev);
+	u16 cfg;
+	int ret;
+
+	guard(mutex)(&ads1x18->msg_lock);
+
+	/* Current config is readback into rx_buf[1] */
+	cfg = be16_to_cpu(ads1x18->rx_buf[1]);
+	if (FIELD_GET(ADS1X18_CFG_MODE_MASK, cfg) == ADS1X18_MODE_ONESHOT)
+		return 0;
+
+	cfg |= FIELD_PREP(ADS1X18_CFG_MODE_MASK, ADS1X18_MODE_ONESHOT);
+	ret = ads1x18_write_config(ads1x18, cfg);
+	if (ret)
+		return ret;
+
+	ads1x18->restore_mode = 1;
+
+	return 0;
+}
+
+static int ads1x18_resume(struct device *dev)
+{
+	struct ads1x18 *ads1x18 = dev_get_drvdata(dev);
+	u16 cfg;
+	int ret;
+
+	guard(mutex)(&ads1x18->msg_lock);
+
+	if (!ads1x18->restore_mode)
+		return 0;
+
+	cfg = be16_to_cpu(ads1x18->rx_buf[1]);
+	FIELD_MODIFY(ADS1X18_CFG_MODE_MASK, &cfg, ADS1X18_MODE_CONTINUOUS);
+	ret = ads1x18_write_config(ads1x18, cfg);
+	if (ret)
+		return ret;
+
+	ads1x18->restore_mode = 0;
+
+	return 0;
+}
+
+static DEFINE_SIMPLE_DEV_PM_OPS(ads1x18_pm_ops, ads1x18_suspend, ads1x18_resume);
+
+static const int ads1118_fsr_table[][2] = {
+	[ADS1X18_PGA_MODE_0] = { 0, 187500 },
+	[ADS1X18_PGA_MODE_1] = { 0, 125000 },
+	[ADS1X18_PGA_MODE_2] = { 0, 62500 },
+	[ADS1X18_PGA_MODE_3] = { 0, 31250 },
+	[ADS1X18_PGA_MODE_4] = { 0, 15625 },
+	[ADS1X18_PGA_MODE_5] = { 0, 7812 }
+};
+
+static const int ads1018_fsr_table[][2] = {
+	[ADS1X18_PGA_MODE_0] = { 0, 3000000 },
+	[ADS1X18_PGA_MODE_1] = { 0, 2000000 },
+	[ADS1X18_PGA_MODE_2] = { 0, 1000000 },
+	[ADS1X18_PGA_MODE_3] = { 0, 500000 },
+	[ADS1X18_PGA_MODE_4] = { 0, 250000 },
+	[ADS1X18_PGA_MODE_5] = { 0, 125000 }
+};
+
+static const unsigned int ads1018_drate_table[] = {
+	[ADS1X18_DRATE_MODE_0] = 128,
+	[ADS1X18_DRATE_MODE_1] = 250,
+	[ADS1X18_DRATE_MODE_2] = 490,
+	[ADS1X18_DRATE_MODE_3] = 920,
+	[ADS1X18_DRATE_MODE_4] = 1600,
+	[ADS1X18_DRATE_MODE_5] = 2400,
+	[ADS1X18_DRATE_MODE_6] = 3300
+};
+
+static const unsigned int ads1118_drate_table[] = {
+	[ADS1X18_DRATE_MODE_0] = 8,
+	[ADS1X18_DRATE_MODE_1] = 16,
+	[ADS1X18_DRATE_MODE_2] = 32,
+	[ADS1X18_DRATE_MODE_3] = 64,
+	[ADS1X18_DRATE_MODE_4] = 128,
+	[ADS1X18_DRATE_MODE_5] = 250,
+	[ADS1X18_DRATE_MODE_6] = 475,
+	[ADS1X18_DRATE_MODE_7] = 860
+};
+
+static const struct ads1x18_chip_info ads1018_chip_info = {
+	.name = "ads1018",
+
+	.channels = ads1018_iio_channels,
+	.channels_sz = ARRAY_SIZE(ads1018_iio_channels),
+
+	.fsr_table = ads1018_fsr_table,
+	.fsr_table_sz = ARRAY_SIZE(ads1018_fsr_table),
+	.sps_table = ads1018_drate_table,
+	.sps_table_sz = ARRAY_SIZE(ads1018_drate_table),
+	.temp_scale = { 0, 125000 },
+};
+
+static const struct ads1x18_chip_info ads1118_chip_info = {
+	.name = "ads1118",
+
+	.channels = ads1118_iio_channels,
+	.channels_sz = ARRAY_SIZE(ads1118_iio_channels),
+
+	.fsr_table = ads1118_fsr_table,
+	.fsr_table_sz = ARRAY_SIZE(ads1118_fsr_table),
+	.sps_table = ads1118_drate_table,
+	.sps_table_sz = ARRAY_SIZE(ads1118_drate_table),
+	.temp_scale = { 0, 31250 },
+};
+
+static const struct of_device_id ads1x18_of_match[] = {
+	{ .compatible = "ti,ads1018", .data = &ads1018_chip_info },
+	{ .compatible = "ti,ads1118", .data = &ads1118_chip_info },
+	{ }
+};
+MODULE_DEVICE_TABLE(of, ads1x18_of_match);
+
+static const struct spi_device_id ads1x18_spi_match[] = {
+	{ "ads1018", (kernel_ulong_t)&ads1018_chip_info },
+	{ "ads1118", (kernel_ulong_t)&ads1118_chip_info },
+	{ }
+};
+MODULE_DEVICE_TABLE(spi, ads1x18_spi_match);
+
+static struct spi_driver ads1x18_spi_driver = {
+	.driver = {
+		.name = "ads1x18",
+		.of_match_table = ads1x18_of_match,
+		.pm = pm_sleep_ptr(&ads1x18_pm_ops),
+	},
+	.probe = ads1x18_spi_probe,
+	.id_table = ads1x18_spi_match,
+};
+
+module_spi_driver(ads1x18_spi_driver);
+
+MODULE_DESCRIPTION("Texas Instruments ADS1X18 ADC Driver");
+MODULE_LICENSE("GPL");
+MODULE_AUTHOR("Kurt Borja <kuurtb@gmail.com>");

-- 
2.52.0

Re: [PATCH 2/2] iio: adc: Add ti-ads1x18 driver

[David Lechner]

On 11/21/25 11:16 AM, Kurt Borja wrote:
> Add ti-ads1x18 driver for Texas Instruments ADS1018 and ADS1118 SPI
> analog-to-digital converters.
> 
> These devices support a data-ready IRQ, which is shared with the MOSI
> line. Due to this peculiarity, interrupt and IIO trigger design is
> heavily inspired in ad_sigma_delta drivers. The IRQ is only enabled when
> waiting for data and an additional GPIO is needed to check if it isn't a
> latched pending interrupt.
> 
> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
> ---
>  MAINTAINERS                  |   7 +
>  drivers/iio/adc/Kconfig      |  12 +
>  drivers/iio/adc/Makefile     |   1 +
>  drivers/iio/adc/ti-ads1x18.c | 919 +++++++++++++++++++++++++++++++++++++++++++
>  4 files changed, 939 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 31d98efb1ad1..f9f0983d5d6f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -25646,6 +25646,13 @@ S:	Maintained
>  F:	Documentation/devicetree/bindings/iio/adc/ti,ads1119.yaml
>  F:	drivers/iio/adc/ti-ads1119.c
>  
> +TI ADS1X18 ADC DRIVER
> +M:	Kurt Borja <kuurtb@gmail.com>
> +L:	linux-iio@vger.kernel.org
> +S:	Maintained
> +F:	Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml

It is better if the maintainer entry minus the line below is included in
the dt-bindings patch rather than this patch since that is when the first
file is added.

> +F:	drivers/iio/adc/ti-ads1x18.c

Then just the line above will stay in this patch.

> +
>  TI ADS7924 ADC DRIVER
>  M:	Hugo Villeneuve <hvilleneuve@dimonoff.com>
>  L:	linux-iio@vger.kernel.org
> diff --git a/drivers/iio/adc/Kconfig b/drivers/iio/adc/Kconfig
> index 58da8255525e..0d3229a67af8 100644
> --- a/drivers/iio/adc/Kconfig
> +++ b/drivers/iio/adc/Kconfig
> @@ -1686,6 +1686,18 @@ config TI_ADS1119
>           This driver can also be built as a module. If so, the module will be
>           called ti-ads1119.
>  
> +config TI_ADS1X18

We strongly avoid putting an X in names. This applies here and in file names,
etc. Too many times, the pattern has not matched future parts and has been more
confusing than helpful. I like to use the lowsest number part for the generic
name.

> +       tristate "Texas Instruments ADS1119 ADC"

Typo. There is no 9 in these part numbers. And so this should be moved above
the previous existing entry to maintain alphabetical ordering.

> +       depends on SPI
> +       select IIO_BUFFER
> +       select IIO_TRIGGERED_BUFFER
> +       help
> +         If you say yes here you get support for Texas Instruments ADS1X18
> +         ADC chips.
> +
> +         This driver can also be built as a module. If so, the module will be
> +         called ti-ads1x18.
> +
>  config TI_ADS124S08
>  	tristate "Texas Instruments ADS124S08"
>  	depends on SPI
> diff --git a/drivers/iio/adc/Makefile b/drivers/iio/adc/Makefile
> index 7cc8f9a12f76..ab3b52307482 100644
> --- a/drivers/iio/adc/Makefile
> +++ b/drivers/iio/adc/Makefile
> @@ -147,6 +147,7 @@ obj-$(CONFIG_TI_ADC161S626) += ti-adc161s626.o
>  obj-$(CONFIG_TI_ADS1015) += ti-ads1015.o
>  obj-$(CONFIG_TI_ADS1100) += ti-ads1100.o
>  obj-$(CONFIG_TI_ADS1119) += ti-ads1119.o
> +obj-$(CONFIG_TI_ADS1X18) += ti-ads1x18.o

Comment above apply here as well.

>  obj-$(CONFIG_TI_ADS124S08) += ti-ads124s08.o
>  obj-$(CONFIG_TI_ADS1298) += ti-ads1298.o
>  obj-$(CONFIG_TI_ADS131E08) += ti-ads131e08.o
> diff --git a/drivers/iio/adc/ti-ads1x18.c b/drivers/iio/adc/ti-ads1x18.c
> new file mode 100644
> index 000000000000..1bf4fe34a825
> --- /dev/null
> +++ b/drivers/iio/adc/ti-ads1x18.c
> @@ -0,0 +1,919 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Texas Instruments ADS1X18 ADC driver
> + *
> + * Copyright (C) 2025 Kurt Borja <kuurtb@gmail.com>
> + */
> +
> +#include <linux/array_size.h>
> +#include <linux/bitfield.h>
> +#include <linux/bits.h>
> +#include <linux/bitmap.h>
> +#include <linux/byteorder/generic.h>
> +#include <linux/cleanup.h>
> +#include <linux/completion.h>
> +#include <linux/dev_printk.h>
> +#include <linux/device.h>
> +#include <linux/device/devres.h>
> +#include <linux/errno.h>
> +#include <linux/find.h>
> +#include <linux/gfp_types.h>
> +#include <linux/gpio/consumer.h>
> +#include <linux/interrupt.h>
> +#include <linux/jiffies.h>
> +#include <linux/module.h>
> +#include <linux/mod_devicetable.h>
> +#include <linux/mutex.h>
> +#include <linux/pm.h>
> +#include <linux/regmap.h>
> +#include <linux/spinlock.h>

spinlock isn't used. Probabaly others as well. Please check and
remove them.

> +#include <linux/spi/spi.h>
> +#include <linux/units.h>
> +
> +#include <linux/iio/buffer.h>
> +#include <linux/iio/iio.h>
> +#include <linux/iio/trigger.h>
> +#include <linux/iio/triggered_buffer.h>
> +#include <linux/iio/trigger_consumer.h>
> +

Comment on not using X also applies to identifier names.

> +#define ADS1X18_CFG_DEFAULT		0x058b
> +

Usually, we have macros to define the registers. and group
the fields under each register.

#define ADS1018_CFG_REG			0x0000

And indent the fields a bit to make a visual distenction

> +#define ADS1X18_CFG_OS_TRIG		BIT_U16(15)
> +#define ADS1X18_CFG_TS_MODE_EN		BIT_U16(4)
> +#define ADS1X18_CFG_PULL_UP		BIT_U16(3)
> +#define ADS1X18_CFG_NOP			BIT_U16(1)
> +#define ADS1X18_CFG_VALID		(ADS1X18_CFG_PULL_UP | ADS1X18_CFG_NOP)
> +

In IIO, we just use BIT() and GENMASK(). The U16 version doesn't really
add anything useful and IMHO makes it harder to read.

> +#define ADS1X18_CFG_MUX_MASK		GENMASK_U16(14, 12)
> +#define ADS1X18_AIN0_AIN1_ADDR		0
> +#define ADS1X18_AIN0_AIN3_ADDR		1
> +#define ADS1X18_AIN1_AIN3_ADDR		2
> +#define ADS1X18_AIN2_AIN3_ADDR		3
> +#define ADS1X18_AIN0_GND_ADDR		4
> +#define ADS1X18_AIN1_GND_ADDR		5
> +#define ADS1X18_AIN2_GND_ADDR		6
> +#define ADS1X18_AIN3_GND_ADDR		7
> +#define ADS1X18_TEMP_ADDR		8
> +#define ADS1X18_TIMESTAMP_ADDR		9
> +
> +#define ADS1X18_CFG_PGA_MASK		GENMASK_U16(11, 9)
> +#define ADS1X18_PGA_MODE_0		0
> +#define ADS1X18_PGA_MODE_1		1
> +#define ADS1X18_PGA_MODE_2		2
> +#define ADS1X18_PGA_MODE_3		3
> +#define ADS1X18_PGA_MODE_4		4
> +#define ADS1X18_PGA_MODE_5		5

Not much use in making a macro that matches the value. We can just
use the value directly. And we will have a lookup table to map the

> +#define ADS1X18_PGA_DEFAULT		ADS1X18_PGA_MODE_2
> +
> +#define ADS1X18_CFG_MODE_MASK		GENMASK_U16(8, 8)
> +#define ADS1X18_MODE_CONTINUOUS		0
> +#define ADS1X18_MODE_ONESHOT		1
> +
> +#define ADS1X18_CFG_DRATE_MASK		GENMASK_U16(7, 5)
> +#define ADS1X18_DRATE_MODE_0		0
> +#define ADS1X18_DRATE_MODE_1		1
> +#define ADS1X18_DRATE_MODE_2		2
> +#define ADS1X18_DRATE_MODE_3		3
> +#define ADS1X18_DRATE_MODE_4		4
> +#define ADS1X18_DRATE_MODE_5		5
> +#define ADS1X18_DRATE_MODE_6		6
> +#define ADS1X18_DRATE_MODE_7		7
> +#define ADS1X18_DRATE_DEFAULT		ADS1X18_DRATE_MODE_4
> +
> +#define ADS1X18_MAX_ADC_ADDR		7
> +#define ADS1X18_MAX_CHANNELS		9
> +
> +struct ads1x18_chan_data {
> +	unsigned int pga_mode:3;
> +	unsigned int drate_mode:3;

I would just use u8 instead of bit fields. We don't usually worry
about saving every little byte unless there are going to be 100s or
1000s of copies of something.

And I would spell out data_rate.

> +};
> +
> +struct ads1x18_chip_info {
> +	const char *name;
> +
> +	const struct iio_chan_spec *channels;
> +	unsigned long channels_sz;

Usually, we say "num_channels" as size could be interpreted as
size in bytes.

> +
> +	const int *sps_table;

"sps" is a bit obscure. I assume this corresponds to drate_mode above?
So perhaps call this data_rate_mode_to_hz_table.

> +	unsigned long sps_table_sz;
> +	const int (*fsr_table)[2];
> +	unsigned long fsr_table_sz;

Same with "fsr". Maybe pga_mode_to_gain_table?

> +	const int temp_scale[2];

This could use a comment. I assume it is integer and micro?

> +};
> +
> +struct ads1x18 {
> +	struct spi_device *spi;
> +	struct iio_dev *indio_dev;
> +	struct iio_trigger *indio_trig;
> +
> +	struct gpio_desc *drdy_gpiod;
> +	int drdy_irq;
> +
> +	u16 tx_buf[2] __aligned(IIO_DMA_MINALIGN);
> +	u16 rx_buf[2];

These need to be moved to the end of the struct. Otherwise everything
after could be in the same cache line and run into problems when DMA
is used.

> +	struct spi_transfer xfer;
> +	struct spi_message message;
> +	struct completion data_ready;
> +	struct mutex msg_lock; /* Protects message transfers */

Unless we need to be able to do direct reads and buffered reads
at the same time, we can usually make use of iio_device_claim_direct()
instead of a new mutex.

> +
> +	unsigned int restore_mode:1;

Just use bool.

> +
> +	unsigned long bufidx_to_addr[ADS1X18_MAX_CHANNELS];

This looks fishy. I think it is only needed because of the lack of
.scan_index, so should be able to remove it.

> +	struct ads1x18_chan_data channels[ADS1X18_MAX_CHANNELS];
> +
> +	const struct ads1x18_chip_info *chip_info;
> +};
> +
> +#define ADS1X18_VOLT_CHANNEL(_addr, _chan, _chan2, _diff, _realbits) {		\
> +	.type = IIO_VOLTAGE,							\
> +	.channel = _chan,							\
> +	.channel2 = _chan2,							\
> +	.address = _addr,							\

Since we are doing buffered reads, we need to set .scan_index. And usually,
we can make it so that .scan_index is the same as .address and just use
.scan_index everywhere and never set .address.

> +	.scan_type = {								\
> +		.sign = 's',							\
> +		.realbits = _realbits,						\
> +		.storagebits = 16,						\
> +		.shift = 16 - _realbits,					\
> +	},									\
> +	.info_mask_separate = BIT(IIO_CHAN_INFO_RAW) |				\
> +			      BIT(IIO_CHAN_INFO_SCALE) |			\
> +			      BIT(IIO_CHAN_INFO_SAMP_FREQ),			\

Since we have to write the data rate to the config register on every sample
anyway, it is possible we could have a different data rate for each channel.
So it could make sensible to make SAMP_FREQ separate instead of shared_by_all
to allow that possibility.

> +	.info_mask_shared_by_type_available = BIT(IIO_CHAN_INFO_SCALE),		\

I'm a bit tempted to say that the scale_available should also be separate instead
of by_type. It is technically fine from what I could see in the datasheet, but I
just saw another chip recently that was simiar but had limits on the PGA on certain
mux channels.


> +	.info_mask_shared_by_all_available = BIT(IIO_CHAN_INFO_SAMP_FREQ),	\
> +	.modified = _diff,							\

We can't have .modified and .diff at the same time. And there should be no need
for .modified in this driver.

> +	.indexed = true,							\
> +	.differential = _diff,							\

I would make 2 different macros, one for .differential = 0 and one for
.differential = 1. This way we don't have the noise of an unused chan2
parameter when differential = 0.

> +}
> +
> +#define ADS1X18_TEMP_CHANNEL(_realbits)	{					\
> +	.type = IIO_TEMP,							\
> +	.channel = 0,								\
> +	.address = ADS1X18_TEMP_ADDR,						\

Also needs .scan_index.

> +	.scan_type = {								\
> +		.sign = 's',							\
> +		.realbits = _realbits,						\
> +		.storagebits = 16,						\
> +		.shift = 16 - _realbits,					\
> +	},									\
> +	.info_mask_separate = BIT(IIO_CHAN_INFO_RAW) |				\
> +			      BIT(IIO_CHAN_INFO_SCALE) |			\
> +			      BIT(IIO_CHAN_INFO_SAMP_FREQ),			\
> +	.info_mask_shared_by_all_available = BIT(IIO_CHAN_INFO_SAMP_FREQ),	\
> +}
> +
> +static const struct iio_chan_spec ads1118_iio_channels[] = {
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_AIN1_ADDR, 0, 1, true, 16),
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_AIN3_ADDR, 0, 3, true, 16),
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN1_AIN3_ADDR, 1, 3, true, 16),
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN2_AIN3_ADDR, 2, 3, true, 16),
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_GND_ADDR, 0, 0, false, 16),
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN1_GND_ADDR, 1, 0, false, 16),
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN2_GND_ADDR, 2, 0, false, 16),
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN3_GND_ADDR, 3, 0, false, 16),
> +	ADS1X18_TEMP_CHANNEL(14),
> +	IIO_CHAN_SOFT_TIMESTAMP(ADS1X18_TIMESTAMP_ADDR),

When we switch out .address for .scan_index, I would drop the ADDR macros
here. It should just be 0, 1, 2, 3, ... on each line. With numbers, it is
easy to see mistakes, but the macros hide that.

> +};
> +
> +static const struct iio_chan_spec ads1018_iio_channels[] = {
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_AIN1_ADDR, 0, 1, true, 12),
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_AIN3_ADDR, 0, 3, true, 12),
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN1_AIN3_ADDR, 1, 3, true, 12),
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN2_AIN3_ADDR, 2, 3, true, 12),
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_GND_ADDR, 0, 0, false, 12),
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN1_GND_ADDR, 1, 0, false, 12),
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN2_GND_ADDR, 2, 0, false, 12),
> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN3_GND_ADDR, 3, 0, false, 12),
> +	ADS1X18_TEMP_CHANNEL(12),
> +	IIO_CHAN_SOFT_TIMESTAMP(ADS1X18_TIMESTAMP_ADDR),
> +};
> +
> +static unsigned int ads1x18_get_drate_mode(struct ads1x18 *ads1x18,
> +					   unsigned int address)
> +{
> +	return ads1x18->channels[address].drate_mode;
> +}
> +
> +static unsigned int ads1x18_get_pga_mode(struct ads1x18 *ads1x18,
> +					 unsigned int address)
> +{
> +	return ads1x18->channels[address].pga_mode;
> +}
> +
> +static void ads1x18_set_drate_mode(struct ads1x18 *ads1x18, unsigned int address,
> +				   unsigned int val)
> +{
> +	ads1x18->channels[address].drate_mode = val;
> +}
> +
> +static void ads1x18_set_pga_mode(struct ads1x18 *ads1x18, unsigned int address,
> +				 unsigned int val)
> +{
> +	ads1x18->channels[address].pga_mode = val;
> +}
> +
> +static unsigned long ads1x18_calc_timeout(struct ads1x18 *ads1x18,
> +					  unsigned int drate_mode)
> +{
> +	const struct ads1x18_chip_info *chip_info = ads1x18->chip_info;
> +	unsigned long timeout;
> +	unsigned int sps;
> +

This could use some comments explaining how we came up with this
calculation and what the timeout will be used for.

> +	sps = chip_info->sps_table[drate_mode];
> +	timeout = DIV_ROUND_UP(MICROHZ_PER_HZ, sps);
> +
> +	return usecs_to_jiffies(timeout * 2);
> +}
> +
> +static int __ads1x18_read_conver(struct ads1x18 *ads1x18, u16 *cnv)
> +{
> +	int ret;
> +
> +	ads1x18->tx_buf[0] = 0;
> +	ads1x18->tx_buf[1] = 0;
> +	ret = spi_sync_locked(ads1x18->spi, &ads1x18->message);
> +	if (ret)
> +		return ret;
> +
> +	*cnv = be16_to_cpu(ads1x18->rx_buf[0]);
> +
> +	return 0;
> +}
> +
> +static int __ads1x18_write_config(struct ads1x18 *ads1x18, u16 cfg)
> +{
> +	ads1x18->tx_buf[0] = cpu_to_be16(cfg);
> +	ads1x18->tx_buf[1] = 0;
> +
> +	return spi_sync_locked(ads1x18->spi, &ads1x18->message);
> +}
> +
> +static int ads1x18_read_conver(struct ads1x18 *ads1x18, u16 *cnv)
> +{
> +	int ret;
> +
> +	spi_bus_lock(ads1x18->spi->controller);

It is very unusual to manually manage the SPI bus lock. I see later that there
is a good reason for it. It would be good to mention that in the commit message
as well.

And it would be helpful to have a few more comments throughout explaining
which function should be called from where to get proper locking.

> +	ret = __ads1x18_read_conver(ads1x18, cnv);
> +	spi_bus_unlock(ads1x18->spi->controller);
> +
> +	return ret;
> +}
> +
> +static int ads1x18_write_config(struct ads1x18 *ads1x18, u16 cfg)
> +{
> +	int ret;
> +
> +	spi_bus_lock(ads1x18->spi->controller);
> +	ret = __ads1x18_write_config(ads1x18, cfg);
> +	spi_bus_unlock(ads1x18->spi->controller);
> +
> +	return ret;
> +}
> +
> +static int ads1x18_oneshot(struct ads1x18 *ads1x18,
> +			   struct iio_chan_spec const *chan, int *val)
> +{
> +	unsigned int drate = ads1x18_get_drate_mode(ads1x18, chan->address);
> +	unsigned int pga = ads1x18_get_pga_mode(ads1x18, chan->address);
> +	unsigned long timeout = ads1x18_calc_timeout(ads1x18, drate);
> +	u16 cnv, cfg = 0;
> +	int ret;
> +
> +	reinit_completion(&ads1x18->data_ready);
> +
> +	cfg |= ADS1X18_CFG_VALID;
> +	cfg |= ADS1X18_CFG_OS_TRIG;
> +	cfg |= FIELD_PREP(ADS1X18_CFG_MUX_MASK, chan->address);
> +	cfg |= FIELD_PREP(ADS1X18_CFG_PGA_MASK, pga);
> +	cfg |= FIELD_PREP(ADS1X18_CFG_MODE_MASK, ADS1X18_MODE_ONESHOT);
> +	cfg |= FIELD_PREP(ADS1X18_CFG_DRATE_MASK, drate);
> +	if (chan->type == IIO_TEMP)
> +		cfg |= ADS1X18_CFG_TS_MODE_EN;
> +
> +	ret = __ads1x18_write_config(ads1x18, cfg);
> +	if (ret)
> +		return ret;
> +	enable_irq(ads1x18->drdy_irq);
> +
> +	if (!wait_for_completion_timeout(&ads1x18->data_ready, timeout)) {
> +		disable_irq(ads1x18->drdy_irq);
> +		return -ETIMEDOUT;
> +	}
> +	disable_irq(ads1x18->drdy_irq);
> +
> +	ret = __ads1x18_read_conver(ads1x18, &cnv);
> +	if (ret)
> +		return ret;
> +
> +	cnv >>= chan->scan_type.shift;
> +	*val = sign_extend32(cnv, chan->scan_type.realbits - 1);

For direct reads, I would not mess with the interrupt. Unless there is some reason
(like filtering effects) that the data rate is important when reading a single sample,
I would just set the sample rate to the lowest value. Then we can create a single
SPI message using the delay feature of struct spi_xfer that has a delay to match
the period of the data rate. The SPI message would have to have two transfers, one
to trigger the conversion and the other to read the data. Then this will also work
even in cases where the DRDY interrupt is not wired up.

Also, this would allow to simplify the SPI bus lock situation in that we would only
need to take the lock when starting a buffered read

> +
> +	return ret;
> +}
> +
> +static int
> +ads1x18_read_raw(struct iio_dev *indio_dev, struct iio_chan_spec const *chan,
> +		 int *val, int *val2, long mask)
> +{
> +	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
> +	struct ads1x18_chan_data *chan_info = &ads1x18->channels[chan->address];
> +	const struct ads1x18_chip_info *chip_info = ads1x18->chip_info;
> +	int ret;
> +
> +	guard(mutex)(&ads1x18->msg_lock);

Yup,  there is already iio_device_claim_direct() in use here so this
mutex seems redundant.

> +
> +	switch (mask) {
> +	case IIO_CHAN_INFO_RAW:
> +		if (!iio_device_claim_direct(indio_dev))
> +			return -EBUSY;
> +		/* CS needs to remain asserted until dataready IRQ */
> +		spi_bus_lock(ads1x18->spi->controller);
> +
> +		ret = ads1x18_oneshot(ads1x18, chan, val);
> +
> +		spi_bus_unlock(ads1x18->spi->controller);
> +		iio_device_release_direct(indio_dev);
> +
> +		if (ret)
> +			return ret;
> +
> +		return IIO_VAL_INT;
> +
> +	case IIO_CHAN_INFO_SCALE:
> +		switch (chan->type) {
> +		case IIO_VOLTAGE:
> +			*val = chip_info->fsr_table[chan_info->pga_mode][0];
> +			*val2 = chip_info->fsr_table[chan_info->pga_mode][1];
> +			return IIO_VAL_INT_PLUS_NANO;
> +
> +		case IIO_TEMP:
> +			*val = chip_info->temp_scale[0];
> +			*val2 = chip_info->temp_scale[1];
> +			return IIO_VAL_INT_PLUS_MICRO;
> +
> +		default:
> +			return -EOPNOTSUPP;
> +		}
> +
> +	case IIO_CHAN_INFO_SAMP_FREQ:
> +		*val = chip_info->sps_table[chan_info->drate_mode];
> +		return IIO_VAL_INT;
> +
> +	default:
> +		return -EOPNOTSUPP;
> +	}
> +}
> +
> +static int
> +ads1x18_read_avail(struct iio_dev *indio_dev, struct iio_chan_spec const *chan,
> +		   const int **vals, int *type, int *length, long mask)
> +{
> +	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
> +
> +	switch (mask) {
> +	case IIO_CHAN_INFO_SCALE:
> +		*type = IIO_VAL_INT_PLUS_NANO;
> +		*vals = (const int *)ads1x18->chip_info->fsr_table;
> +		*length = ads1x18->chip_info->fsr_table_sz * 2;
> +		return IIO_AVAIL_LIST;
> +
> +	case IIO_CHAN_INFO_SAMP_FREQ:
> +		*type = IIO_VAL_INT;
> +		*vals = ads1x18->chip_info->sps_table;
> +		*length = ads1x18->chip_info->sps_table_sz;
> +		return IIO_AVAIL_LIST;
> +
> +	default:
> +		return -EOPNOTSUPP;
> +	}
> +}
> +
> +static int
> +ads1x18_write_raw(struct iio_dev *indio_dev, struct iio_chan_spec const *chan,
> +		  int val, int val2, long mask)
> +{
> +	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
> +	const struct ads1x18_chip_info *info = ads1x18->chip_info;
> +	unsigned int i = 0;

Strange way to initialize a for loop. I would just do it normally.

> +
> +	guard(mutex)(&ads1x18->msg_lock);
> +
> +	switch (mask) {
> +	case IIO_CHAN_INFO_SCALE:
> +		for (; i < info->fsr_table_sz; i++) {
> +			if (val != info->fsr_table[i][0] ||
> +			    val2 != info->fsr_table[i][1])
> +				continue;
> +
> +			ads1x18_set_pga_mode(ads1x18, chan->address, i);
> +			return 0;
> +		}
> +
> +		return -EINVAL;
> +
> +	case IIO_CHAN_INFO_SAMP_FREQ:
> +		for (; i < info->sps_table_sz; i++) {
> +			if (val != info->sps_table[i])
> +				continue;
> +
> +			ads1x18_set_drate_mode(ads1x18, chan->address, i);
> +			return 0;
> +		}
> +
> +		return -EINVAL;
> +
> +	default:
> +		return -EOPNOTSUPP;
> +	}
> +}
> +
> +static int
> +ads1x18_write_raw_get_fmt(struct iio_dev *indio_dev,
> +			  struct iio_chan_spec const *chan, long mask)
> +{
> +	switch (mask) {
> +	case IIO_CHAN_INFO_SCALE:
> +		return IIO_VAL_INT_PLUS_NANO;
> +	default:
> +		return IIO_VAL_INT_PLUS_MICRO;
> +	}
> +}
> +
> +static const struct iio_info ads1x18_iio_info = {
> +	.read_raw = ads1x18_read_raw,
> +	.read_avail = ads1x18_read_avail,
> +	.write_raw = ads1x18_write_raw,
> +	.write_raw_get_fmt = ads1x18_write_raw_get_fmt,
> +};
> +
> +static int ads1x18_set_trigger_state(struct iio_trigger *trig, bool state)
> +{
> +	struct ads1x18 *ads1x18 = iio_trigger_get_drvdata(trig);
> +	u16 cnv;
> +
> +	guard(mutex)(&ads1x18->msg_lock);
> +
> +	/*
> +	 * We need to lock the SPI bus when enabling the trigger to prevent
> +	 * another device from taking the CS and DOUT/DRDY lines.
> +	 */
> +
> +	if (state) {
> +		spi_bus_lock(ads1x18->spi->controller);
> +		enable_irq(ads1x18->drdy_irq);
> +
> +		/*
> +		 * Read once to ensure we are holding the CS line after locking
> +		 */
> +		return __ads1x18_read_conver(ads1x18, &cnv);

It is a bit confusing to have this here rather than in the buffer
enable callback since that is also setting the config that triggers
the first conversion.

Having the spi_bus_lock() and enable_irq() in the buffer enable
would make more sense to me too.

It should also be possible to use the chip without the interrupt
by using delay to wait for conversions, so perhaps we could make
the case for doing the enable_irq() here. But for sure spi_bus_lock()
would need to be in the buffer enable callback.

> +	}
> +
> +	disable_irq(ads1x18->drdy_irq);
> +	spi_bus_unlock(ads1x18->spi->controller);
> +
> +	return 0;
> +}
> +
> +static const struct iio_trigger_ops ads1x18_trigger_ops = {
> +	.set_trigger_state = ads1x18_set_trigger_state,
> +	.validate_device = iio_trigger_validate_own_device,
> +};
> +
> +static int ads1x18_buffer_preenable(struct iio_dev *indio_dev)
> +{
> +	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
> +	unsigned int pga, drate, addr, idx;
> +	u16 cfg = 0;
> +
> +	guard(mutex)(&ads1x18->msg_lock);
> +
> +	idx = find_first_bit(indio_dev->active_scan_mask,
> +			     iio_get_masklength(indio_dev));
> +	addr = ads1x18->bufidx_to_addr[idx];
> +	pga = ads1x18_get_pga_mode(ads1x18, addr);
> +	drate = ads1x18_get_drate_mode(ads1x18, addr);
> +
> +	cfg |= ADS1X18_CFG_VALID;
> +	cfg |= FIELD_PREP(ADS1X18_CFG_MUX_MASK, addr);
> +	cfg |= FIELD_PREP(ADS1X18_CFG_PGA_MASK, pga);
> +	cfg |= FIELD_PREP(ADS1X18_CFG_MODE_MASK, ADS1X18_MODE_CONTINUOUS);
> +	cfg |= FIELD_PREP(ADS1X18_CFG_DRATE_MASK, drate);
> +	if (addr == ADS1X18_TEMP_ADDR)
> +		cfg |= ADS1X18_CFG_TS_MODE_EN;
> +
> +	return ads1x18_write_config(ads1x18, cfg);
> +}
> +
> +static int ads1x18_buffer_postdisable(struct iio_dev *indio_dev)
> +{
> +	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
> +
> +	guard(mutex)(&ads1x18->msg_lock);
> +
> +	return ads1x18_write_config(ads1x18, ADS1X18_CFG_DEFAULT);
> +}
> +
> +static bool ads1x18_validate_scan_mask(struct iio_dev *indio_dev,
> +				       const unsigned long *mask)
> +{
> +	return bitmap_weight(mask, iio_get_masklength(indio_dev)) == 1;
> +}
> +
> +static const struct iio_buffer_setup_ops ads1x18_buffer_ops = {
> +	.preenable = ads1x18_buffer_preenable,
> +	.postdisable = ads1x18_buffer_postdisable,
> +	.validate_scan_mask = ads1x18_validate_scan_mask,
> +};
> +
> +static irqreturn_t ads1x18_irq_handler(int irq, void *dev_id)
> +{
> +	struct ads1x18 *ads1x18 = dev_id;
> +
> +	/*
> +	 * We need to check if the "drdy" pin is actually active or if it's a
> +	 * latched pending interrupt.
> +	 */
> +	if (!gpiod_get_value(ads1x18->drdy_gpiod))
> +		return IRQ_HANDLED;
> +
> +	complete(&ads1x18->data_ready);
> +	iio_trigger_poll(ads1x18->indio_trig);
> +
> +	return IRQ_HANDLED;
> +}
> +
> +static int ads1x18_interrupt_init(struct ads1x18 *ads1x18)
> +{
> +	const struct ads1x18_chip_info *info = ads1x18->chip_info;
> +	struct spi_device *spi = ads1x18->spi;
> +
> +	ads1x18->drdy_gpiod = devm_gpiod_get(&spi->dev, "drdy", GPIOD_IN);
> +	if (IS_ERR(ads1x18->drdy_gpiod))
> +		return dev_err_probe(&spi->dev, PTR_ERR(ads1x18->drdy_gpiod),
> +				     "Failed to get 'drdy' GPIO.\n");
> +

According the the dt-bindings, the interrupt could be separate from the
gpio. The SPI framework already looks up the first interrupts node if there
is one, so this could be

	if (spi->irq)
		ads1x18->drdy_irq = spi->irq;
	else

> +	ads1x18->drdy_irq = gpiod_to_irq(ads1x18->drdy_gpiod);
> +	if (ads1x18->drdy_irq < 0)
> +		return dev_err_probe(&spi->dev, ads1x18->drdy_irq,
> +				     "Failed to get 'drdy IRQ.\n'");
> +
> +	/*
> +	 * The "data-ready" IRQ line is shared with the MOSI pin, thus we need
> +	 * to keep it disabled until we actually request data.
> +	 */
> +	return devm_request_irq(&spi->dev, ads1x18->drdy_irq,
> +				ads1x18_irq_handler, IRQF_NO_AUTOEN,
> +				info->name, ads1x18);
> +}
> +
> +static irqreturn_t ads1x18_trigger_handler(int irq, void *p)
> +{
> +	struct iio_poll_func *pf = p;
> +	struct iio_dev *indio_dev = pf->indio_dev;
> +	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
> +	struct {
> +		u16 conv;
> +		aligned_s64 ts;
> +	} scan;

Need to 0-initilze with = { }; to avoid leaking uninitialized stack data.

> +	int ret;
> +
> +	guard(mutex)(&ads1x18->msg_lock);
> +
> +	if (iio_trigger_using_own(indio_dev)) {
> +		disable_irq(ads1x18->drdy_irq);
> +		ret = __ads1x18_read_conver(ads1x18, &scan.conv);
> +		enable_irq(ads1x18->drdy_irq);
> +	} else {
> +		ret = ads1x18_read_conver(ads1x18, &scan.conv);
> +	}
> +
> +	if (ret)
> +		return IRQ_HANDLED;
> +
> +	ret = iio_push_to_buffers_with_ts(indio_dev, &scan, sizeof(scan),
> +					  pf->timestamp);
> +	if (!ret)
> +		iio_trigger_notify_done(ads1x18->indio_trig);

Pretty sure we need to notify doen even in case of error, otherwise
we can get a deadlock.

In interrupt handlers our only choice is to ignore errors or do rate-limted
logging of them.

> +
> +	return IRQ_HANDLED;
> +}
> +
> +static int ads1x18_triggered_buffer_init(struct ads1x18 *ads1x18)
> +{
> +	struct iio_dev *indio_dev = ads1x18->indio_dev;
> +	struct spi_device *spi = ads1x18->spi;
> +	int ret;
> +
> +	ads1x18->indio_trig = devm_iio_trigger_alloc(&spi->dev, "%s-dev%d-drdy",
> +						     indio_dev->name,
> +						     iio_device_id(indio_dev));
> +	if (!ads1x18->indio_trig)
> +		return -ENOMEM;
> +
> +	iio_trigger_set_drvdata(ads1x18->indio_trig, ads1x18);
> +	ads1x18->indio_trig->ops = &ads1x18_trigger_ops;
> +
> +	ret = devm_iio_trigger_register(&spi->dev, ads1x18->indio_trig);
> +	if (ret)
> +		return ret;
> +
> +	return devm_iio_triggered_buffer_setup(&spi->dev, indio_dev,
> +					       iio_pollfunc_store_time,
> +					       ads1x18_trigger_handler,
> +					       &ads1x18_buffer_ops);
> +}
> +
> +static int ads1x18_message_init(struct ads1x18 *ads1x18)
> +{
> +	struct spi_device *spi = ads1x18->spi;
> +
> +	/*
> +	 * We need to keep CS asserted to catch "data-ready" interrupts.
> +	 * Otherwise the DOUT/DRDY line enters a Hi-Z state and it can't be
> +	 * driven by the ADC.
> +	 */
> +	ads1x18->xfer.cs_change = 1;

I think this is going to be problamatic for reading/writing the configuration
register and for direct reads of a single sample. My suggestion to make a
separate message with 2 xfers for the single read will partiall solve it.
And we could just use spi_write() for writing the config register.

> +	ads1x18->xfer.tx_buf = ads1x18->tx_buf;
> +	ads1x18->xfer.rx_buf = ads1x18->rx_buf;
> +	ads1x18->xfer.len = sizeof(ads1x18->tx_buf);
> +	spi_message_init_no_memset(&ads1x18->message);
> +	spi_message_add_tail(&ads1x18->xfer, &ads1x18->message);

Can be simplifed with spi_message_init_with_transfers().

> +
> +	return devm_spi_optimize_message(&spi->dev, spi, &ads1x18->message);
> +}
> +
> +static int ads1x18_fill_properties(struct ads1x18 *ads1x18,
> +				   struct fwnode_handle *handle,
> +				   struct iio_chan_spec *chan)
> +{
> +	const struct ads1x18_chip_info *info = ads1x18->chip_info;
> +	struct ads1x18_chan_data *chan_data;
> +	u32 val, reg;
> +	int ret;
> +
> +	ret = fwnode_property_read_u32(handle, "reg", &reg);
> +	if (ret)
> +		return ret;
> +	if (reg > ADS1X18_MAX_ADC_ADDR)
> +		return dev_err_probe(&ads1x18->spi->dev, -ENXIO,
> +				     "%s: Invalid channel address %u.\n",
> +				     fwnode_get_name(handle), reg);
> +
> +	*chan = info->channels[reg];
> +
> +	chan_data = &ads1x18->channels[reg];
> +	chan_data->pga_mode = ADS1X18_PGA_DEFAULT;
> +	chan_data->drate_mode = ADS1X18_DRATE_DEFAULT;
> +
> +	if (fwnode_property_present(handle, "ti,gain")) {
> +		ret = fwnode_property_read_u32(handle, "ti,gain", &val);
> +		if (ret)
> +			return ret;
> +		if (val >= info->fsr_table_sz)
> +			return dev_err_probe(&ads1x18->spi->dev, -ENXIO,
> +					     "%s: ti,gain not in range.",
> +					     fwnode_get_name(handle));
> +
> +		chan_data->pga_mode = val;
> +	}
> +
> +	if (fwnode_property_present(handle, "ti,datarate")) {
> +		ret = fwnode_property_read_u32(handle, "ti,datarate", &val);
> +		if (ret)
> +			return ret;
> +		if (val >= info->sps_table_sz)
> +			return dev_err_probe(&ads1x18->spi->dev, -ENXIO,
> +					     "%s: ti,datarate not in range.",
> +					     fwnode_get_name(handle));
> +
> +		chan_data->drate_mode = val;
> +	}

As mentioned in the dt-bindings review. We don't set an initial value
from the devicetree like this. So we should be able to drop all of this.

> +
> +	return 0;
> +}
> +
> +static int ads1x18_channels_init(struct ads1x18 *ads1x18,
> +				 const struct ads1x18_chip_info *info,
> +				 struct iio_chan_spec **cs)
> +{
> +	struct device *dev = &ads1x18->spi->dev;
> +	struct iio_chan_spec *channels;
> +	int ret, nchans, index = 0;
> +
> +	nchans = device_get_named_child_node_count(dev, "channel");
> +	if (!nchans)
> +		return dev_err_probe(dev, -ENODEV,
> +				     "No ADC channels described.\n");
> +
> +	channels = devm_kcalloc(dev, nchans + 2, sizeof(*channels), GFP_KERNEL);
> +	if (!channels)
> +		return -ENOMEM;
> +
> +	device_for_each_named_child_node_scoped(dev, child, "channel") {
> +		ret = ads1x18_fill_properties(ads1x18, child, &channels[index]);
> +		if (ret)
> +			return ret;
> +
> +		channels[index].scan_index = index;
> +		ads1x18->bufidx_to_addr[index] = channels[index].address;
> +		index++;
> +	}

There is a small enough number of channels that we shouldn't need any of this.
We can just make an array big enough for all channels in struct ads1x18.

> +
> +	ads1x18->channels[ADS1X18_TEMP_ADDR].drate_mode = ADS1X18_DRATE_DEFAULT;
> +	channels[index] = info->channels[ADS1X18_TEMP_ADDR];
> +	channels[index].scan_index = index;
> +	ads1x18->bufidx_to_addr[index] = channels[index].address;
> +	index++;
> +
> +	channels[index] = info->channels[ADS1X18_TIMESTAMP_ADDR];
> +	ads1x18->bufidx_to_addr[index] = channels[index].address;
> +
> +	*cs = channels;
> +
> +	return index;
> +}
> +
> +static int ads1x18_spi_probe(struct spi_device *spi)
> +{
> +	const struct ads1x18_chip_info *info = spi_get_device_match_data(spi);
> +	struct iio_chan_spec *channels;
> +	struct iio_dev *indio_dev;
> +	struct ads1x18 *ads1x18;
> +	int num_channels, ret;
> +
> +	indio_dev = devm_iio_device_alloc(&spi->dev, sizeof(*ads1x18));
> +	if (!indio_dev)
> +		return -ENOMEM;
> +
> +	ads1x18 = iio_priv(indio_dev);
> +	ads1x18->spi = spi;
> +	ads1x18->indio_dev = indio_dev;

Usually, we can write code so that a pointer back to indio_dev is not needed.

> +	ads1x18->chip_info = info;
> +	mutex_init(&ads1x18->msg_lock);
> +	init_completion(&ads1x18->data_ready);
> +	spi_set_drvdata(spi, ads1x18);

There is no spi_get_drvdata(), so we don't need this.

> +
> +	num_channels = ads1x18_channels_init(ads1x18, info, &channels);
> +	if (num_channels < 0)
> +		return num_channels;
> +	indio_dev->modes = INDIO_DIRECT_MODE;
> +	indio_dev->name = info->name;
> +	indio_dev->info = &ads1x18_iio_info;
> +	indio_dev->channels = channels;
> +	indio_dev->num_channels = num_channels;
> +
> +	ret = ads1x18_message_init(ads1x18);
> +	if (ret)
> +		return ret;
> +
> +	ret = ads1x18_triggered_buffer_init(ads1x18);
> +	if (ret)
> +		return ret;
> +
> +	ret = ads1x18_interrupt_init(ads1x18);
> +	if (ret)
> +		return ret;
> +
> +	return devm_iio_device_register(&spi->dev, indio_dev);
> +}
> +
> +static int ads1x18_suspend(struct device *dev)
> +{
> +	struct ads1x18 *ads1x18 = dev_get_drvdata(dev);
> +	u16 cfg;
> +	int ret;
> +
> +	guard(mutex)(&ads1x18->msg_lock);
> +
> +	/* Current config is readback into rx_buf[1] */
> +	cfg = be16_to_cpu(ads1x18->rx_buf[1]);
> +	if (FIELD_GET(ADS1X18_CFG_MODE_MASK, cfg) == ADS1X18_MODE_ONESHOT)
> +		return 0;
> +
> +	cfg |= FIELD_PREP(ADS1X18_CFG_MODE_MASK, ADS1X18_MODE_ONESHOT);
> +	ret = ads1x18_write_config(ads1x18, cfg);
> +	if (ret)
> +		return ret;
> +
> +	ads1x18->restore_mode = 1;
> +
> +	return 0;
> +}
> +
> +static int ads1x18_resume(struct device *dev)
> +{
> +	struct ads1x18 *ads1x18 = dev_get_drvdata(dev);
> +	u16 cfg;
> +	int ret;
> +
> +	guard(mutex)(&ads1x18->msg_lock);
> +
> +	if (!ads1x18->restore_mode)
> +		return 0;
> +
> +	cfg = be16_to_cpu(ads1x18->rx_buf[1]);
> +	FIELD_MODIFY(ADS1X18_CFG_MODE_MASK, &cfg, ADS1X18_MODE_CONTINUOUS);
> +	ret = ads1x18_write_config(ads1x18, cfg);
> +	if (ret)
> +		return ret;
> +
> +	ads1x18->restore_mode = 0;
> +
> +	return 0;
> +}

I think we could simplify this and avoid needing to use pm runtime (and use
even less power!). During probe, put the chip in power down mode. When doing
direct reads of a single value, put the chip in single-shot mode. When doing
starting a buffered read, put it in continuous mode and when the buffered read
is stopped, put it back in shutdown mode.

> +
> +static DEFINE_SIMPLE_DEV_PM_OPS(ads1x18_pm_ops, ads1x18_suspend, ads1x18_resume);
> +
> +static const int ads1118_fsr_table[][2] = {
> +	[ADS1X18_PGA_MODE_0] = { 0, 187500 },
> +	[ADS1X18_PGA_MODE_1] = { 0, 125000 },
> +	[ADS1X18_PGA_MODE_2] = { 0, 62500 },
> +	[ADS1X18_PGA_MODE_3] = { 0, 31250 },
> +	[ADS1X18_PGA_MODE_4] = { 0, 15625 },
> +	[ADS1X18_PGA_MODE_5] = { 0, 7812 }
> +};
> +
> +static const int ads1018_fsr_table[][2] = {
> +	[ADS1X18_PGA_MODE_0] = { 0, 3000000 },
> +	[ADS1X18_PGA_MODE_1] = { 0, 2000000 },
> +	[ADS1X18_PGA_MODE_2] = { 0, 1000000 },
> +	[ADS1X18_PGA_MODE_3] = { 0, 500000 },
> +	[ADS1X18_PGA_MODE_4] = { 0, 250000 },
> +	[ADS1X18_PGA_MODE_5] = { 0, 125000 }
> +};
> +
> +static const unsigned int ads1018_drate_table[] = {
> +	[ADS1X18_DRATE_MODE_0] = 128,
> +	[ADS1X18_DRATE_MODE_1] = 250,
> +	[ADS1X18_DRATE_MODE_2] = 490,
> +	[ADS1X18_DRATE_MODE_3] = 920,
> +	[ADS1X18_DRATE_MODE_4] = 1600,
> +	[ADS1X18_DRATE_MODE_5] = 2400,
> +	[ADS1X18_DRATE_MODE_6] = 3300
> +};
> +
> +static const unsigned int ads1118_drate_table[] = {
> +	[ADS1X18_DRATE_MODE_0] = 8,
> +	[ADS1X18_DRATE_MODE_1] = 16,
> +	[ADS1X18_DRATE_MODE_2] = 32,
> +	[ADS1X18_DRATE_MODE_3] = 64,
> +	[ADS1X18_DRATE_MODE_4] = 128,
> +	[ADS1X18_DRATE_MODE_5] = 250,
> +	[ADS1X18_DRATE_MODE_6] = 475,
> +	[ADS1X18_DRATE_MODE_7] = 860
> +};

These table could use more descriptive names or comments that exlain what
sort of mapping they are doing.

> +
> +static const struct ads1x18_chip_info ads1018_chip_info = {
> +	.name = "ads1018",
> +
> +	.channels = ads1018_iio_channels,
> +	.channels_sz = ARRAY_SIZE(ads1018_iio_channels),
> +
> +	.fsr_table = ads1018_fsr_table,
> +	.fsr_table_sz = ARRAY_SIZE(ads1018_fsr_table),
> +	.sps_table = ads1018_drate_table,
> +	.sps_table_sz = ARRAY_SIZE(ads1018_drate_table),
> +	.temp_scale = { 0, 125000 },
> +};
> +
> +static const struct ads1x18_chip_info ads1118_chip_info = {
> +	.name = "ads1118",
> +
> +	.channels = ads1118_iio_channels,
> +	.channels_sz = ARRAY_SIZE(ads1118_iio_channels),
> +
> +	.fsr_table = ads1118_fsr_table,
> +	.fsr_table_sz = ARRAY_SIZE(ads1118_fsr_table),
> +	.sps_table = ads1118_drate_table,
> +	.sps_table_sz = ARRAY_SIZE(ads1118_drate_table),
> +	.temp_scale = { 0, 31250 },
> +};
> +
> +static const struct of_device_id ads1x18_of_match[] = {
> +	{ .compatible = "ti,ads1018", .data = &ads1018_chip_info },
> +	{ .compatible = "ti,ads1118", .data = &ads1118_chip_info },
> +	{ }
> +};
> +MODULE_DEVICE_TABLE(of, ads1x18_of_match);
> +
> +static const struct spi_device_id ads1x18_spi_match[] = {
> +	{ "ads1018", (kernel_ulong_t)&ads1018_chip_info },
> +	{ "ads1118", (kernel_ulong_t)&ads1118_chip_info },
> +	{ }
> +};
> +MODULE_DEVICE_TABLE(spi, ads1x18_spi_match);
> +
> +static struct spi_driver ads1x18_spi_driver = {
> +	.driver = {
> +		.name = "ads1x18",

No x here either.

> +		.of_match_table = ads1x18_of_match,
> +		.pm = pm_sleep_ptr(&ads1x18_pm_ops),
> +	},
> +	.probe = ads1x18_spi_probe,
> +	.id_table = ads1x18_spi_match,
> +};
> +
> +module_spi_driver(ads1x18_spi_driver);
> +
> +MODULE_DESCRIPTION("Texas Instruments ADS1X18 ADC Driver");

or here.

> +MODULE_LICENSE("GPL");
> +MODULE_AUTHOR("Kurt Borja <kuurtb@gmail.com>");
> 

Re: [PATCH 2/2] iio: adc: Add ti-ads1x18 driver

[Kurt Borja]

On Fri Nov 21, 2025 at 5:33 PM -05, David Lechner wrote:
> On 11/21/25 11:16 AM, Kurt Borja wrote:
>> Add ti-ads1x18 driver for Texas Instruments ADS1018 and ADS1118 SPI
>> analog-to-digital converters.
>> 
>> These devices support a data-ready IRQ, which is shared with the MOSI
>> line. Due to this peculiarity, interrupt and IIO trigger design is
>> heavily inspired in ad_sigma_delta drivers. The IRQ is only enabled when
>> waiting for data and an additional GPIO is needed to check if it isn't a
>> latched pending interrupt.
>> 
>> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
>> ---
>>  MAINTAINERS                  |   7 +
>>  drivers/iio/adc/Kconfig      |  12 +
>>  drivers/iio/adc/Makefile     |   1 +
>>  drivers/iio/adc/ti-ads1x18.c | 919 +++++++++++++++++++++++++++++++++++++++++++
>>  4 files changed, 939 insertions(+)
>> 
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 31d98efb1ad1..f9f0983d5d6f 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -25646,6 +25646,13 @@ S:	Maintained
>>  F:	Documentation/devicetree/bindings/iio/adc/ti,ads1119.yaml
>>  F:	drivers/iio/adc/ti-ads1119.c
>>  
>> +TI ADS1X18 ADC DRIVER
>> +M:	Kurt Borja <kuurtb@gmail.com>
>> +L:	linux-iio@vger.kernel.org
>> +S:	Maintained
>> +F:	Documentation/devicetree/bindings/iio/adc/ti,ads1118.yaml
>
> It is better if the maintainer entry minus the line below is included in
> the dt-bindings patch rather than this patch since that is when the first
> file is added.
>
>> +F:	drivers/iio/adc/ti-ads1x18.c
>
> Then just the line above will stay in this patch.

Will do!

>
>> +
>>  TI ADS7924 ADC DRIVER
>>  M:	Hugo Villeneuve <hvilleneuve@dimonoff.com>
>>  L:	linux-iio@vger.kernel.org
>> diff --git a/drivers/iio/adc/Kconfig b/drivers/iio/adc/Kconfig
>> index 58da8255525e..0d3229a67af8 100644
>> --- a/drivers/iio/adc/Kconfig
>> +++ b/drivers/iio/adc/Kconfig
>> @@ -1686,6 +1686,18 @@ config TI_ADS1119
>>           This driver can also be built as a module. If so, the module will be
>>           called ti-ads1119.
>>  
>> +config TI_ADS1X18
>
> We strongly avoid putting an X in names. This applies here and in file names,
> etc. Too many times, the pattern has not matched future parts and has been more
> confusing than helpful. I like to use the lowsest number part for the generic
> name.

Will do, for both files. I'll also change every symbol prefix.

>
>> +       tristate "Texas Instruments ADS1119 ADC"
>
> Typo. There is no 9 in these part numbers. And so this should be moved above
> the previous existing entry to maintain alphabetical ordering.
>
>> +       depends on SPI
>> +       select IIO_BUFFER
>> +       select IIO_TRIGGERED_BUFFER
>> +       help
>> +         If you say yes here you get support for Texas Instruments ADS1X18
>> +         ADC chips.
>> +
>> +         This driver can also be built as a module. If so, the module will be
>> +         called ti-ads1x18.
>> +
>>  config TI_ADS124S08
>>  	tristate "Texas Instruments ADS124S08"
>>  	depends on SPI
>> diff --git a/drivers/iio/adc/Makefile b/drivers/iio/adc/Makefile
>> index 7cc8f9a12f76..ab3b52307482 100644
>> --- a/drivers/iio/adc/Makefile
>> +++ b/drivers/iio/adc/Makefile
>> @@ -147,6 +147,7 @@ obj-$(CONFIG_TI_ADC161S626) += ti-adc161s626.o
>>  obj-$(CONFIG_TI_ADS1015) += ti-ads1015.o
>>  obj-$(CONFIG_TI_ADS1100) += ti-ads1100.o
>>  obj-$(CONFIG_TI_ADS1119) += ti-ads1119.o
>> +obj-$(CONFIG_TI_ADS1X18) += ti-ads1x18.o
>
> Comment above apply here as well.
>
>>  obj-$(CONFIG_TI_ADS124S08) += ti-ads124s08.o
>>  obj-$(CONFIG_TI_ADS1298) += ti-ads1298.o
>>  obj-$(CONFIG_TI_ADS131E08) += ti-ads131e08.o
>> diff --git a/drivers/iio/adc/ti-ads1x18.c b/drivers/iio/adc/ti-ads1x18.c
>> new file mode 100644
>> index 000000000000..1bf4fe34a825
>> --- /dev/null
>> +++ b/drivers/iio/adc/ti-ads1x18.c
>> @@ -0,0 +1,919 @@
>> +// SPDX-License-Identifier: GPL-2.0-only
>> +/*
>> + * Texas Instruments ADS1X18 ADC driver
>> + *
>> + * Copyright (C) 2025 Kurt Borja <kuurtb@gmail.com>
>> + */
>> +
>> +#include <linux/array_size.h>
>> +#include <linux/bitfield.h>
>> +#include <linux/bits.h>
>> +#include <linux/bitmap.h>
>> +#include <linux/byteorder/generic.h>
>> +#include <linux/cleanup.h>
>> +#include <linux/completion.h>
>> +#include <linux/dev_printk.h>
>> +#include <linux/device.h>
>> +#include <linux/device/devres.h>
>> +#include <linux/errno.h>
>> +#include <linux/find.h>
>> +#include <linux/gfp_types.h>
>> +#include <linux/gpio/consumer.h>
>> +#include <linux/interrupt.h>
>> +#include <linux/jiffies.h>
>> +#include <linux/module.h>
>> +#include <linux/mod_devicetable.h>
>> +#include <linux/mutex.h>
>> +#include <linux/pm.h>
>> +#include <linux/regmap.h>
>> +#include <linux/spinlock.h>
>
> spinlock isn't used. Probabaly others as well. Please check and
> remove them.
>
>> +#include <linux/spi/spi.h>
>> +#include <linux/units.h>
>> +
>> +#include <linux/iio/buffer.h>
>> +#include <linux/iio/iio.h>
>> +#include <linux/iio/trigger.h>
>> +#include <linux/iio/triggered_buffer.h>
>> +#include <linux/iio/trigger_consumer.h>
>> +
>
> Comment on not using X also applies to identifier names.
>
>> +#define ADS1X18_CFG_DEFAULT		0x058b
>> +
>
> Usually, we have macros to define the registers. and group
> the fields under each register.

I'll order it like that.

>
> #define ADS1018_CFG_REG			0x0000

I didn't define these because ads1118 dumps all registers (2) in each
transfer.

>
> And indent the fields a bit to make a visual distenction
>
>> +#define ADS1X18_CFG_OS_TRIG		BIT_U16(15)
>> +#define ADS1X18_CFG_TS_MODE_EN		BIT_U16(4)
>> +#define ADS1X18_CFG_PULL_UP		BIT_U16(3)
>> +#define ADS1X18_CFG_NOP			BIT_U16(1)
>> +#define ADS1X18_CFG_VALID		(ADS1X18_CFG_PULL_UP | ADS1X18_CFG_NOP)
>> +
>
> In IIO, we just use BIT() and GENMASK(). The U16 version doesn't really
> add anything useful and IMHO makes it harder to read.
>
>> +#define ADS1X18_CFG_MUX_MASK		GENMASK_U16(14, 12)
>> +#define ADS1X18_AIN0_AIN1_ADDR		0
>> +#define ADS1X18_AIN0_AIN3_ADDR		1
>> +#define ADS1X18_AIN1_AIN3_ADDR		2
>> +#define ADS1X18_AIN2_AIN3_ADDR		3
>> +#define ADS1X18_AIN0_GND_ADDR		4
>> +#define ADS1X18_AIN1_GND_ADDR		5
>> +#define ADS1X18_AIN2_GND_ADDR		6
>> +#define ADS1X18_AIN3_GND_ADDR		7
>> +#define ADS1X18_TEMP_ADDR		8
>> +#define ADS1X18_TIMESTAMP_ADDR		9
>> +
>> +#define ADS1X18_CFG_PGA_MASK		GENMASK_U16(11, 9)
>> +#define ADS1X18_PGA_MODE_0		0
>> +#define ADS1X18_PGA_MODE_1		1
>> +#define ADS1X18_PGA_MODE_2		2
>> +#define ADS1X18_PGA_MODE_3		3
>> +#define ADS1X18_PGA_MODE_4		4
>> +#define ADS1X18_PGA_MODE_5		5
>
> Not much use in making a macro that matches the value. We can just
> use the value directly. And we will have a lookup table to map the
>
>> +#define ADS1X18_PGA_DEFAULT		ADS1X18_PGA_MODE_2
>> +
>> +#define ADS1X18_CFG_MODE_MASK		GENMASK_U16(8, 8)
>> +#define ADS1X18_MODE_CONTINUOUS		0
>> +#define ADS1X18_MODE_ONESHOT		1
>> +
>> +#define ADS1X18_CFG_DRATE_MASK		GENMASK_U16(7, 5)
>> +#define ADS1X18_DRATE_MODE_0		0
>> +#define ADS1X18_DRATE_MODE_1		1
>> +#define ADS1X18_DRATE_MODE_2		2
>> +#define ADS1X18_DRATE_MODE_3		3
>> +#define ADS1X18_DRATE_MODE_4		4
>> +#define ADS1X18_DRATE_MODE_5		5
>> +#define ADS1X18_DRATE_MODE_6		6
>> +#define ADS1X18_DRATE_MODE_7		7
>> +#define ADS1X18_DRATE_DEFAULT		ADS1X18_DRATE_MODE_4
>> +
>> +#define ADS1X18_MAX_ADC_ADDR		7
>> +#define ADS1X18_MAX_CHANNELS		9
>> +
>> +struct ads1x18_chan_data {
>> +	unsigned int pga_mode:3;
>> +	unsigned int drate_mode:3;
>
> I would just use u8 instead of bit fields. We don't usually worry
> about saving every little byte unless there are going to be 100s or
> 1000s of copies of something.
>
> And I would spell out data_rate.
>
>> +};
>> +
>> +struct ads1x18_chip_info {
>> +	const char *name;
>> +
>> +	const struct iio_chan_spec *channels;
>> +	unsigned long channels_sz;
>
> Usually, we say "num_channels" as size could be interpreted as
> size in bytes.
>
>> +
>> +	const int *sps_table;
>
> "sps" is a bit obscure. I assume this corresponds to drate_mode above?
> So perhaps call this data_rate_mode_to_hz_table.
>
>> +	unsigned long sps_table_sz;
>> +	const int (*fsr_table)[2];
>> +	unsigned long fsr_table_sz;
>
> Same with "fsr". Maybe pga_mode_to_gain_table?
>
>> +	const int temp_scale[2];
>
> This could use a comment. I assume it is integer and micro?
>
>> +};
>> +
>> +struct ads1x18 {
>> +	struct spi_device *spi;
>> +	struct iio_dev *indio_dev;
>> +	struct iio_trigger *indio_trig;
>> +
>> +	struct gpio_desc *drdy_gpiod;
>> +	int drdy_irq;
>> +
>> +	u16 tx_buf[2] __aligned(IIO_DMA_MINALIGN);
>> +	u16 rx_buf[2];
>
> These need to be moved to the end of the struct. Otherwise everything
> after could be in the same cache line and run into problems when DMA
> is used.
>
>> +	struct spi_transfer xfer;
>> +	struct spi_message message;
>> +	struct completion data_ready;
>> +	struct mutex msg_lock; /* Protects message transfers */
>
> Unless we need to be able to do direct reads and buffered reads
> at the same time, we can usually make use of iio_device_claim_direct()
> instead of a new mutex.

I think my comment is misleading.

I added this mutex to protect channel state (pga, drate) while doing
transfers, either in direct or buffer mode.

>
>> +
>> +	unsigned int restore_mode:1;
>
> Just use bool.
>
>> +
>> +	unsigned long bufidx_to_addr[ADS1X18_MAX_CHANNELS];
>
> This looks fishy. I think it is only needed because of the lack of
> .scan_index, so should be able to remove it.
>
>> +	struct ads1x18_chan_data channels[ADS1X18_MAX_CHANNELS];
>> +
>> +	const struct ads1x18_chip_info *chip_info;
>> +};
>> +
>> +#define ADS1X18_VOLT_CHANNEL(_addr, _chan, _chan2, _diff, _realbits) {		\
>> +	.type = IIO_VOLTAGE,							\
>> +	.channel = _chan,							\
>> +	.channel2 = _chan2,							\
>> +	.address = _addr,							\
>
> Since we are doing buffered reads, we need to set .scan_index. And usually,
> we can make it so that .scan_index is the same as .address and just use
> .scan_index everywhere and never set .address.
>
>> +	.scan_type = {								\
>> +		.sign = 's',							\
>> +		.realbits = _realbits,						\
>> +		.storagebits = 16,						\
>> +		.shift = 16 - _realbits,					\
>> +	},									\
>> +	.info_mask_separate = BIT(IIO_CHAN_INFO_RAW) |				\
>> +			      BIT(IIO_CHAN_INFO_SCALE) |			\
>> +			      BIT(IIO_CHAN_INFO_SAMP_FREQ),			\
>
> Since we have to write the data rate to the config register on every sample
> anyway, it is possible we could have a different data rate for each channel.
> So it could make sensible to make SAMP_FREQ separate instead of shared_by_all
> to allow that possibility.
>
>> +	.info_mask_shared_by_type_available = BIT(IIO_CHAN_INFO_SCALE),		\
>
> I'm a bit tempted to say that the scale_available should also be separate instead
> of by_type. It is technically fine from what I could see in the datasheet, but I
> just saw another chip recently that was simiar but had limits on the PGA on certain
> mux channels.
>
>
>> +	.info_mask_shared_by_all_available = BIT(IIO_CHAN_INFO_SAMP_FREQ),	\
>> +	.modified = _diff,							\
>
> We can't have .modified and .diff at the same time. And there should be no need
> for .modified in this driver.
>
>> +	.indexed = true,							\
>> +	.differential = _diff,							\
>
> I would make 2 different macros, one for .differential = 0 and one for
> .differential = 1. This way we don't have the noise of an unused chan2
> parameter when differential = 0.
>
>> +}
>> +
>> +#define ADS1X18_TEMP_CHANNEL(_realbits)	{					\
>> +	.type = IIO_TEMP,							\
>> +	.channel = 0,								\
>> +	.address = ADS1X18_TEMP_ADDR,						\
>
> Also needs .scan_index.
>
>> +	.scan_type = {								\
>> +		.sign = 's',							\
>> +		.realbits = _realbits,						\
>> +		.storagebits = 16,						\
>> +		.shift = 16 - _realbits,					\
>> +	},									\
>> +	.info_mask_separate = BIT(IIO_CHAN_INFO_RAW) |				\
>> +			      BIT(IIO_CHAN_INFO_SCALE) |			\
>> +			      BIT(IIO_CHAN_INFO_SAMP_FREQ),			\
>> +	.info_mask_shared_by_all_available = BIT(IIO_CHAN_INFO_SAMP_FREQ),	\
>> +}
>> +
>> +static const struct iio_chan_spec ads1118_iio_channels[] = {
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_AIN1_ADDR, 0, 1, true, 16),
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_AIN3_ADDR, 0, 3, true, 16),
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN1_AIN3_ADDR, 1, 3, true, 16),
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN2_AIN3_ADDR, 2, 3, true, 16),
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_GND_ADDR, 0, 0, false, 16),
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN1_GND_ADDR, 1, 0, false, 16),
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN2_GND_ADDR, 2, 0, false, 16),
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN3_GND_ADDR, 3, 0, false, 16),
>> +	ADS1X18_TEMP_CHANNEL(14),
>> +	IIO_CHAN_SOFT_TIMESTAMP(ADS1X18_TIMESTAMP_ADDR),
>
> When we switch out .address for .scan_index, I would drop the ADDR macros
> here. It should just be 0, 1, 2, 3, ... on each line. With numbers, it is
> easy to see mistakes, but the macros hide that.

I like these macro suggestions. Will follow on v2.

>
>> +};
>> +
>> +static const struct iio_chan_spec ads1018_iio_channels[] = {
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_AIN1_ADDR, 0, 1, true, 12),
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_AIN3_ADDR, 0, 3, true, 12),
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN1_AIN3_ADDR, 1, 3, true, 12),
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN2_AIN3_ADDR, 2, 3, true, 12),
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN0_GND_ADDR, 0, 0, false, 12),
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN1_GND_ADDR, 1, 0, false, 12),
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN2_GND_ADDR, 2, 0, false, 12),
>> +	ADS1X18_VOLT_CHANNEL(ADS1X18_AIN3_GND_ADDR, 3, 0, false, 12),
>> +	ADS1X18_TEMP_CHANNEL(12),
>> +	IIO_CHAN_SOFT_TIMESTAMP(ADS1X18_TIMESTAMP_ADDR),
>> +};
>> +
>> +static unsigned int ads1x18_get_drate_mode(struct ads1x18 *ads1x18,
>> +					   unsigned int address)
>> +{
>> +	return ads1x18->channels[address].drate_mode;
>> +}
>> +
>> +static unsigned int ads1x18_get_pga_mode(struct ads1x18 *ads1x18,
>> +					 unsigned int address)
>> +{
>> +	return ads1x18->channels[address].pga_mode;
>> +}
>> +
>> +static void ads1x18_set_drate_mode(struct ads1x18 *ads1x18, unsigned int address,
>> +				   unsigned int val)
>> +{
>> +	ads1x18->channels[address].drate_mode = val;
>> +}
>> +
>> +static void ads1x18_set_pga_mode(struct ads1x18 *ads1x18, unsigned int address,
>> +				 unsigned int val)
>> +{
>> +	ads1x18->channels[address].pga_mode = val;
>> +}
>> +
>> +static unsigned long ads1x18_calc_timeout(struct ads1x18 *ads1x18,
>> +					  unsigned int drate_mode)
>> +{
>> +	const struct ads1x18_chip_info *chip_info = ads1x18->chip_info;
>> +	unsigned long timeout;
>> +	unsigned int sps;
>> +
>
> This could use some comments explaining how we came up with this
> calculation and what the timeout will be used for.
>
>> +	sps = chip_info->sps_table[drate_mode];
>> +	timeout = DIV_ROUND_UP(MICROHZ_PER_HZ, sps);
>> +
>> +	return usecs_to_jiffies(timeout * 2);
>> +}
>> +
>> +static int __ads1x18_read_conver(struct ads1x18 *ads1x18, u16 *cnv)
>> +{
>> +	int ret;
>> +
>> +	ads1x18->tx_buf[0] = 0;
>> +	ads1x18->tx_buf[1] = 0;
>> +	ret = spi_sync_locked(ads1x18->spi, &ads1x18->message);
>> +	if (ret)
>> +		return ret;
>> +
>> +	*cnv = be16_to_cpu(ads1x18->rx_buf[0]);
>> +
>> +	return 0;
>> +}
>> +
>> +static int __ads1x18_write_config(struct ads1x18 *ads1x18, u16 cfg)
>> +{
>> +	ads1x18->tx_buf[0] = cpu_to_be16(cfg);
>> +	ads1x18->tx_buf[1] = 0;
>> +
>> +	return spi_sync_locked(ads1x18->spi, &ads1x18->message);
>> +}
>> +
>> +static int ads1x18_read_conver(struct ads1x18 *ads1x18, u16 *cnv)
>> +{
>> +	int ret;
>> +
>> +	spi_bus_lock(ads1x18->spi->controller);
>
> It is very unusual to manually manage the SPI bus lock. I see later that there
> is a good reason for it. It would be good to mention that in the commit message
> as well.
>
> And it would be helpful to have a few more comments throughout explaining
> which function should be called from where to get proper locking.
>
>> +	ret = __ads1x18_read_conver(ads1x18, cnv);
>> +	spi_bus_unlock(ads1x18->spi->controller);
>> +
>> +	return ret;
>> +}
>> +
>> +static int ads1x18_write_config(struct ads1x18 *ads1x18, u16 cfg)
>> +{
>> +	int ret;
>> +
>> +	spi_bus_lock(ads1x18->spi->controller);
>> +	ret = __ads1x18_write_config(ads1x18, cfg);
>> +	spi_bus_unlock(ads1x18->spi->controller);
>> +
>> +	return ret;
>> +}
>> +
>> +static int ads1x18_oneshot(struct ads1x18 *ads1x18,
>> +			   struct iio_chan_spec const *chan, int *val)
>> +{
>> +	unsigned int drate = ads1x18_get_drate_mode(ads1x18, chan->address);
>> +	unsigned int pga = ads1x18_get_pga_mode(ads1x18, chan->address);
>> +	unsigned long timeout = ads1x18_calc_timeout(ads1x18, drate);
>> +	u16 cnv, cfg = 0;
>> +	int ret;
>> +
>> +	reinit_completion(&ads1x18->data_ready);
>> +
>> +	cfg |= ADS1X18_CFG_VALID;
>> +	cfg |= ADS1X18_CFG_OS_TRIG;
>> +	cfg |= FIELD_PREP(ADS1X18_CFG_MUX_MASK, chan->address);
>> +	cfg |= FIELD_PREP(ADS1X18_CFG_PGA_MASK, pga);
>> +	cfg |= FIELD_PREP(ADS1X18_CFG_MODE_MASK, ADS1X18_MODE_ONESHOT);
>> +	cfg |= FIELD_PREP(ADS1X18_CFG_DRATE_MASK, drate);
>> +	if (chan->type == IIO_TEMP)
>> +		cfg |= ADS1X18_CFG_TS_MODE_EN;
>> +
>> +	ret = __ads1x18_write_config(ads1x18, cfg);
>> +	if (ret)
>> +		return ret;
>> +	enable_irq(ads1x18->drdy_irq);
>> +
>> +	if (!wait_for_completion_timeout(&ads1x18->data_ready, timeout)) {
>> +		disable_irq(ads1x18->drdy_irq);
>> +		return -ETIMEDOUT;
>> +	}
>> +	disable_irq(ads1x18->drdy_irq);
>> +
>> +	ret = __ads1x18_read_conver(ads1x18, &cnv);
>> +	if (ret)
>> +		return ret;
>> +
>> +	cnv >>= chan->scan_type.shift;
>> +	*val = sign_extend32(cnv, chan->scan_type.realbits - 1);
>
> For direct reads, I would not mess with the interrupt. Unless there is some reason
> (like filtering effects) that the data rate is important when reading a single sample,
> I would just set the sample rate to the lowest value. Then we can create a single
> SPI message using the delay feature of struct spi_xfer that has a delay to match
> the period of the data rate. The SPI message would have to have two transfers, one
> to trigger the conversion and the other to read the data. Then this will also work
> even in cases where the DRDY interrupt is not wired up.
>
> Also, this would allow to simplify the SPI bus lock situation in that we would only
> need to take the lock when starting a buffered read

Hmm.

I like this approach. However I'm still not fully convinced we should
drop the interrupt approach. Mainly because finding a suitable
delay will require taking the worst-case sample rate error, to avoid
stale readings.

Shouldn't be the end of the world, but it would definitely be nerf that
IMO it's maybe unnecessary(? I do agree we should max sample rate on
single-shot readings either way.

I'll do some testing with this approach.

>
>> +
>> +	return ret;
>> +}
>> +
>> +static int
>> +ads1x18_read_raw(struct iio_dev *indio_dev, struct iio_chan_spec const *chan,
>> +		 int *val, int *val2, long mask)
>> +{
>> +	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
>> +	struct ads1x18_chan_data *chan_info = &ads1x18->channels[chan->address];
>> +	const struct ads1x18_chip_info *chip_info = ads1x18->chip_info;
>> +	int ret;
>> +
>> +	guard(mutex)(&ads1x18->msg_lock);
>
> Yup,  there is already iio_device_claim_direct() in use here so this
> mutex seems redundant.
>
>> +
>> +	switch (mask) {
>> +	case IIO_CHAN_INFO_RAW:
>> +		if (!iio_device_claim_direct(indio_dev))
>> +			return -EBUSY;
>> +		/* CS needs to remain asserted until dataready IRQ */
>> +		spi_bus_lock(ads1x18->spi->controller);
>> +
>> +		ret = ads1x18_oneshot(ads1x18, chan, val);
>> +
>> +		spi_bus_unlock(ads1x18->spi->controller);
>> +		iio_device_release_direct(indio_dev);
>> +
>> +		if (ret)
>> +			return ret;
>> +
>> +		return IIO_VAL_INT;
>> +
>> +	case IIO_CHAN_INFO_SCALE:
>> +		switch (chan->type) {
>> +		case IIO_VOLTAGE:
>> +			*val = chip_info->fsr_table[chan_info->pga_mode][0];
>> +			*val2 = chip_info->fsr_table[chan_info->pga_mode][1];
>> +			return IIO_VAL_INT_PLUS_NANO;
>> +
>> +		case IIO_TEMP:
>> +			*val = chip_info->temp_scale[0];
>> +			*val2 = chip_info->temp_scale[1];
>> +			return IIO_VAL_INT_PLUS_MICRO;
>> +
>> +		default:
>> +			return -EOPNOTSUPP;
>> +		}
>> +
>> +	case IIO_CHAN_INFO_SAMP_FREQ:
>> +		*val = chip_info->sps_table[chan_info->drate_mode];
>> +		return IIO_VAL_INT;
>> +
>> +	default:
>> +		return -EOPNOTSUPP;
>> +	}
>> +}
>> +
>> +static int
>> +ads1x18_read_avail(struct iio_dev *indio_dev, struct iio_chan_spec const *chan,
>> +		   const int **vals, int *type, int *length, long mask)
>> +{
>> +	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
>> +
>> +	switch (mask) {
>> +	case IIO_CHAN_INFO_SCALE:
>> +		*type = IIO_VAL_INT_PLUS_NANO;
>> +		*vals = (const int *)ads1x18->chip_info->fsr_table;
>> +		*length = ads1x18->chip_info->fsr_table_sz * 2;
>> +		return IIO_AVAIL_LIST;
>> +
>> +	case IIO_CHAN_INFO_SAMP_FREQ:
>> +		*type = IIO_VAL_INT;
>> +		*vals = ads1x18->chip_info->sps_table;
>> +		*length = ads1x18->chip_info->sps_table_sz;
>> +		return IIO_AVAIL_LIST;
>> +
>> +	default:
>> +		return -EOPNOTSUPP;
>> +	}
>> +}
>> +
>> +static int
>> +ads1x18_write_raw(struct iio_dev *indio_dev, struct iio_chan_spec const *chan,
>> +		  int val, int val2, long mask)
>> +{
>> +	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
>> +	const struct ads1x18_chip_info *info = ads1x18->chip_info;
>> +	unsigned int i = 0;
>
> Strange way to initialize a for loop. I would just do it normally.
>
>> +
>> +	guard(mutex)(&ads1x18->msg_lock);
>> +
>> +	switch (mask) {
>> +	case IIO_CHAN_INFO_SCALE:
>> +		for (; i < info->fsr_table_sz; i++) {
>> +			if (val != info->fsr_table[i][0] ||
>> +			    val2 != info->fsr_table[i][1])
>> +				continue;
>> +
>> +			ads1x18_set_pga_mode(ads1x18, chan->address, i);
>> +			return 0;
>> +		}
>> +
>> +		return -EINVAL;
>> +
>> +	case IIO_CHAN_INFO_SAMP_FREQ:
>> +		for (; i < info->sps_table_sz; i++) {
>> +			if (val != info->sps_table[i])
>> +				continue;
>> +
>> +			ads1x18_set_drate_mode(ads1x18, chan->address, i);
>> +			return 0;
>> +		}
>> +
>> +		return -EINVAL;
>> +
>> +	default:
>> +		return -EOPNOTSUPP;
>> +	}
>> +}
>> +
>> +static int
>> +ads1x18_write_raw_get_fmt(struct iio_dev *indio_dev,
>> +			  struct iio_chan_spec const *chan, long mask)
>> +{
>> +	switch (mask) {
>> +	case IIO_CHAN_INFO_SCALE:
>> +		return IIO_VAL_INT_PLUS_NANO;
>> +	default:
>> +		return IIO_VAL_INT_PLUS_MICRO;
>> +	}
>> +}
>> +
>> +static const struct iio_info ads1x18_iio_info = {
>> +	.read_raw = ads1x18_read_raw,
>> +	.read_avail = ads1x18_read_avail,
>> +	.write_raw = ads1x18_write_raw,
>> +	.write_raw_get_fmt = ads1x18_write_raw_get_fmt,
>> +};
>> +
>> +static int ads1x18_set_trigger_state(struct iio_trigger *trig, bool state)
>> +{
>> +	struct ads1x18 *ads1x18 = iio_trigger_get_drvdata(trig);
>> +	u16 cnv;
>> +
>> +	guard(mutex)(&ads1x18->msg_lock);
>> +
>> +	/*
>> +	 * We need to lock the SPI bus when enabling the trigger to prevent
>> +	 * another device from taking the CS and DOUT/DRDY lines.
>> +	 */
>> +
>> +	if (state) {
>> +		spi_bus_lock(ads1x18->spi->controller);
>> +		enable_irq(ads1x18->drdy_irq);
>> +
>> +		/*
>> +		 * Read once to ensure we are holding the CS line after locking
>> +		 */
>> +		return __ads1x18_read_conver(ads1x18, &cnv);

There is a mistake here. I should read before enabling the IRQ and do
proper cleanup. I'll fix it.

>
> It is a bit confusing to have this here rather than in the buffer
> enable callback since that is also setting the config that triggers
> the first conversion.
>
> Having the spi_bus_lock() and enable_irq() in the buffer enable
> would make more sense to me too.

This is the approach ad_sigma_delta takes.

>
> It should also be possible to use the chip without the interrupt
> by using delay to wait for conversions, so perhaps we could make
> the case for doing the enable_irq() here. But for sure spi_bus_lock()
> would need to be in the buffer enable callback.

I separated the logic to be able to assign a different trigger to this
buffer and in that case I think we shouldn't lock the bus. That way
other SPI devices may use it while buffer is active and the trigger is
not.

>
>> +	}
>> +
>> +	disable_irq(ads1x18->drdy_irq);
>> +	spi_bus_unlock(ads1x18->spi->controller);
>> +
>> +	return 0;
>> +}
>> +
>> +static const struct iio_trigger_ops ads1x18_trigger_ops = {
>> +	.set_trigger_state = ads1x18_set_trigger_state,
>> +	.validate_device = iio_trigger_validate_own_device,
>> +};
>> +
>> +static int ads1x18_buffer_preenable(struct iio_dev *indio_dev)
>> +{
>> +	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
>> +	unsigned int pga, drate, addr, idx;
>> +	u16 cfg = 0;
>> +
>> +	guard(mutex)(&ads1x18->msg_lock);
>> +
>> +	idx = find_first_bit(indio_dev->active_scan_mask,
>> +			     iio_get_masklength(indio_dev));
>> +	addr = ads1x18->bufidx_to_addr[idx];
>> +	pga = ads1x18_get_pga_mode(ads1x18, addr);
>> +	drate = ads1x18_get_drate_mode(ads1x18, addr);
>> +
>> +	cfg |= ADS1X18_CFG_VALID;
>> +	cfg |= FIELD_PREP(ADS1X18_CFG_MUX_MASK, addr);
>> +	cfg |= FIELD_PREP(ADS1X18_CFG_PGA_MASK, pga);
>> +	cfg |= FIELD_PREP(ADS1X18_CFG_MODE_MASK, ADS1X18_MODE_CONTINUOUS);
>> +	cfg |= FIELD_PREP(ADS1X18_CFG_DRATE_MASK, drate);
>> +	if (addr == ADS1X18_TEMP_ADDR)
>> +		cfg |= ADS1X18_CFG_TS_MODE_EN;
>> +
>> +	return ads1x18_write_config(ads1x18, cfg);
>> +}
>> +
>> +static int ads1x18_buffer_postdisable(struct iio_dev *indio_dev)
>> +{
>> +	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
>> +
>> +	guard(mutex)(&ads1x18->msg_lock);
>> +
>> +	return ads1x18_write_config(ads1x18, ADS1X18_CFG_DEFAULT);
>> +}
>> +
>> +static bool ads1x18_validate_scan_mask(struct iio_dev *indio_dev,
>> +				       const unsigned long *mask)
>> +{
>> +	return bitmap_weight(mask, iio_get_masklength(indio_dev)) == 1;
>> +}
>> +
>> +static const struct iio_buffer_setup_ops ads1x18_buffer_ops = {
>> +	.preenable = ads1x18_buffer_preenable,
>> +	.postdisable = ads1x18_buffer_postdisable,
>> +	.validate_scan_mask = ads1x18_validate_scan_mask,
>> +};
>> +
>> +static irqreturn_t ads1x18_irq_handler(int irq, void *dev_id)
>> +{
>> +	struct ads1x18 *ads1x18 = dev_id;
>> +
>> +	/*
>> +	 * We need to check if the "drdy" pin is actually active or if it's a
>> +	 * latched pending interrupt.
>> +	 */
>> +	if (!gpiod_get_value(ads1x18->drdy_gpiod))
>> +		return IRQ_HANDLED;
>> +
>> +	complete(&ads1x18->data_ready);
>> +	iio_trigger_poll(ads1x18->indio_trig);
>> +
>> +	return IRQ_HANDLED;
>> +}
>> +
>> +static int ads1x18_interrupt_init(struct ads1x18 *ads1x18)
>> +{
>> +	const struct ads1x18_chip_info *info = ads1x18->chip_info;
>> +	struct spi_device *spi = ads1x18->spi;
>> +
>> +	ads1x18->drdy_gpiod = devm_gpiod_get(&spi->dev, "drdy", GPIOD_IN);
>> +	if (IS_ERR(ads1x18->drdy_gpiod))
>> +		return dev_err_probe(&spi->dev, PTR_ERR(ads1x18->drdy_gpiod),
>> +				     "Failed to get 'drdy' GPIO.\n");
>> +
>
> According the the dt-bindings, the interrupt could be separate from the
> gpio. The SPI framework already looks up the first interrupts node if there
> is one, so this could be
>
> 	if (spi->irq)
> 		ads1x18->drdy_irq = spi->irq;
> 	else
>
>> +	ads1x18->drdy_irq = gpiod_to_irq(ads1x18->drdy_gpiod);
>> +	if (ads1x18->drdy_irq < 0)
>> +		return dev_err_probe(&spi->dev, ads1x18->drdy_irq,
>> +				     "Failed to get 'drdy IRQ.\n'");
>> +
>> +	/*
>> +	 * The "data-ready" IRQ line is shared with the MOSI pin, thus we need
>> +	 * to keep it disabled until we actually request data.
>> +	 */
>> +	return devm_request_irq(&spi->dev, ads1x18->drdy_irq,
>> +				ads1x18_irq_handler, IRQF_NO_AUTOEN,
>> +				info->name, ads1x18);
>> +}
>> +
>> +static irqreturn_t ads1x18_trigger_handler(int irq, void *p)
>> +{
>> +	struct iio_poll_func *pf = p;
>> +	struct iio_dev *indio_dev = pf->indio_dev;
>> +	struct ads1x18 *ads1x18 = iio_priv(indio_dev);
>> +	struct {
>> +		u16 conv;
>> +		aligned_s64 ts;
>> +	} scan;
>
> Need to 0-initilze with = { }; to avoid leaking uninitialized stack data.
>
>> +	int ret;
>> +
>> +	guard(mutex)(&ads1x18->msg_lock);
>> +
>> +	if (iio_trigger_using_own(indio_dev)) {
>> +		disable_irq(ads1x18->drdy_irq);
>> +		ret = __ads1x18_read_conver(ads1x18, &scan.conv);
>> +		enable_irq(ads1x18->drdy_irq);
>> +	} else {
>> +		ret = ads1x18_read_conver(ads1x18, &scan.conv);
>> +	}
>> +
>> +	if (ret)
>> +		return IRQ_HANDLED;
>> +
>> +	ret = iio_push_to_buffers_with_ts(indio_dev, &scan, sizeof(scan),
>> +					  pf->timestamp);
>> +	if (!ret)
>> +		iio_trigger_notify_done(ads1x18->indio_trig);
>
> Pretty sure we need to notify doen even in case of error, otherwise
> we can get a deadlock.
>
> In interrupt handlers our only choice is to ignore errors or do rate-limted
> logging of them.
>
>> +
>> +	return IRQ_HANDLED;
>> +}
>> +
>> +static int ads1x18_triggered_buffer_init(struct ads1x18 *ads1x18)
>> +{
>> +	struct iio_dev *indio_dev = ads1x18->indio_dev;
>> +	struct spi_device *spi = ads1x18->spi;
>> +	int ret;
>> +
>> +	ads1x18->indio_trig = devm_iio_trigger_alloc(&spi->dev, "%s-dev%d-drdy",
>> +						     indio_dev->name,
>> +						     iio_device_id(indio_dev));
>> +	if (!ads1x18->indio_trig)
>> +		return -ENOMEM;
>> +
>> +	iio_trigger_set_drvdata(ads1x18->indio_trig, ads1x18);
>> +	ads1x18->indio_trig->ops = &ads1x18_trigger_ops;
>> +
>> +	ret = devm_iio_trigger_register(&spi->dev, ads1x18->indio_trig);
>> +	if (ret)
>> +		return ret;
>> +
>> +	return devm_iio_triggered_buffer_setup(&spi->dev, indio_dev,
>> +					       iio_pollfunc_store_time,
>> +					       ads1x18_trigger_handler,
>> +					       &ads1x18_buffer_ops);
>> +}
>> +
>> +static int ads1x18_message_init(struct ads1x18 *ads1x18)
>> +{
>> +	struct spi_device *spi = ads1x18->spi;
>> +
>> +	/*
>> +	 * We need to keep CS asserted to catch "data-ready" interrupts.
>> +	 * Otherwise the DOUT/DRDY line enters a Hi-Z state and it can't be
>> +	 * driven by the ADC.
>> +	 */
>> +	ads1x18->xfer.cs_change = 1;
>
> I think this is going to be problamatic for reading/writing the configuration
> register and for direct reads of a single sample. My suggestion to make a

Can you elaborate on why it would be problematic?

> separate message with 2 xfers for the single read will partiall solve it.
> And we could just use spi_write() for writing the config register.
>
>> +	ads1x18->xfer.tx_buf = ads1x18->tx_buf;
>> +	ads1x18->xfer.rx_buf = ads1x18->rx_buf;
>> +	ads1x18->xfer.len = sizeof(ads1x18->tx_buf);
>> +	spi_message_init_no_memset(&ads1x18->message);
>> +	spi_message_add_tail(&ads1x18->xfer, &ads1x18->message);
>
> Can be simplifed with spi_message_init_with_transfers().
>
>> +
>> +	return devm_spi_optimize_message(&spi->dev, spi, &ads1x18->message);
>> +}
>> +
>> +static int ads1x18_fill_properties(struct ads1x18 *ads1x18,
>> +				   struct fwnode_handle *handle,
>> +				   struct iio_chan_spec *chan)
>> +{
>> +	const struct ads1x18_chip_info *info = ads1x18->chip_info;
>> +	struct ads1x18_chan_data *chan_data;
>> +	u32 val, reg;
>> +	int ret;
>> +
>> +	ret = fwnode_property_read_u32(handle, "reg", &reg);
>> +	if (ret)
>> +		return ret;
>> +	if (reg > ADS1X18_MAX_ADC_ADDR)
>> +		return dev_err_probe(&ads1x18->spi->dev, -ENXIO,
>> +				     "%s: Invalid channel address %u.\n",
>> +				     fwnode_get_name(handle), reg);
>> +
>> +	*chan = info->channels[reg];
>> +
>> +	chan_data = &ads1x18->channels[reg];
>> +	chan_data->pga_mode = ADS1X18_PGA_DEFAULT;
>> +	chan_data->drate_mode = ADS1X18_DRATE_DEFAULT;
>> +
>> +	if (fwnode_property_present(handle, "ti,gain")) {
>> +		ret = fwnode_property_read_u32(handle, "ti,gain", &val);
>> +		if (ret)
>> +			return ret;
>> +		if (val >= info->fsr_table_sz)
>> +			return dev_err_probe(&ads1x18->spi->dev, -ENXIO,
>> +					     "%s: ti,gain not in range.",
>> +					     fwnode_get_name(handle));
>> +
>> +		chan_data->pga_mode = val;
>> +	}
>> +
>> +	if (fwnode_property_present(handle, "ti,datarate")) {
>> +		ret = fwnode_property_read_u32(handle, "ti,datarate", &val);
>> +		if (ret)
>> +			return ret;
>> +		if (val >= info->sps_table_sz)
>> +			return dev_err_probe(&ads1x18->spi->dev, -ENXIO,
>> +					     "%s: ti,datarate not in range.",
>> +					     fwnode_get_name(handle));
>> +
>> +		chan_data->drate_mode = val;
>> +	}
>
> As mentioned in the dt-bindings review. We don't set an initial value
> from the devicetree like this. So we should be able to drop all of this.

I will!

>
>> +
>> +	return 0;
>> +}
>> +
>> +static int ads1x18_channels_init(struct ads1x18 *ads1x18,
>> +				 const struct ads1x18_chip_info *info,
>> +				 struct iio_chan_spec **cs)
>> +{
>> +	struct device *dev = &ads1x18->spi->dev;
>> +	struct iio_chan_spec *channels;
>> +	int ret, nchans, index = 0;
>> +
>> +	nchans = device_get_named_child_node_count(dev, "channel");
>> +	if (!nchans)
>> +		return dev_err_probe(dev, -ENODEV,
>> +				     "No ADC channels described.\n");
>> +
>> +	channels = devm_kcalloc(dev, nchans + 2, sizeof(*channels), GFP_KERNEL);
>> +	if (!channels)
>> +		return -ENOMEM;
>> +
>> +	device_for_each_named_child_node_scoped(dev, child, "channel") {
>> +		ret = ads1x18_fill_properties(ads1x18, child, &channels[index]);
>> +		if (ret)
>> +			return ret;
>> +
>> +		channels[index].scan_index = index;
>> +		ads1x18->bufidx_to_addr[index] = channels[index].address;
>> +		index++;
>> +	}
>
> There is a small enough number of channels that we shouldn't need any of this.
> We can just make an array big enough for all channels in struct ads1x18.

Ack.

Do you think we should just let every channel be visible in sysfs or
should we still control visibility with the channel@[0-7] node?

>
>> +
>> +	ads1x18->channels[ADS1X18_TEMP_ADDR].drate_mode = ADS1X18_DRATE_DEFAULT;
>> +	channels[index] = info->channels[ADS1X18_TEMP_ADDR];
>> +	channels[index].scan_index = index;
>> +	ads1x18->bufidx_to_addr[index] = channels[index].address;
>> +	index++;
>> +
>> +	channels[index] = info->channels[ADS1X18_TIMESTAMP_ADDR];
>> +	ads1x18->bufidx_to_addr[index] = channels[index].address;
>> +
>> +	*cs = channels;
>> +
>> +	return index;
>> +}
>> +
>> +static int ads1x18_spi_probe(struct spi_device *spi)
>> +{
>> +	const struct ads1x18_chip_info *info = spi_get_device_match_data(spi);
>> +	struct iio_chan_spec *channels;
>> +	struct iio_dev *indio_dev;
>> +	struct ads1x18 *ads1x18;
>> +	int num_channels, ret;
>> +
>> +	indio_dev = devm_iio_device_alloc(&spi->dev, sizeof(*ads1x18));
>> +	if (!indio_dev)
>> +		return -ENOMEM;
>> +
>> +	ads1x18 = iio_priv(indio_dev);
>> +	ads1x18->spi = spi;
>> +	ads1x18->indio_dev = indio_dev;
>
> Usually, we can write code so that a pointer back to indio_dev is not needed.
>
>> +	ads1x18->chip_info = info;
>> +	mutex_init(&ads1x18->msg_lock);
>> +	init_completion(&ads1x18->data_ready);
>> +	spi_set_drvdata(spi, ads1x18);
>
> There is no spi_get_drvdata(), so we don't need this.

I do however use dev_get_drvdata() directly in PM ops.

>
>> +
>> +	num_channels = ads1x18_channels_init(ads1x18, info, &channels);
>> +	if (num_channels < 0)
>> +		return num_channels;
>> +	indio_dev->modes = INDIO_DIRECT_MODE;
>> +	indio_dev->name = info->name;
>> +	indio_dev->info = &ads1x18_iio_info;
>> +	indio_dev->channels = channels;
>> +	indio_dev->num_channels = num_channels;
>> +
>> +	ret = ads1x18_message_init(ads1x18);
>> +	if (ret)
>> +		return ret;
>> +
>> +	ret = ads1x18_triggered_buffer_init(ads1x18);
>> +	if (ret)
>> +		return ret;
>> +
>> +	ret = ads1x18_interrupt_init(ads1x18);
>> +	if (ret)
>> +		return ret;
>> +
>> +	return devm_iio_device_register(&spi->dev, indio_dev);
>> +}
>> +
>> +static int ads1x18_suspend(struct device *dev)
>> +{
>> +	struct ads1x18 *ads1x18 = dev_get_drvdata(dev);
>> +	u16 cfg;
>> +	int ret;
>> +
>> +	guard(mutex)(&ads1x18->msg_lock);
>> +
>> +	/* Current config is readback into rx_buf[1] */
>> +	cfg = be16_to_cpu(ads1x18->rx_buf[1]);
>> +	if (FIELD_GET(ADS1X18_CFG_MODE_MASK, cfg) == ADS1X18_MODE_ONESHOT)
>> +		return 0;
>> +
>> +	cfg |= FIELD_PREP(ADS1X18_CFG_MODE_MASK, ADS1X18_MODE_ONESHOT);
>> +	ret = ads1x18_write_config(ads1x18, cfg);
>> +	if (ret)
>> +		return ret;
>> +
>> +	ads1x18->restore_mode = 1;
>> +
>> +	return 0;
>> +}
>> +
>> +static int ads1x18_resume(struct device *dev)
>> +{
>> +	struct ads1x18 *ads1x18 = dev_get_drvdata(dev);
>> +	u16 cfg;
>> +	int ret;
>> +
>> +	guard(mutex)(&ads1x18->msg_lock);
>> +
>> +	if (!ads1x18->restore_mode)
>> +		return 0;
>> +
>> +	cfg = be16_to_cpu(ads1x18->rx_buf[1]);
>> +	FIELD_MODIFY(ADS1X18_CFG_MODE_MASK, &cfg, ADS1X18_MODE_CONTINUOUS);
>> +	ret = ads1x18_write_config(ads1x18, cfg);
>> +	if (ret)
>> +		return ret;
>> +
>> +	ads1x18->restore_mode = 0;
>> +
>> +	return 0;
>> +}
>
> I think we could simplify this and avoid needing to use pm runtime (and use
> even less power!). During probe, put the chip in power down mode. When doing
> direct reads of a single value, put the chip in single-shot mode. When doing
> starting a buffered read, put it in continuous mode and when the buffered read
> is stopped, put it back in shutdown mode.

These chips only have two modes single-shot (low-power) and continuous.
Are you suggesting we shut it down using the vdd regulator?

Either way, can't the system go to sleep while in buffer mode? If that's
the case we should still need these handlers.

>
>> +
>> +static DEFINE_SIMPLE_DEV_PM_OPS(ads1x18_pm_ops, ads1x18_suspend, ads1x18_resume);
>> +
>> +static const int ads1118_fsr_table[][2] = {
>> +	[ADS1X18_PGA_MODE_0] = { 0, 187500 },
>> +	[ADS1X18_PGA_MODE_1] = { 0, 125000 },
>> +	[ADS1X18_PGA_MODE_2] = { 0, 62500 },
>> +	[ADS1X18_PGA_MODE_3] = { 0, 31250 },
>> +	[ADS1X18_PGA_MODE_4] = { 0, 15625 },
>> +	[ADS1X18_PGA_MODE_5] = { 0, 7812 }
>> +};
>> +
>> +static const int ads1018_fsr_table[][2] = {
>> +	[ADS1X18_PGA_MODE_0] = { 0, 3000000 },
>> +	[ADS1X18_PGA_MODE_1] = { 0, 2000000 },
>> +	[ADS1X18_PGA_MODE_2] = { 0, 1000000 },
>> +	[ADS1X18_PGA_MODE_3] = { 0, 500000 },
>> +	[ADS1X18_PGA_MODE_4] = { 0, 250000 },
>> +	[ADS1X18_PGA_MODE_5] = { 0, 125000 }
>> +};
>> +
>> +static const unsigned int ads1018_drate_table[] = {
>> +	[ADS1X18_DRATE_MODE_0] = 128,
>> +	[ADS1X18_DRATE_MODE_1] = 250,
>> +	[ADS1X18_DRATE_MODE_2] = 490,
>> +	[ADS1X18_DRATE_MODE_3] = 920,
>> +	[ADS1X18_DRATE_MODE_4] = 1600,
>> +	[ADS1X18_DRATE_MODE_5] = 2400,
>> +	[ADS1X18_DRATE_MODE_6] = 3300
>> +};
>> +
>> +static const unsigned int ads1118_drate_table[] = {
>> +	[ADS1X18_DRATE_MODE_0] = 8,
>> +	[ADS1X18_DRATE_MODE_1] = 16,
>> +	[ADS1X18_DRATE_MODE_2] = 32,
>> +	[ADS1X18_DRATE_MODE_3] = 64,
>> +	[ADS1X18_DRATE_MODE_4] = 128,
>> +	[ADS1X18_DRATE_MODE_5] = 250,
>> +	[ADS1X18_DRATE_MODE_6] = 475,
>> +	[ADS1X18_DRATE_MODE_7] = 860
>> +};
>
> These table could use more descriptive names or comments that exlain what
> sort of mapping they are doing.
>
>> +
>> +static const struct ads1x18_chip_info ads1018_chip_info = {
>> +	.name = "ads1018",
>> +
>> +	.channels = ads1018_iio_channels,
>> +	.channels_sz = ARRAY_SIZE(ads1018_iio_channels),
>> +
>> +	.fsr_table = ads1018_fsr_table,
>> +	.fsr_table_sz = ARRAY_SIZE(ads1018_fsr_table),
>> +	.sps_table = ads1018_drate_table,
>> +	.sps_table_sz = ARRAY_SIZE(ads1018_drate_table),
>> +	.temp_scale = { 0, 125000 },
>> +};
>> +
>> +static const struct ads1x18_chip_info ads1118_chip_info = {
>> +	.name = "ads1118",
>> +
>> +	.channels = ads1118_iio_channels,
>> +	.channels_sz = ARRAY_SIZE(ads1118_iio_channels),
>> +
>> +	.fsr_table = ads1118_fsr_table,
>> +	.fsr_table_sz = ARRAY_SIZE(ads1118_fsr_table),
>> +	.sps_table = ads1118_drate_table,
>> +	.sps_table_sz = ARRAY_SIZE(ads1118_drate_table),
>> +	.temp_scale = { 0, 31250 },
>> +};
>> +
>> +static const struct of_device_id ads1x18_of_match[] = {
>> +	{ .compatible = "ti,ads1018", .data = &ads1018_chip_info },
>> +	{ .compatible = "ti,ads1118", .data = &ads1118_chip_info },
>> +	{ }
>> +};
>> +MODULE_DEVICE_TABLE(of, ads1x18_of_match);
>> +
>> +static const struct spi_device_id ads1x18_spi_match[] = {
>> +	{ "ads1018", (kernel_ulong_t)&ads1018_chip_info },
>> +	{ "ads1118", (kernel_ulong_t)&ads1118_chip_info },
>> +	{ }
>> +};
>> +MODULE_DEVICE_TABLE(spi, ads1x18_spi_match);
>> +
>> +static struct spi_driver ads1x18_spi_driver = {
>> +	.driver = {
>> +		.name = "ads1x18",
>
> No x here either.
>
>> +		.of_match_table = ads1x18_of_match,
>> +		.pm = pm_sleep_ptr(&ads1x18_pm_ops),
>> +	},
>> +	.probe = ads1x18_spi_probe,
>> +	.id_table = ads1x18_spi_match,
>> +};
>> +
>> +module_spi_driver(ads1x18_spi_driver);
>> +
>> +MODULE_DESCRIPTION("Texas Instruments ADS1X18 ADC Driver");
>
> or here.
>
>> +MODULE_LICENSE("GPL");
>> +MODULE_AUTHOR("Kurt Borja <kuurtb@gmail.com>");
>> 

Ack for everything else.

Thank you so much for your detailed review :)


-- 
 ~ Kurt

Re: [PATCH 2/2] iio: adc: Add ti-ads1x18 driver

[David Lechner]

On 11/21/25 6:24 PM, Kurt Borja wrote:
> On Fri Nov 21, 2025 at 5:33 PM -05, David Lechner wrote:
>> On 11/21/25 11:16 AM, Kurt Borja wrote:
>>

...

>> #define ADS1018_CFG_REG			0x0000
> 
> I didn't define these because ads1118 dumps all registers (2) in each
> transfer.

Oh, right, there is basically only one register so we don't have to
address it. :-)


>>
>> It is a bit confusing to have this here rather than in the buffer
>> enable callback since that is also setting the config that triggers
>> the first conversion.
>>
>> Having the spi_bus_lock() and enable_irq() in the buffer enable
>> would make more sense to me too.
> 
> This is the approach ad_sigma_delta takes.
> 

I did some work on that with that module recently. I would not say that
it is an ideal reference. IIRC, it still has some race condition with
enabling/disabling interrupts in some cases. So hopefully we can do better
here.

>>> +
>>> +static int ads1x18_message_init(struct ads1x18 *ads1x18)
>>> +{
>>> +	struct spi_device *spi = ads1x18->spi;
>>> +
>>> +	/*
>>> +	 * We need to keep CS asserted to catch "data-ready" interrupts.
>>> +	 * Otherwise the DOUT/DRDY line enters a Hi-Z state and it can't be
>>> +	 * driven by the ADC.
>>> +	 */
>>> +	ads1x18->xfer.cs_change = 1;
>>
>> I think this is going to be problematic for reading/writing the configuration
>> register and for direct reads of a single sample. My suggestion to make a
> 
> Can you elaborate on why it would be problematic?

This transfer is used for all SPI messages. So it means that CS will still
be high after every transfer, not just the ones during a buffered read where
it is actually needed.

This would be a problem if there were any other devices on the SPI bus.
When the controller communicates with the other device, the ADC will
still be listening and responding because CS is still high.


>>> +
>>> +static int ads1x18_channels_init(struct ads1x18 *ads1x18,
>>> +				 const struct ads1x18_chip_info *info,
>>> +				 struct iio_chan_spec **cs)
>>> +{
>>> +	struct device *dev = &ads1x18->spi->dev;
>>> +	struct iio_chan_spec *channels;
>>> +	int ret, nchans, index = 0;
>>> +
>>> +	nchans = device_get_named_child_node_count(dev, "channel");
>>> +	if (!nchans)
>>> +		return dev_err_probe(dev, -ENODEV,
>>> +				     "No ADC channels described.\n");
>>> +
>>> +	channels = devm_kcalloc(dev, nchans + 2, sizeof(*channels), GFP_KERNEL);
>>> +	if (!channels)
>>> +		return -ENOMEM;
>>> +
>>> +	device_for_each_named_child_node_scoped(dev, child, "channel") {
>>> +		ret = ads1x18_fill_properties(ads1x18, child, &channels[index]);
>>> +		if (ret)
>>> +			return ret;
>>> +
>>> +		channels[index].scan_index = index;
>>> +		ads1x18->bufidx_to_addr[index] = channels[index].address;
>>> +		index++;
>>> +	}
>>
>> There is a small enough number of channels that we shouldn't need any of this.
>> We can just make an array big enough for all channels in struct ads1x18.
> 
> Ack.
> 
> Do you think we should just let every channel be visible in sysfs or
> should we still control visibility with the channel@[0-7] node?

Yes. It is normal to show all channels. The few exceptions, like multiplexed
chips where there can be 100s or 1000s of possible combinations of differential
channels possible. And sometimes for ADCs built into a SoC, we omit the channels
that aren't wired up to something.

It makes it much easier to write userspace software though if every instance
of the ADC has exactly the same attributes, so I try to advocate for that.


>>> +	ads1x18->chip_info = info;
>>> +	mutex_init(&ads1x18->msg_lock);
>>> +	init_completion(&ads1x18->data_ready);
>>> +	spi_set_drvdata(spi, ads1x18);
>>
>> There is no spi_get_drvdata(), so we don't need this.
> 
> I do however use dev_get_drvdata() directly in PM ops.
> 

OK, so dev_set_drvdata() would make it symmetric.


>>
>> I think we could simplify this and avoid needing to use pm runtime (and use
>> even less power!). During probe, put the chip in power down mode. When doing
>> direct reads of a single value, put the chip in single-shot mode. When doing
>> starting a buffered read, put it in continuous mode and when the buffered read
>> is stopped, put it back in shutdown mode.
> 
> These chips only have two modes single-shot (low-power) and continuous.
> Are you suggesting we shut it down using the vdd regulator?
> 
> Either way, can't the system go to sleep while in buffer mode? If that's
> the case we should still need these handlers.
> 

I hope not. I would suspect that most IIO drivers are broken in this
regard. I've never attempted to try to implement suspend/resume in an
IIO driver yet because I didn't have an application that required it
and it would be very difficult to get right without very extensive
testing.

Re: [PATCH 2/2] iio: adc: Add ti-ads1x18 driver

[Kurt Borja]

On Sat Nov 22, 2025 at 10:56 AM -05, David Lechner wrote:
> On 11/21/25 6:24 PM, Kurt Borja wrote:
>> On Fri Nov 21, 2025 at 5:33 PM -05, David Lechner wrote:
>>> On 11/21/25 11:16 AM, Kurt Borja wrote:
>>>
>
> ...
>
>>> #define ADS1018_CFG_REG			0x0000
>> 
>> I didn't define these because ads1118 dumps all registers (2) in each
>> transfer.
>
> Oh, right, there is basically only one register so we don't have to
> address it. :-)
>
>
>>>
>>> It is a bit confusing to have this here rather than in the buffer
>>> enable callback since that is also setting the config that triggers
>>> the first conversion.
>>>
>>> Having the spi_bus_lock() and enable_irq() in the buffer enable
>>> would make more sense to me too.
>> 
>> This is the approach ad_sigma_delta takes.
>> 
>
> I did some work on that with that module recently. I would not say that
> it is an ideal reference. IIRC, it still has some race condition with
> enabling/disabling interrupts in some cases. So hopefully we can do better
> here.

Oh - I meant haveing spi_bus_lock() and enable_irq() in buffer enable is
the approach ad_sigma_delta takes.

I moved them to set_trigger_state() to be able to use other triggers.
Furthermore if interrupts or drdy-gpios are not defined, we don't really
have to take spi_bus_lock() and doing it this way ensures that.

For this reason I would like to keep this for v2 and we can discuss it
further if you disagree.

>
>>>> +
>>>> +static int ads1x18_message_init(struct ads1x18 *ads1x18)
>>>> +{
>>>> +	struct spi_device *spi = ads1x18->spi;
>>>> +
>>>> +	/*
>>>> +	 * We need to keep CS asserted to catch "data-ready" interrupts.
>>>> +	 * Otherwise the DOUT/DRDY line enters a Hi-Z state and it can't be
>>>> +	 * driven by the ADC.
>>>> +	 */
>>>> +	ads1x18->xfer.cs_change = 1;
>>>
>>> I think this is going to be problematic for reading/writing the configuration
>>> register and for direct reads of a single sample. My suggestion to make a
>> 
>> Can you elaborate on why it would be problematic?
>
> This transfer is used for all SPI messages. So it means that CS will still
> be high after every transfer, not just the ones during a buffered read where
> it is actually needed.
>
> This would be a problem if there were any other devices on the SPI bus.
> When the controller communicates with the other device, the ADC will
> still be listening and responding because CS is still high.

Thanks for the heads up!

This was a misunderstading on my part, I thought the SPI core would
de-assert CS if another device requested a transfer.

>
>
>>>> +
>>>> +static int ads1x18_channels_init(struct ads1x18 *ads1x18,
>>>> +				 const struct ads1x18_chip_info *info,
>>>> +				 struct iio_chan_spec **cs)
>>>> +{
>>>> +	struct device *dev = &ads1x18->spi->dev;
>>>> +	struct iio_chan_spec *channels;
>>>> +	int ret, nchans, index = 0;
>>>> +
>>>> +	nchans = device_get_named_child_node_count(dev, "channel");
>>>> +	if (!nchans)
>>>> +		return dev_err_probe(dev, -ENODEV,
>>>> +				     "No ADC channels described.\n");
>>>> +
>>>> +	channels = devm_kcalloc(dev, nchans + 2, sizeof(*channels), GFP_KERNEL);
>>>> +	if (!channels)
>>>> +		return -ENOMEM;
>>>> +
>>>> +	device_for_each_named_child_node_scoped(dev, child, "channel") {
>>>> +		ret = ads1x18_fill_properties(ads1x18, child, &channels[index]);
>>>> +		if (ret)
>>>> +			return ret;
>>>> +
>>>> +		channels[index].scan_index = index;
>>>> +		ads1x18->bufidx_to_addr[index] = channels[index].address;
>>>> +		index++;
>>>> +	}
>>>
>>> There is a small enough number of channels that we shouldn't need any of this.
>>> We can just make an array big enough for all channels in struct ads1x18.
>> 
>> Ack.
>> 
>> Do you think we should just let every channel be visible in sysfs or
>> should we still control visibility with the channel@[0-7] node?
>
> Yes. It is normal to show all channels. The few exceptions, like multiplexed
> chips where there can be 100s or 1000s of possible combinations of differential
> channels possible. And sometimes for ADCs built into a SoC, we omit the channels
> that aren't wired up to something.
>
> It makes it much easier to write userspace software though if every instance
> of the ADC has exactly the same attributes, so I try to advocate for that.

Agreed.

>
>
>>>> +	ads1x18->chip_info = info;
>>>> +	mutex_init(&ads1x18->msg_lock);
>>>> +	init_completion(&ads1x18->data_ready);
>>>> +	spi_set_drvdata(spi, ads1x18);
>>>
>>> There is no spi_get_drvdata(), so we don't need this.
>> 
>> I do however use dev_get_drvdata() directly in PM ops.
>> 
>
> OK, so dev_set_drvdata() would make it symmetric.
>
>
>>>
>>> I think we could simplify this and avoid needing to use pm runtime (and use
>>> even less power!). During probe, put the chip in power down mode. When doing
>>> direct reads of a single value, put the chip in single-shot mode. When doing
>>> starting a buffered read, put it in continuous mode and when the buffered read
>>> is stopped, put it back in shutdown mode.
>> 
>> These chips only have two modes single-shot (low-power) and continuous.
>> Are you suggesting we shut it down using the vdd regulator?
>> 
>> Either way, can't the system go to sleep while in buffer mode? If that's
>> the case we should still need these handlers.
>> 
>
> I hope not. I would suspect that most IIO drivers are broken in this
> regard. I've never attempted to try to implement suspend/resume in an
> IIO driver yet because I didn't have an application that required it
> and it would be very difficult to get right without very extensive
> testing.

Then I'll drop it.

Thanks! I will submit v2 soon :)


-- 
 ~ Kurt

Re: [PATCH 2/2] iio: adc: Add ti-ads1x18 driver

[kernel test robot]

Hi Kurt,

kernel test robot noticed the following build warnings:

[auto build test WARNING on f9e05791642810a0cf6237d39fafd6fec5e0b4bb]

url:    https://github.com/intel-lab-lkp/linux/commits/Kurt-Borja/dt-bindings-iio-adc-Add-TI-ADS1018-ADS1118/20251122-012031
base:   f9e05791642810a0cf6237d39fafd6fec5e0b4bb
patch link:    https://lore.kernel.org/r/20251121-ads1x18-v1-2-86db080fc9a4%40gmail.com
patch subject: [PATCH 2/2] iio: adc: Add ti-ads1x18 driver
config: openrisc-randconfig-r131-20251122 (https://download.01.org/0day-ci/archive/20251122/202511221834.DmWdWn3a-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251122/202511221834.DmWdWn3a-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202511221834.DmWdWn3a-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/iio/adc/ti-ads1x18.c:237:16: sparse: sparse: cast to restricted __be16
>> drivers/iio/adc/ti-ads1x18.c:244:28: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned short @@     got restricted __be16 [usertype] @@
   drivers/iio/adc/ti-ads1x18.c:244:28: sparse:     expected unsigned short
   drivers/iio/adc/ti-ads1x18.c:244:28: sparse:     got restricted __be16 [usertype]
   drivers/iio/adc/ti-ads1x18.c:788:15: sparse: sparse: cast to restricted __be16
   drivers/iio/adc/ti-ads1x18.c:813:15: sparse: sparse: cast to restricted __be16

vim +237 drivers/iio/adc/ti-ads1x18.c

   226	
   227	static int __ads1x18_read_conver(struct ads1x18 *ads1x18, u16 *cnv)
   228	{
   229		int ret;
   230	
   231		ads1x18->tx_buf[0] = 0;
   232		ads1x18->tx_buf[1] = 0;
   233		ret = spi_sync_locked(ads1x18->spi, &ads1x18->message);
   234		if (ret)
   235			return ret;
   236	
 > 237		*cnv = be16_to_cpu(ads1x18->rx_buf[0]);
   238	
   239		return 0;
   240	}
   241	
   242	static int __ads1x18_write_config(struct ads1x18 *ads1x18, u16 cfg)
   243	{
 > 244		ads1x18->tx_buf[0] = cpu_to_be16(cfg);
   245		ads1x18->tx_buf[1] = 0;
   246	
   247		return spi_sync_locked(ads1x18->spi, &ads1x18->message);
   248	}
   249	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

Re: [PATCH 0/2] iio: Add support for TI ADS1X18 ADCs

[David Lechner]

On 11/21/25 11:16 AM, Kurt Borja wrote:
> Hi,
> 
> This series adds a new driver for TI ADS1X18 SPI devices.
> 
> This is my first time contributing to the IIO subsystem and making
> dt-bindings documentation, so (don't) go easy on me :p.

I actually had these parts on my radar, so happy to help you out.
Unfortunately, I don't have the hardware for testing though.

The first thing I was going to do was check the existing drivers
to make sure that there isn't one already that has a compatible
register layout. I have a feeling we won't find one, but would be
good to mention that in the cover to justify adding a new driver.

There are a couple of similar TI ADCs on the mailing list right
now, but they are IMHO just slightly too different to share a
driver, but would be good to look at just to make things are
consistent on a high level.

> 
> As explained in Patch 2 changelog, the DRDY interrupt line is shared
> with the MOSI pin. This awkward quirk is also found on some Analog
> Devices sigma-delta SPI ADCs, so the interrupt and trigger design is
> inspired by those.

Yup, that seems to be the best way we know how to handle this.

Re: [PATCH 0/2] iio: Add support for TI ADS1X18 ADCs

[Kurt Borja]

Hi David,

On Fri Nov 21, 2025 at 5:32 PM -05, David Lechner wrote:
> On 11/21/25 11:16 AM, Kurt Borja wrote:
>> Hi,
>> 
>> This series adds a new driver for TI ADS1X18 SPI devices.
>> 
>> This is my first time contributing to the IIO subsystem and making
>> dt-bindings documentation, so (don't) go easy on me :p.
>
> I actually had these parts on my radar, so happy to help you out.
> Unfortunately, I don't have the hardware for testing though.
>
> The first thing I was going to do was check the existing drivers
> to make sure that there isn't one already that has a compatible
> register layout. I have a feeling we won't find one, but would be
> good to mention that in the cover to justify adding a new driver.

The closest driver I could find was the ti-ads1015 I2C driver. It has
the same register map and similar specs. Although I think we can adapt
it to be "compatible", I chose to do a different driver for a few
reasons:

  - ads1015 and compatible devices have a separate DRDY interrupt line.

  - The ti-ads1015 driver doesn't support the DRDY interrupt (sleeps
    until data is ready and it doesn't have an iio_trigger).

  - To correctly handle the DOUT/DRDY line we need to manually control
    the spi_bus_lock. And we do it differently based on which IIO device
    mode we are operating on, so it would be difficult to stuff this
    logic into regmap_bus callbacks alone.

  - IMO the end result of merging these drivers would be too messy.

This is just my opinion though, so let me know what you think. If do
agree I will add some of this points in the patch changelog!

>
> There are a couple of similar TI ADCs on the mailing list right
> now, but they are IMHO just slightly too different to share a
> driver, but would be good to look at just to make things are
> consistent on a high level.

Yes, the other two TI ADCs, ADS1120 and ADS131M02 are very different
devices.

>
>> 
>> As explained in Patch 2 changelog, the DRDY interrupt line is shared
>> with the MOSI pin. This awkward quirk is also found on some Analog
>> Devices sigma-delta SPI ADCs, so the interrupt and trigger design is
>> inspired by those.
>
> Yup, that seems to be the best way we know how to handle this.


-- 
 ~ Kurt

Re: [PATCH 0/2] iio: Add support for TI ADS1X18 ADCs

[David Lechner]

On 11/21/25 5:28 PM, Kurt Borja wrote:
> Hi David,
> 
> On Fri Nov 21, 2025 at 5:32 PM -05, David Lechner wrote:
>> On 11/21/25 11:16 AM, Kurt Borja wrote:
>>> Hi,
>>>
>>> This series adds a new driver for TI ADS1X18 SPI devices.
>>>
>>> This is my first time contributing to the IIO subsystem and making
>>> dt-bindings documentation, so (don't) go easy on me :p.
>>
>> I actually had these parts on my radar, so happy to help you out.
>> Unfortunately, I don't have the hardware for testing though.
>>
>> The first thing I was going to do was check the existing drivers
>> to make sure that there isn't one already that has a compatible
>> register layout. I have a feeling we won't find one, but would be
>> good to mention that in the cover to justify adding a new driver.
> 
> The closest driver I could find was the ti-ads1015 I2C driver. It has
> the same register map and similar specs. Although I think we can adapt
> it to be "compatible", I chose to do a different driver for a few
> reasons:
> 
>   - ads1015 and compatible devices have a separate DRDY interrupt line.
> 
>   - The ti-ads1015 driver doesn't support the DRDY interrupt (sleeps
>     until data is ready and it doesn't have an iio_trigger).

I don't think this one is a big deal. Ideally, eventually both drivers
would support operating both with and without interrupts.

> 
>   - To correctly handle the DOUT/DRDY line we need to manually control
>     the spi_bus_lock. And we do it differently based on which IIO device
>     mode we are operating on, so it would be difficult to stuff this
>     logic into regmap_bus callbacks alone.
> 
>   - IMO the end result of merging these drivers would be too messy.

This one I agree with 100%, but for different reasons. ads1015 is I2C
and ads1018 is SPI _and_ regmap is not a good fit for either of these.
Mostly because when reading sample data, we need a custom SPI message
to read the data and write the setup for the next conversion at the
same time. And ads1018 only has 1 register anyway that isn't 100%
identical to the same register in ads1015.

> 
> This is just my opinion though, so let me know what you think. If do
> agree I will add some of this points in the patch changelog!
> 
In the end, we both have the same conclusion.