Re: [PATCH 0/3] mxs-lradc: Add support for current sources

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 01.05.2016 20:02, Jonathan Cameron wrote:
On 29/04/16 18:45, Harald Geyer wrote:
My thinking is that there should be a thermistor (or whatever else) driver, that is a consumer of the regulator and a consumer of the IIO_VOLTAGE iio channel and provides a new device with an IIO_RESISTANCE or IIO_TEMP
channel. Maybe there is a simpler solution, that I'm missing?
I agree with that approach - need a way to describe the upstream
hardware - so
will need a thermistor driver

Actually I'm not 100% happy with the above solution myself, because if we start supporting devices that act as an iio-multiplexer (some device that is an iio consumer and provides many new iio channels and can control via gpios which of it child channels is actually routed to the upstream
device) I don't know how to properly manage the regulator device.
Hmm. Are you talking about muxing the regulator as well? That will get complex indeed. Might be possible to cheat and imply the regulators are always connected to all inputs... or do you want to dynamically change the regulator output? That gets messy fast - though in theory might be
possible...

Yes, that's a good summary of what I'm thinking. As there is no
iio-multiplexer yet, this is sort of an academic question. But it's
kind of an obvious thing to want, so we shouldn't be surprised when
somebody actually starts working on that.

Thanks,
Harald
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux