All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "Breana, Tiberiu A" <tiberiu.a.breana@intel.com>,
	LM Sensors <lm-sensors@lm-sensors.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"Baluta, Daniel" <daniel.baluta@intel.com>
Subject: Re: [PATCH 0/2] Add support for MAX31722/MAX31723 temperature sensors
Date: Tue, 15 Mar 2016 06:34:25 -0700	[thread overview]
Message-ID: <56E80F61.4000304@roeck-us.net> (raw)
In-Reply-To: <4586F61A4A291F4DA44D32824E7C0F4023568DEC@IRSMSX109.ger.corp.intel.com>

On 03/15/2016 05:58 AM, Breana, Tiberiu A wrote:
> Hello Guenter, hwmon,
>
> We have a dilemma as to wether this device driver belongs in IIO or hwmon:
> https://datasheets.maximintegrated.com/en/ds/MAX31722-MAX31723.pdf
>
> Could you please give us your opinion on this?

The chip has limit registers and an alarm signal output, suggesting that
its intended use is for hardware monitoring purposes.

The conversion time is between 50ms and 200ms, which suggests that the
faster ABI provided by iio isn't really beneficial.

Given all that, I think that hwmon would be a better place.

If you want to keep the driver in iio, I would suggest to consider enhancing
the iio-hwmon bridge with threshold/limit support if that is possible.
This would ensure that the chip can be used for its intended purpose.

Thanks,
Guenter

> Thanks,
>
> Tiberiu
>
>> -----Original Message-----
>> From: linux-iio-owner@vger.kernel.org [mailto:linux-iio-
>> owner@vger.kernel.org] On Behalf Of Jonathan Cameron
>> Sent: Wednesday, March 9, 2016 10:32 PM
>> To: Breana, Tiberiu A <tiberiu.a.breana@intel.com>; linux-
>> iio@vger.kernel.org
>> Subject: Re: [PATCH 0/2] Add support for MAX31722/MAX31723
>> temperature sensors
>>
>> On 09/03/16 13:30, Tiberiu Breana wrote:
>>> This patch set adds support for the MAX31722/MAX31723 temperature
>>> sensors / thermostats.
>>> Patch 1 adds basic support and power management.
>>> Patch 2 adds threshold interrupt support.
>>>
>>> Tiberiu Breana (2):
>>>    iio: temperature: Add support for MAX31722/MAX31723 temperature
>>>      sensors
>>>    iio: temperature: Add threshold interrupt support for max31722
>>>
>>>   drivers/iio/temperature/Kconfig    |  12 +
>>>   drivers/iio/temperature/Makefile   |   1 +
>>>   drivers/iio/temperature/max31722.c | 673
>>> +++++++++++++++++++++++++++++++++++++
>>>   3 files changed, 686 insertions(+)
>>>   create mode 100644 drivers/iio/temperature/max31722.c
>>>
>> Hi Tiberiu,
>>
>> When proposing a temperature sensor driver, we need some additional
>> justification for why it is suited for IIO rather than the more focused (and in
>> someways simpler) hwmon.
>>
>> So far we have had thermophiles that don't fit in as devices typically used for
>> hardware monitoring. Also in there are a few drivers which are for parts
>> where they are a cut down version of a more complex sensor (the
>> measurement specialties parts are either pressure sensors or humidty
>> sensors at least in terms of what they share interfaces with)
>>
>> Also, please cc the hwmon maintainers (and probably list) as we want their
>> agreement.
>>
>> Jonathan
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body
>> of a message to majordomo@vger.kernel.org More majordomo info at
>> http://vger.kernel.org/majordomo-info.html
>


WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: "Breana, Tiberiu A" <tiberiu.a.breana@intel.com>,
	LM Sensors <lm-sensors@lm-sensors.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"Baluta, Daniel" <daniel.baluta@intel.com>
Subject: Re: [lm-sensors] [PATCH 0/2] Add support for MAX31722/MAX31723 temperature sensors
Date: Tue, 15 Mar 2016 13:34:25 +0000	[thread overview]
Message-ID: <56E80F61.4000304@roeck-us.net> (raw)
In-Reply-To: <4586F61A4A291F4DA44D32824E7C0F4023568DEC@IRSMSX109.ger.corp.intel.com>

On 03/15/2016 05:58 AM, Breana, Tiberiu A wrote:
> Hello Guenter, hwmon,
>
> We have a dilemma as to wether this device driver belongs in IIO or hwmon:
> https://datasheets.maximintegrated.com/en/ds/MAX31722-MAX31723.pdf
>
> Could you please give us your opinion on this?

The chip has limit registers and an alarm signal output, suggesting that
its intended use is for hardware monitoring purposes.

The conversion time is between 50ms and 200ms, which suggests that the
faster ABI provided by iio isn't really beneficial.

Given all that, I think that hwmon would be a better place.

If you want to keep the driver in iio, I would suggest to consider enhancing
the iio-hwmon bridge with threshold/limit support if that is possible.
This would ensure that the chip can be used for its intended purpose.

Thanks,
Guenter

> Thanks,
>
> Tiberiu
>
>> -----Original Message-----
>> From: linux-iio-owner@vger.kernel.org [mailto:linux-iio-
>> owner@vger.kernel.org] On Behalf Of Jonathan Cameron
>> Sent: Wednesday, March 9, 2016 10:32 PM
>> To: Breana, Tiberiu A <tiberiu.a.breana@intel.com>; linux-
>> iio@vger.kernel.org
>> Subject: Re: [PATCH 0/2] Add support for MAX31722/MAX31723
>> temperature sensors
>>
>> On 09/03/16 13:30, Tiberiu Breana wrote:
>>> This patch set adds support for the MAX31722/MAX31723 temperature
>>> sensors / thermostats.
>>> Patch 1 adds basic support and power management.
>>> Patch 2 adds threshold interrupt support.
>>>
>>> Tiberiu Breana (2):
>>>    iio: temperature: Add support for MAX31722/MAX31723 temperature
>>>      sensors
>>>    iio: temperature: Add threshold interrupt support for max31722
>>>
>>>   drivers/iio/temperature/Kconfig    |  12 +
>>>   drivers/iio/temperature/Makefile   |   1 +
>>>   drivers/iio/temperature/max31722.c | 673
>>> +++++++++++++++++++++++++++++++++++++
>>>   3 files changed, 686 insertions(+)
>>>   create mode 100644 drivers/iio/temperature/max31722.c
>>>
>> Hi Tiberiu,
>>
>> When proposing a temperature sensor driver, we need some additional
>> justification for why it is suited for IIO rather than the more focused (and in
>> someways simpler) hwmon.
>>
>> So far we have had thermophiles that don't fit in as devices typically used for
>> hardware monitoring. Also in there are a few drivers which are for parts
>> where they are a cut down version of a more complex sensor (the
>> measurement specialties parts are either pressure sensors or humidty
>> sensors at least in terms of what they share interfaces with)
>>
>> Also, please cc the hwmon maintainers (and probably list) as we want their
>> agreement.
>>
>> Jonathan
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body
>> of a message to majordomo@vger.kernel.org More majordomo info at
>> http://vger.kernel.org/majordomo-info.html
>


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2016-03-15 13:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 13:30 [PATCH 0/2] Add support for MAX31722/MAX31723 temperature sensors Tiberiu Breana
2016-03-09 13:30 ` [PATCH 1/2] iio: temperature: " Tiberiu Breana
2016-03-12  9:57   ` Jonathan Cameron
2016-03-14 13:45     ` Breana, Tiberiu A
2016-03-14 17:31       ` Jonathan Cameron
2016-03-09 13:30 ` [PATCH 2/2] iio: temperature: Add threshold interrupt support for max31722 Tiberiu Breana
2016-03-12 10:17   ` Jonathan Cameron
2016-03-14 12:25     ` Daniel Baluta
2016-03-14 15:06       ` Breana, Tiberiu A
2016-03-09 20:31 ` [PATCH 0/2] Add support for MAX31722/MAX31723 temperature sensors Jonathan Cameron
2016-03-15 12:58   ` Breana, Tiberiu A
2016-03-15 13:16     ` Breana, Tiberiu A
2016-03-15 13:16       ` [lm-sensors] " Breana, Tiberiu A
2016-03-22 11:41       ` Tiberiu Breana
2016-03-15 13:34     ` Guenter Roeck [this message]
2016-03-15 13:34       ` Guenter Roeck
2016-03-15 17:28       ` Jonathan Cameron
2016-03-15 17:28         ` [lm-sensors] " Jonathan Cameron
2016-03-15 18:30         ` Guenter Roeck
2016-03-15 18:30           ` [lm-sensors] " Guenter Roeck
2016-03-16 15:16           ` Breana, Tiberiu A
2016-03-16 15:16             ` [lm-sensors] " Breana, Tiberiu A

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56E80F61.4000304@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=daniel.baluta@intel.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=tiberiu.a.breana@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.