From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Need some guidance on adhering to the sysfs
Date: Sun, 22 Apr 2007 15:29:04 +0000 [thread overview]
Message-ID: <20070422172904.477eade4@hyperion.delvare> (raw)
In-Reply-To: <22E26940476D1E48AA6F292B5316C9C33804@bes1.peakin.com>
Hi Juerg,
On Thu, 19 Apr 2007 12:04:28 -0700, Juerg Haefliger wrote:
> George, Jean,
>
> I'm struggling with the same issue for the DME1737 I'm currently
> working on. This chip also features temp zones and "hottest of x,y,z"
> PWM control. The current sysfs standard is not flexible enough to
> handle these features, especially the combination of a single PWM
> being controlled by multiple temp inputs and multiple PMWs being
> controlled by the same temp input. I believe we need another layer of
> mapping. I.e. temp->pwm is not sufficient, but rather temp->zone->pwm.
>
> I therefore propose the add the following sysfs attributes to our standard:
>
> zone[1-*]_auto_channels_temp for temp-to-zone mapping
> pwm[1-*]_auto_channels_zone for zone-to-pwm mapping
> zone[1-*]_auto_point[1-*]_temp for zone temp auto points.
I don't see what value it adds compared to what we currently have.
We have pwm[1-*]_auto_channels_temp, which is a bit vector. We have one
file per PWM, one bit per temperature channel, so all in all we have a
Npwm x Ntemp matrix, or N-N relation between PWM and temperatures. This
already allows us to handle cases such as "the hottest of tempA and
tempB control pwmC" or "tempD controls pwmE and pwmF".
You propose to add the concept of zone. According to the above, each
zone could include any temperature channel, so we have a N-N relation
between zones and temperatures. Then you express another N-N relation
between PWM channels and zones. As far as I can see, this results in a
N-N relation between temperatures and PWM, just expressed differently.
Am I missing something? What do you think it would let us express,
which the current model doesn't?
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2007-04-22 15:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 16:50 [lm-sensors] Need some guidance on adhering to the sysfs standards George T. Joseph (development)
2007-04-19 14:47 ` [lm-sensors] Need some guidance on adhering to the sysfs Jean Delvare
2007-04-19 17:13 ` George T. Joseph (development)
2007-04-19 19:04 ` Juerg Haefliger
2007-04-19 23:30 ` George T. Joseph (development)
2007-04-22 15:29 ` Jean Delvare [this message]
2007-04-22 17:12 ` Mark M. Hoffman
2007-04-22 19:07 ` Jean Delvare
2007-04-22 19:21 ` Juerg Haefliger
2007-04-22 20:41 ` Juerg Haefliger
2007-04-22 20:54 ` Juerg Haefliger
2007-04-22 20:58 ` Juerg Haefliger
2007-04-23 7:47 ` Hans de Goede
2007-04-24 18:26 ` Jean Delvare
2007-04-24 19:14 ` Jean Delvare
2007-04-24 19:31 ` Juerg Haefliger
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=20070422172904.477eade4@hyperion.delvare \
--to=khali@linux-fr.org \
--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.