From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] syfs attributes for signaling
Date: Wed, 10 Oct 2007 07:05:02 +0000 [thread overview]
Message-ID: <470C799E.5030407@hhs.nl> (raw)
In-Reply-To: <20071010004000.GA952@khazad-dum.debian.net>
Henrique de Moraes Holschuh wrote:
> On Tue, 09 Oct 2007, Hans de Goede wrote:
>> I just got some info from Siemens (Thanks Thilo) on howto detect the presence
>> of up to 2 power supplies with the fscscy and fscpos IC's and the status (OK or
>> fail) of these. So we need to come up with a sysfs interface for this.
>>
>> I suggest:
>> powersupplyX_present
>> powersupplyX_fault
>>
>> How does that sound?
>
> Don't we have a sysfs powersupply class? It should probably be used
> instead.
>
That would be a good idea if the darn thing was documented:
[hans@localhost linux-2.6.23-rc9.git4]$ grep -r powersupply Documentation
Documentation/arm/SA1100/LART:through a number of connectors. The powersupply
accepts voltages
[hans@localhost linux-2.6.23-rc9.git4]$
And:
[hans@localhost linux-2.6.23-rc9.git4]$ find -name '*powersupply*.c'
[hans@localhost linux-2.6.23-rc9.git4]$
And:
[hans@localhost linux-2.6.23-rc9.git4]$ grep -r powersupply .
./Documentation/arm/SA1100/LART:through a number of connectors. The powersupply
accepts voltages
./drivers/sbus/char/bbc_envctrl.c: * power for cpu/system and 'on' fo the
powersupply fan
[hans@localhost linux-2.6.23-rc9.git4]$
So either it isn't named powersupply or it is very well hiden.
GRR, found it, actually it is named power_supply. Yes that will work well, thanks!
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2007-10-10 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 0:40 [lm-sensors] syfs attributes for signaling Henrique de Moraes Holschuh
2007-10-10 7:05 ` Hans de Goede [this message]
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=470C799E.5030407@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--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.