On 15 June 2016 05:18:05 BST, Guenter Roeck <linux@xxxxxxxxxxxx> wrote: >On 06/14/2016 12:01 PM, Matt Ranostay wrote: >> Hello Guenter et al, >> >> So seems I wrote an iio driver for the SHT31 chipset about the same >> David Frey had his merged into hwmon tree. So was wondering per >> Jonathan's comments what your input on this would be. >> >>>From what I can see the additional functionality of the hrtimer >> trigger + rather fast update/integration time that a case could be >> made because of the triggered buffer. >> >> Now there is some functionality missing from my iio driver than >exists >> in the hwmon.. like the thermal and humidity trip points (but that >can >> be handled in a userspace HAL anyway), and the non-clock skewing >> read/write functionality (this can be easily added). >> > >I am quite sure that we had this discussion about this very driver >before. >One of the key reasons for going with hwmon was limit register support. > >Guess you claim that is no longer relevant since it can be handled in >user space ? >If so, I would disagree; it seems to be difficult to generate an alert >signal >from user space. Agreed > >I don't mind if you folks want drivers for chips like like this (ie >chips supporting >limits, or in other words typical hardware monitoring chips) in iio, >but I would >kindly ask to enhance the iio subsystem to support limits. It has done since day one via event chardev. Limitations are : * One per channel per type per direction. (Didn't seem necessary at the time) This obviously matters for hwmon chips. * No in kernel interface yet so not pushed on to iio-hwmon bridge. * Intended for interrupt type limits which do not always correspond to how all devices do it... there are ways around it but only indirectly. All fixable and not actually directly relevant for this part (possibly the inkern interface is...) > >It might be worth mentioning that at least for my part am not split on >humidity >sensors. They are supported in high end servers and thus used for >hardware monitoring. Cool. Didn't know that. Jonathan > >Thanks, >Guenter > >> Thanks, >> >> Matt >> >> >> >> On Tue, Jun 14, 2016 at 12:44 AM, <jic23@xxxxxxxxxxxxxxxxxxxxx> >wrote: >>> On 14.06.2016 00:23, Matt Ranostay wrote: >>>> >>>> Didn't notice that will till now, and looking at the timestamp I >see why >>>> :). >>>> However this is more for the sw triggered buffer support which >hwmon >>>> lacks... there is a few examples of this already in the tree. >>>> >>>> Maybe Jonathan and Peter will have some input on this. >>>> >>> Thanks for highlighting this Alison. Not the first time we have had >>> simultaneous driver postings under review for both IIO and >>> HWMON unfortunately. >>> >>> The hwmon guys are fairly flexible iff there is a good reason to >want stuff >>> that is in IIO. The original hwmon humidity driver was actually my >fault >>> as it slipped in when hwmon was effectively not maintained (Andrew >Morton >>> was >>> babysitting). People on their side have always been a bit split on >humidity >>> drivers and whether they are within their scope. >>> >>> Anyhow, best bet is to email their list (perhaps reply to the driver >thread) >>> to make sure everyone knows this is going on (cc linux-iio as well). >>> Then we can work out how to move forward. >>> >>> Two drivers, one in each place is a non starter for new parts. We >have >>> ended up with a few instances, but it's mostly been a case of a >driver >>> with much wider scope ending up covering parts that were already in >hwmon. >>> Also a very small number of devices have moved across from hwmon to >IIO. >>> >>> In this particular case the sensor is reasonably fast so there is at >>> least some argument for IIO support. Note I tend to stay out of >these >>> and let the driver author work on convincing Guenter / Jean >>> (they are very reasonable and responsive!) Only thing I'll say is >that >>> I'm more than happy to have this in IIO if the hwmon guys don't >mind. >>> >>> Jonathan >>> >>>> On Mon, Jun 13, 2016 at 3:25 PM, Alison Schofield ><amsfield22@xxxxxxxxx> >>>> wrote: >>>>> >>>>> On Sat, Jun 11, 2016 at 10:13:15PM -0700, Matt Ranostay wrote: >>>>>> >>>>>> Add support for the humidity and temperature functionally for the >SHT31 >>>>>> chipset. In addition add support for using using software >triggers. >>>>> >>>>> >>>>> Now that I'm hwmon-aware ;) I see this same driver under review >in >>>>> hwmon. >>>>> Can support exist in 2 places? >>>>> >>>>> alisons >>>>> >>>>>> >>>>>> Matt Ranostay (2): >>>>>> devicetree: add Sensirion AG vendor id >>>>>> iio: humidity: sht31: add Sensirion SHT31 support >>>>>> >>>>>> .../devicetree/bindings/i2c/trivial-devices.txt | 1 + >>>>>> .../devicetree/bindings/vendor-prefixes.txt | 1 + >>>>>> drivers/iio/humidity/Kconfig | 11 + >>>>>> drivers/iio/humidity/Makefile | 1 + >>>>>> drivers/iio/humidity/sht31.c | 416 >>>>>> +++++++++++++++++++++ >>>>>> 5 files changed, 430 insertions(+) >>>>>> create mode 100644 drivers/iio/humidity/sht31.c >>>>>> >>>>>> -- >>>>>> 2.7.4 >>>>>> >>>>>> -- >>>>>> To unsubscribe from this list: send the line "unsubscribe >linux-iio" in >>>>>> the body of a message to majordomo@xxxxxxxxxxxxxxx >>>>>> More majordomo info at >http://vger.kernel.org/majordomo-info.html >> -- >> To unsubscribe from this list: send the line "unsubscribe >linux-hwmon" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
