All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Additional PWM driver support for w83792d
Date: Mon, 11 May 2015 13:12:27 +0000	[thread overview]
Message-ID: <5550AABB.2030006@roeck-us.net> (raw)
In-Reply-To: <003901d08a57$bc46f8a0$34d4e9e0$@hiddenengine.co.uk>

On 05/11/2015 03:45 AM, Jean Delvare wrote:
> On Sun, 10 May 2015 09:01:25 -0700, Guenter Roeck wrote:
>> On 05/10/2015 06:42 AM, vt8231@hiddenengine.co.uk wrote:
>> [ ... ]
>>>>>
>>>>> Last note: registers 0xA3-0xA6 have extra configuration bits "Sync
>>>>> T1/2/3". Maybe the driver should handle them but I am not sure how. It
>>>>> could be that the extra outputs should only be exposed to user-space if
>>>>> these bits are 0 (stand alone.) Guenter, any idea/opinion on this?
>>>>
>>>> How about using pwm[4567]_enable ? If I understand correctly, the possible
>>>> modes would be manual or sync(x). In this case we could have 1 (manual),
>>>> 2 (sync with fan1), 3 (sync with fan2), and 4 (sync with fan3), with the
>>>> caveat that the sync settings only make sense if the matching pwmX_enable
>>>> is set to thermal cruise mode.
>>>>
>>>> Does this make sense ?
>
> Not really. The problem is that for now I'm not sure what "sync" really
> refers to. The datasheet mentions temperature channels, and as far as I
> can see each temperature channel is hard-bound to a specific fan
> output. So I suspect that what these configuration bit really mean is
> that the pwm4 output (for example) mirrors the pwm1 output, i.e. pwm4
> has no independent existence. In which case it's better to not expose
> it at all.
>
> If the BIOS specifically configured these bits, there must be a reason
> and that reason would be the way the fans are connected to the chipset.
> Better not change it.
>
> If we really want to expose these bits then abusing pwmX_enable the way
> you suggested is still not correct, pwmX_auto_channels_temp would be
> better suited. But then again I don't think it adds any value if the
> extra PWM outputs only mirror already existing PWM outputs.
>
Ok, fine with me.

Guenter


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

  parent reply	other threads:[~2015-05-11 13:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-09 12:57 [lm-sensors] Additional PWM driver support for w83792d vt8231
2015-05-09 15:30 ` Jean Delvare
2015-05-09 15:55 ` Guenter Roeck
2015-05-09 16:10 ` Guenter Roeck
2015-05-10 16:01 ` Guenter Roeck
2015-05-10 21:44 ` Guenter Roeck
2015-05-11 10:45 ` Jean Delvare
2015-05-11 10:50 ` Jean Delvare
2015-05-11 13:12 ` Guenter Roeck [this message]
2015-05-11 20:15 ` vt8231
2015-05-12 14:19 ` Jean Delvare
2015-05-12 16:21 ` Guenter Roeck
2015-05-14 12:36 ` [lm-sensors] Additional PWM driver support for w83792d - PATCH [1/1] Jean Delvare

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=5550AABB.2030006@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=lm-sensors@vger.kernel.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 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.