RFC hwmon: (iio_hwmon) optionally force iio channel type
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 8 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | hwmon: (iio_hwmon) optionally force iio channel typedrivers/ | +2 | 0 replies | |
| 2/2 | dt-bindings: hwmon: add iio-hwmon bindingsDocumentation/ | +41 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH v1 0/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.
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