Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gianni Vialetto <gianni-1aVadY534Hbk1uMJSBkQmQ@public.gmane.org>
To: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [lm-sensors] hwmon: question about the sysfs interface
Date: Thu, 17 Jul 2014 08:29:29 +0200	[thread overview]
Message-ID: <20140717062929.GA1487@elysium.lan> (raw)
In-Reply-To: <20140714172556.GA3753-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>

Hi Guenter,

> For automatic fan control we don't really have a well defined ABI.
> Part of the problem is that the mechanisms used by various chips are
> quite different.
> 
> Please have a look into Documentation/hwmon/nct6775. It is by far
> the driver with the most comprehensive fan control mechanisms and
> attributes. Would any of the attributes or atribute groups in this
> driver meet your needs ? I could imagine that pwm1_target_temp
> for the upper temperature limit and pwm1_temp_tolerance for the difference
> between upper and lower limit might do. Then there are other attributes
> such as pxm1_start, pwm1_floor, pwm1_step, and pwm1_max which you
> could use to control pwm values further is that is possible with the
> driver.

Using pwm1_target_temp and pwm1_temp_tolerance seems a like nice idea,
yes. Some of the other attributes are already used and I'm not certain
how much I should change at this point.

> An alternative would be to use two sets of pwm_auto_point attributes,
> where the first set specifies the start pwm limit and the second
> specifies the upper temperature and limit. So you would have something
> like
> 
> 	pwm1_auto_point1_pwm	pwm at low temperature
> 	pwm1_auto_point1_temp	low temperature
> 
> 	pwm1_auto_point2_pwm	pwm at high temperature
> 	pwm1_auto_point2_temp	high temperature
> 
> After all, there is no requirement that pwm must exactly match the configured
> value; the above only means that the chip uses those values to calculate
> the necessary fan speed. In addition to that, you could still have some
> of the other attributes as needed, such as pwm1_min, pwm1_max, and so on.

This was my initial plan, roughly, but I like the first solution more at
this point.

> Hope this helps,
> Guenter

Definitely. Thank you.

Regards,
Gianni

  parent reply	other threads:[~2014-07-17  6:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 16:47 hwmon: question about the sysfs interface Gianni Vialetto
2014-07-14 17:25 ` Guenter Roeck
     [not found]   ` <20140714172556.GA3753-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2014-07-17  6:29     ` Gianni Vialetto [this message]
     [not found]       ` <20140717062929.GA1487-kWTPUKa9AM/hXIiyNabO3w@public.gmane.org>
2014-07-17  6:42         ` [lm-sensors] " Guenter Roeck
     [not found]           ` <53C7704E.4060705-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2014-07-17  8:07             ` Martin Peres

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=20140717062929.GA1487@elysium.lan \
    --to=gianni-1avady534hbk1umjsbkqmq@public.gmane.org \
    --cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
    --cc=lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox