Skip to contentSkip to conversation

hwmon: (iio_hwmon) optionally force iio channel type

RFC PATCH In review Liam Beguin 3 participants 11 messages May 16, 2021

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

cover hwmon: (iio_hwmon) optionally force iio channel type

Add a devicetree binding to optionally force a different IIO channel type.

This is useful in cases where ADC channels are connected to a circuit that represent another unit such as a temperature or a current.

channel-types was chosen instead of io-channel-types as this is not part of the iio consumer bindings.

In the current form, this patch does what it's intended to do:
change the unit displayed by sensors, but feels like the wrong way to address the problem.

Would it be possible to force the type of different IIO channels for this kind of use case with a devicetree binding from the IIO subsystem?

It would be convenient to do it within the IIO subsystem to have the right unit there too.

Thanks for your time,
Liam

Liam Beguin (2):
hwmon: (iio_hwmon) optionally force iio channel type
dt-bindings: hwmon: add iio-hwmon bindings

 .../devicetree/bindings/hwmon/iio-hwmon.yaml  | 41 +++++++++++++++++++
 drivers/hwmon/iio_hwmon.c                     |  2 +
 2 files changed, 43 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/hwmon/iio-hwmon.yaml

base-commit: 9f4ad9e425a1d3b6a34617b8ea226d56a119a717

Signature · 1 line
2.30.1.489.g328c10930387
#1 lore raw

RFC PATCH 1/2 hwmon: (iio_hwmon) optionally force iio channel type

Add a devicetree binding to optionally force a different IIO channel type.

This is useful in cases where ADC channels are connected to a circuit that represent another unit such as a temperature or a current.

channel-types was chosen instead of io-channel-types as this is not part of the iio consumer bindings.

---
 drivers/hwmon/iio_hwmon.c | 2 ++
 1 file changed, 2 insertions(+)
drivers/hwmon/iio_hwmon.c +2 -0
index 580a7d125b88..365ea2359b22 100644
@@ -109,6 +109,8 @@ static int iio_hwmon_probe(struct platform_device *pdev)
 		if (ret < 0)
 			return ret;
 
+		of_property_read_u32_index(dev->of_node, "channel-types",
+					   i, &type);
 		switch (type) {
 		case IIO_VOLTAGE:
 			n = in_i++;
Signature · 1 line
2.30.1.489.g328c10930387
#2 lore raw

RFC PATCH 2/2 dt-bindings: hwmon: add iio-hwmon bindings

In reply to Liam Beguin

Document devicetree bindings for the iio-hwmon driver. Also add documentation for the channel-types option.

---
 .../devicetree/bindings/hwmon/iio-hwmon.yaml  | 41 +++++++++++++++++++
 1 file changed, 41 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/hwmon/iio-hwmon.yaml
Documentation/devicetree/bindings/hwmon/iio-hwmon.yaml new file +41 -0
new file mode 100644
index 000000000000..fb8b437112a5
@@ -0,0 +1,41 @@
+# SPDX-License-Identifier: GPL-2.0-only
+%YAML 1.2
+---
+
+$id: http://devicetree.org/schemas/hwmon/iio-hwmon.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: bindings for the IIO hwmon bridge
+
+maintainers:
+  - Jean Delvare <[email protected]>
+  - Guenter Roeck <[email protected]>
+
+properties:
+  compatible:
+    enum:
+      - iio-hwmon
+
+  io-channels:
+    $ref: /schemas/types.yaml#/definitions/phandle-array
+
+  io-channel-names:
+    $ref: /schemas/types.yaml#/definitions/string-array
+
+  channel-types:
+    $ref: /schemas/types.yaml#/definitions/uint32-array
+    description: |
+      an array of channel types used to override the IIO type of each channel.
+
+additionalProperties: false
+
+examples:
+  - |
+    #define IIO_VOLTAGE 0
+    #define IIO_CURRENT 1
+    iio_hwmon_adc0 {
+        compatible = "iio-hwmon";
+        io-channels = <&adc 0>, <&adc 1>;
+        io-channel-names = "input_current", "input_voltage" ;
+        channel-types = <IIO_CURRENT>, <IIO_VOLTAGE>;
+    };
Signature · 1 line
2.30.1.489.g328c10930387
maintainer
#3 lore raw
In reply to Liam Beguin
Quoted 9 lines · Liam Beguin

Add a devicetree binding to optionally force a different IIO channel type.

This is useful in cases where ADC channels are connected to a circuit that represent another unit such as a temperature or a current.

channel-types was chosen instead of io-channel-types as this is not part of the iio consumer bindings.

Quoted 7 lines

In the current form, this patch does what it's intended to do:
change the unit displayed by sensors, but feels like the wrong way to address the problem.

Would it be possible to force the type of different IIO channels for this kind of use case with a devicetree binding from the IIO subsystem?

That doesn't make sense to me. If an ADC is used to report temperatures, it would be a thermistor, and the ntc_thermistor driver should be used. Not sure what to do with currents, but overriding "voltage" with "current" seems wrong.

Guenter

Quoted 18 lines

It would be convenient to do it within the IIO subsystem to have the right unit there too.

Thanks for your time,
Liam

Liam Beguin (2):
hwmon: (iio_hwmon) optionally force iio channel type
dt-bindings: hwmon: add iio-hwmon bindings

  .../devicetree/bindings/hwmon/iio-hwmon.yaml  | 41 +++++++++++++++++++
  drivers/hwmon/iio_hwmon.c                     |  2 +
  2 files changed, 43 insertions(+)

create mode 100644 Documentation/devicetree/bindings/hwmon/iio-hwmon.yaml

base-commit: 9f4ad9e425a1d3b6a34617b8ea226d56a119a717

#4 lore raw

Hi Guenter,

Quoted 18 lines · Guenter Roeck
Quoted 9 lines · Liam Beguin

Add a devicetree binding to optionally force a different IIO channel type.

This is useful in cases where ADC channels are connected to a circuit that represent another unit such as a temperature or a current.

channel-types was chosen instead of io-channel-types as this is not part of the iio consumer bindings.

Quoted 7 lines

In the current form, this patch does what it's intended to do:
change the unit displayed by sensors, but feels like the wrong way to address the problem.

Would it be possible to force the type of different IIO channels for this kind of use case with a devicetree binding from the IIO subsystem?

Quoted 5 lines

That doesn't make sense to me. If an ADC is used to report temperatures, it would be a thermistor, and the ntc_thermistor driver should be used. Not sure what to do with currents, but overriding "voltage" with "current"
seems wrong.

Thanks for pointing out the ntc_thermistor.
It makes sense that the ADC channel would become a thermistor. I'll have a look and see if it fits my use case.

Liam

Quoted 21 lines

Guenter

Quoted 18 lines

It would be convenient to do it within the IIO subsystem to have the right unit there too.

Thanks for your time,
Liam

Liam Beguin (2):
hwmon: (iio_hwmon) optionally force iio channel type
dt-bindings: hwmon: add iio-hwmon bindings

  .../devicetree/bindings/hwmon/iio-hwmon.yaml  | 41 +++++++++++++++++++
  drivers/hwmon/iio_hwmon.c                     |  2 +
  2 files changed, 43 insertions(+)

create mode 100644 Documentation/devicetree/bindings/hwmon/iio-hwmon.yaml

base-commit: 9f4ad9e425a1d3b6a34617b8ea226d56a119a717

maintainer
#5 lore raw
In reply to Liam Beguin
Quoted 13 lines · On Sun, 16 May 2021 00:43:13 -0400 Liam Beguin <[email protected]> wrote:

Add a devicetree binding to optionally force a different IIO channel type.

This is useful in cases where ADC channels are connected to a circuit that represent another unit such as a temperature or a current.

channel-types was chosen instead of io-channel-types as this is not part of the iio consumer bindings.

In the current form, this patch does what it's intended to do:
change the unit displayed by sensors, but feels like the wrong way to address the problem.

Quoted 8 lines

Would it be possible to force the type of different IIO channels for this kind of use case with a devicetree binding from the IIO subsystem?

It would be convenient to do it within the IIO subsystem to have the right unit there too.

Thanks for your time,
Liam

Hi Liam,

+CC Peter for AFE part.

It's an interesting approach, but I would suggest we think about this a different way.

Whenever a channel is being used to measure something 'different' from what it actually measures (e.g. a voltage ADC measuring a current) that reflects their being some analog component involved.
If you look at drivers/iio/afe/iio-rescale.c you can see the approach we currently use to handle this.

Effectively what you add to devicetree is a consumer of the ADC channel which in turn provides services to other devices. For this current case it would be either a current-sense-amplifier or a current-sense-shunt depending on what the analog front end looks like. We have to describe the characteristics of that front end which isn't something that can be done via a simple channel type.

That afe consumer device can then provide services to another consumer (e.g. iio-hwmon) which work for your usecase.

The main limitation of this approach currently is you end up with one device per channel. That could be improved upon if you have a usecase where it matters.

I don't think we currently have an equivalent for temperature sensing but it would be easy enough to do something similar.

Jonathan

Quoted 12 lines

Liam Beguin (2):
hwmon: (iio_hwmon) optionally force iio channel type
dt-bindings: hwmon: add iio-hwmon bindings

 .../devicetree/bindings/hwmon/iio-hwmon.yaml  | 41 +++++++++++++++++++
 drivers/hwmon/iio_hwmon.c                     |  2 +
 2 files changed, 43 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/hwmon/iio-hwmon.yaml

base-commit: 9f4ad9e425a1d3b6a34617b8ea226d56a119a717

#6 lore raw

Hi Jonathan,

Quoted 29 lines · Jonathan Cameron
Quoted 13 lines · On Sun, 16 May 2021 00:43:13 -0400 Liam Beguin <[email protected]> wrote:

Add a devicetree binding to optionally force a different IIO channel type.

This is useful in cases where ADC channels are connected to a circuit that represent another unit such as a temperature or a current.

channel-types was chosen instead of io-channel-types as this is not part of the iio consumer bindings.

In the current form, this patch does what it's intended to do:
change the unit displayed by sensors, but feels like the wrong way to address the problem.

Quoted 8 lines

Would it be possible to force the type of different IIO channels for this kind of use case with a devicetree binding from the IIO subsystem?

It would be convenient to do it within the IIO subsystem to have the right unit there too.

Thanks for your time,
Liam

Hi Liam,

+CC Peter for AFE part.

Quoted 8 lines

It's an interesting approach, but I would suggest we think about this a different way.

Whenever a channel is being used to measure something 'different' from what it actually measures (e.g. a voltage ADC measuring a current) that reflects their being some analog component involved.
If you look at drivers/iio/afe/iio-rescale.c you can see the approach we currently use to handle this.

Many thanks for pointing out the AFE code. That look like what I was hoping to accomplish, but in a much better way.

Quoted 8 lines

Effectively what you add to devicetree is a consumer of the ADC channel which in turn provides services to other devices. For this current case it would be either a current-sense-amplifier or a current-sense-shunt depending on what the analog front end looks like. We have to describe the characteristics of that front end which isn't something that can be done via a simple channel type.

Understood. My original intention was to use sensors.conf to do the conversions and take into accounts those parameters.

Quoted 10 lines

That afe consumer device can then provide services to another consumer (e.g. iio-hwmon) which work for your usecase.

The main limitation of this approach currently is you end up with one device per channel. That could be improved upon if you have a usecase
where it matters.

I don't think we currently have an equivalent for temperature sensing but it would be easy enough to do something similar.

Wonderful, thanks again for pointing out the AFE!

Liam

Quoted 16 lines

Jonathan

Quoted 12 lines

Liam Beguin (2):
hwmon: (iio_hwmon) optionally force iio channel type
dt-bindings: hwmon: add iio-hwmon bindings

 .../devicetree/bindings/hwmon/iio-hwmon.yaml  | 41 +++++++++++++++++++
 drivers/hwmon/iio_hwmon.c                     |  2 +
 2 files changed, 43 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/hwmon/iio-hwmon.yaml

base-commit: 9f4ad9e425a1d3b6a34617b8ea226d56a119a717

maintainer
#7 lore raw
Quoted 64 lines · Liam Beguin

Hi Jonathan,

Quoted 29 lines · Jonathan Cameron
Quoted 13 lines · On Sun, 16 May 2021 00:43:13 -0400 Liam Beguin <[email protected]> wrote:

Add a devicetree binding to optionally force a different IIO channel type.

This is useful in cases where ADC channels are connected to a circuit that represent another unit such as a temperature or a current.

channel-types was chosen instead of io-channel-types as this is not part of the iio consumer bindings.

In the current form, this patch does what it's intended to do:
change the unit displayed by sensors, but feels like the wrong way to address the problem.

Quoted 8 lines

Would it be possible to force the type of different IIO channels for this kind of use case with a devicetree binding from the IIO subsystem?

It would be convenient to do it within the IIO subsystem to have the right unit there too.

Thanks for your time,
Liam

Hi Liam,

+CC Peter for AFE part.

Quoted 8 lines

It's an interesting approach, but I would suggest we think about this a different way.

Whenever a channel is being used to measure something 'different' from what it actually measures (e.g. a voltage ADC measuring a current) that reflects their being some analog component involved.
If you look at drivers/iio/afe/iio-rescale.c you can see the approach we currently use to handle this.

Many thanks for pointing out the AFE code. That look like what I was hoping to accomplish, but in a much better way.

Quoted 8 lines

Effectively what you add to devicetree is a consumer of the ADC channel which in turn provides services to other devices. For this current case it would be either a current-sense-amplifier or a current-sense-shunt depending on what the analog front end looks like. We have to describe the characteristics of that front end which isn't something that can be done via a simple channel type.

Understood. My original intention was to use sensors.conf to do the conversions and take into accounts those parameters.

Quoted 8 lines

That afe consumer device can then provide services to another consumer (e.g. iio-hwmon) which work for your usecase.

The main limitation of this approach currently is you end up with one device per channel. That could be improved upon if you have a usecase
where it matters.

Quoted 5 lines
Quoted 2 lines

I don't think we currently have an equivalent for temperature sensing but it would be easy enough to do something similar.

Wonderful, thanks again for pointing out the AFE!

Please don't reinvent the ntc_thermistor driver.

Thanks,
Guenter

Quoted 19 lines

Liam

Quoted 16 lines

Jonathan

Quoted 12 lines

Liam Beguin (2):
hwmon: (iio_hwmon) optionally force iio channel type
dt-bindings: hwmon: add iio-hwmon bindings

  .../devicetree/bindings/hwmon/iio-hwmon.yaml  | 41 +++++++++++++++++++
  drivers/hwmon/iio_hwmon.c                     |  2 +
  2 files changed, 43 insertions(+)

create mode 100644 Documentation/devicetree/bindings/hwmon/iio-hwmon.yaml

base-commit: 9f4ad9e425a1d3b6a34617b8ea226d56a119a717

maintainer
#8 lore raw
Quoted 65 lines · On Sun, 16 May 2021 08:54:06 -0700 Guenter Roeck <[email protected]> wrote:
Quoted 64 lines · Liam Beguin

Hi Jonathan,

Quoted 29 lines · Jonathan Cameron
Quoted 13 lines · On Sun, 16 May 2021 00:43:13 -0400 Liam Beguin <[email protected]> wrote:

Add a devicetree binding to optionally force a different IIO channel type.

This is useful in cases where ADC channels are connected to a circuit that represent another unit such as a temperature or a current.

channel-types was chosen instead of io-channel-types as this is not part of the iio consumer bindings.

In the current form, this patch does what it's intended to do:
change the unit displayed by sensors, but feels like the wrong way to address the problem.

Quoted 8 lines

Would it be possible to force the type of different IIO channels for this kind of use case with a devicetree binding from the IIO subsystem?

It would be convenient to do it within the IIO subsystem to have the right unit there too.

Thanks for your time,
Liam

Hi Liam,

+CC Peter for AFE part.

Quoted 8 lines

It's an interesting approach, but I would suggest we think about this a different way.

Whenever a channel is being used to measure something 'different' from what it actually measures (e.g. a voltage ADC measuring a current) that reflects their being some analog component involved.
If you look at drivers/iio/afe/iio-rescale.c you can see the approach we currently use to handle this.

Many thanks for pointing out the AFE code. That look like what I was hoping to accomplish, but in a much better way.

Quoted 8 lines

Effectively what you add to devicetree is a consumer of the ADC channel which in turn provides services to other devices. For this current case it would be either a current-sense-amplifier or a current-sense-shunt depending on what the analog front end looks like. We have to describe the characteristics of that front end which isn't something that can be done via a simple channel type.

Understood. My original intention was to use sensors.conf to do the conversions and take into accounts those parameters.

Quoted 8 lines

That afe consumer device can then provide services to another consumer (e.g. iio-hwmon) which work for your usecase.

The main limitation of this approach currently is you end up with one device per channel. That could be improved upon if you have a usecase
where it matters.

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

I don't think we currently have an equivalent for temperature sensing but it would be easy enough to do something similar.

Wonderful, thanks again for pointing out the AFE!

Please don't reinvent the ntc_thermistor driver.

Agreed, I'd forgotten it existed :( Had a feeling we'd solved that problem before but couldn't remember the name of the driver.

The afe driver already deals with current / voltage scaling and conversion for common analog circuits. Potential dividers, current shunts etc, but they are all the linear cases IIRC.

ntc_thermistor deals with the much more complex job of dealing with a thermistor.

Thanks,

Jonathan

Quoted 24 lines

Thanks,
Guenter

Quoted 19 lines

Liam

Quoted 16 lines

Jonathan

Quoted 12 lines

Liam Beguin (2):
hwmon: (iio_hwmon) optionally force iio channel type
dt-bindings: hwmon: add iio-hwmon bindings

  .../devicetree/bindings/hwmon/iio-hwmon.yaml  | 41 +++++++++++++++++++
  drivers/hwmon/iio_hwmon.c                     |  2 +
  2 files changed, 43 insertions(+)

create mode 100644 Documentation/devicetree/bindings/hwmon/iio-hwmon.yaml

base-commit: 9f4ad9e425a1d3b6a34617b8ea226d56a119a717

#9 lore raw
Quoted 80 lines · Jonathan Cameron
Quoted 65 lines · On Sun, 16 May 2021 08:54:06 -0700 Guenter Roeck <[email protected]> wrote:
Quoted 64 lines · Liam Beguin

Hi Jonathan,

Quoted 29 lines · Jonathan Cameron
Quoted 13 lines · On Sun, 16 May 2021 00:43:13 -0400 Liam Beguin <[email protected]> wrote:

Add a devicetree binding to optionally force a different IIO channel type.

This is useful in cases where ADC channels are connected to a circuit that represent another unit such as a temperature or a current.

channel-types was chosen instead of io-channel-types as this is not part of the iio consumer bindings.

In the current form, this patch does what it's intended to do:
change the unit displayed by sensors, but feels like the wrong way to address the problem.

Quoted 8 lines

Would it be possible to force the type of different IIO channels for this kind of use case with a devicetree binding from the IIO subsystem?

It would be convenient to do it within the IIO subsystem to have the right unit there too.

Thanks for your time,
Liam

Hi Liam,

+CC Peter for AFE part.

Quoted 8 lines

It's an interesting approach, but I would suggest we think about this a different way.

Whenever a channel is being used to measure something 'different' from what it actually measures (e.g. a voltage ADC measuring a current) that reflects their being some analog component involved.
If you look at drivers/iio/afe/iio-rescale.c you can see the approach we currently use to handle this.

Many thanks for pointing out the AFE code. That look like what I was hoping to accomplish, but in a much better way.

Quoted 8 lines

Effectively what you add to devicetree is a consumer of the ADC channel which in turn provides services to other devices. For this current case it would be either a current-sense-amplifier or a current-sense-shunt depending on what the analog front end looks like. We have to describe the characteristics of that front end which isn't something that can be done via a simple channel type.

Understood. My original intention was to use sensors.conf to do the conversions and take into accounts those parameters.

Quoted 8 lines

That afe consumer device can then provide services to another consumer (e.g. iio-hwmon) which work for your usecase.

The main limitation of this approach currently is you end up with one device per channel. That could be improved upon if you have a usecase
where it matters.

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

I don't think we currently have an equivalent for temperature sensing but it would be easy enough to do something similar.

Wonderful, thanks again for pointing out the AFE!

Please don't reinvent the ntc_thermistor driver.

Agreed, I'd forgotten it existed :( Had a feeling we'd solved that problem before
but couldn't remember the name of the driver.

Quoted 8 lines

The afe driver already deals with current / voltage scaling and conversion
for common analog circuits. Potential dividers, current shunts etc, but they
are all the linear cases IIRC.

ntc_thermistor deals with the much more complex job of dealing with a thermistor.

I agree, no need to reinvent this.

Like Jonathan said, the ntc_thermistor driver seems to handle much more complex cases. Where would be the best place to add support for PT100 and PT1000? iio-rescale?

Thanks,
Liam

Quoted 29 lines

Thanks,

Jonathan

Quoted 24 lines

Thanks,
Guenter

Quoted 19 lines

Liam

Quoted 16 lines

Jonathan

Quoted 12 lines

Liam Beguin (2):
hwmon: (iio_hwmon) optionally force iio channel type
dt-bindings: hwmon: add iio-hwmon bindings

  .../devicetree/bindings/hwmon/iio-hwmon.yaml  | 41 +++++++++++++++++++
  drivers/hwmon/iio_hwmon.c                     |  2 +
  2 files changed, 43 insertions(+)

create mode 100644 Documentation/devicetree/bindings/hwmon/iio-hwmon.yaml

base-commit: 9f4ad9e425a1d3b6a34617b8ea226d56a119a717

maintainer
#10 lore raw
Quoted 87 lines · Liam Beguin
Quoted 86 lines · Jonathan Cameron
Quoted 65 lines · On Sun, 16 May 2021 08:54:06 -0700 Guenter Roeck <[email protected]> wrote:
Quoted 64 lines · Liam Beguin

Hi Jonathan,

Quoted 29 lines · Jonathan Cameron
Quoted 13 lines · On Sun, 16 May 2021 00:43:13 -0400 Liam Beguin <[email protected]> wrote:

Add a devicetree binding to optionally force a different IIO channel type.

This is useful in cases where ADC channels are connected to a circuit that represent another unit such as a temperature or a current.

channel-types was chosen instead of io-channel-types as this is not part of the iio consumer bindings.

In the current form, this patch does what it's intended to do:
change the unit displayed by sensors, but feels like the wrong way to address the problem.

Quoted 8 lines

Would it be possible to force the type of different IIO channels for this kind of use case with a devicetree binding from the IIO subsystem?

It would be convenient to do it within the IIO subsystem to have the right unit there too.

Thanks for your time,
Liam

Hi Liam,

+CC Peter for AFE part.

Quoted 8 lines

It's an interesting approach, but I would suggest we think about this a different way.

Whenever a channel is being used to measure something 'different' from what it actually measures (e.g. a voltage ADC measuring a current) that reflects their being some analog component involved.
If you look at drivers/iio/afe/iio-rescale.c you can see the approach we currently use to handle this.

Many thanks for pointing out the AFE code. That look like what I was hoping to accomplish, but in a much better way.

Quoted 8 lines

Effectively what you add to devicetree is a consumer of the ADC channel which in turn provides services to other devices. For this current case it would be either a current-sense-amplifier or a current-sense-shunt depending on what the analog front end looks like. We have to describe the characteristics of that front end which isn't something that can be done via a simple channel type.

Understood. My original intention was to use sensors.conf to do the conversions and take into accounts those parameters.

Quoted 8 lines

That afe consumer device can then provide services to another consumer (e.g. iio-hwmon) which work for your usecase.

The main limitation of this approach currently is you end up with one device per channel. That could be improved upon if you have a usecase
where it matters.

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

I don't think we currently have an equivalent for temperature sensing but it would be easy enough to do something similar.

Wonderful, thanks again for pointing out the AFE!

Please don't reinvent the ntc_thermistor driver.

Agreed, I'd forgotten it existed :( Had a feeling we'd solved that problem before
but couldn't remember the name of the driver.

The afe driver already deals with current / voltage scaling and conversion
for common analog circuits. Potential dividers, current shunts etc, but they
are all the linear cases IIRC.

Quoted 9 lines
Quoted 2 lines

ntc_thermistor deals with the much more complex job of dealing with a thermistor.

I agree, no need to reinvent this.

Like Jonathan said, the ntc_thermistor driver seems to handle much more complex cases. Where would be the best place to add support for PT100 and PT1000? iio-rescale?

Those sensors don't seem to be even useful for hardware monitoring, so if they are linear (and it looks like that that the case) iio would be a better place.

Guenter