[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210516044315.116290-1-liambeguin@gmail.com>
Date: Sun, 16 May 2021 00:43:13 -0400
From: Liam Beguin <liambeguin@...il.com>
To: liambeguin@...il.com, jdelvare@...e.com, linux@...ck-us.net,
jic23@...nel.org, lars@...afoo.de, pmeerw@...erw.net
Cc: linux-hwmon@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-iio@...r.kernel.org, devicetree@...r.kernel.org,
robh+dt@...nel.org
Subject: [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
--
2.30.1.489.g328c10930387
Powered by blists - more mailing lists