From: Arjan van de Ven <arjan@infradead.org>
To: Kaiwan N Billimoria <kaiwan@designergraphix.com>
Cc: Greg KH <greg@kroah.com>,
philippe.seewer@bfh.ch, linux-kernel@vger.kernel.org
Subject: Re: Stuck creating sysfs hooks for a driver..
Date: Thu, 16 Feb 2006 13:16:28 +0100 [thread overview]
Message-ID: <1140092189.4117.74.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <43F46319.9090400@designergraphix.com>
> Also it's a relatively simple temperature sensor - it does not seem to
> support hysteresis temperature, i/p voltages, etc. I'm saying all this
> as the sysfs interface i envision is just a simple read-only hook: the
> o/p value (after a little userspace massaging) is the temperature in
> Celsius correct to 0.25 degrees. So it looks to me that this particular
> driver necessitates a kind-of "custom" entry under /sys/class/hwmon with
> it's own userspace support.
try to avoid this!
It is very useful for EVERYONE to only have ONE interface to report such
temperatures. That way *all* applications will just work, and nobody
needs to do 5 to 50 different interfaces in their application.
Please try to see if it's possible to use the existing userspace
interface. Pretty please with sugar on top ;)
next prev parent reply other threads:[~2006-02-16 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 7:54 Kaiwan N Billimoria
2006-02-15 22:13 ` Greg KH
2006-02-16 11:33 ` Kaiwan N Billimoria
2006-02-16 12:16 ` Arjan van de Ven [this message]
2006-02-16 16:41 ` Greg KH
2006-02-19 13:23 ` Jean Delvare
2006-02-21 6:18 ` Kaiwan N Billimoria
2006-03-31 6:01 ` SPI <-> Parport (light) bridge code (Re: Stuck creating sysfs hooks for a driver..) Kaiwan N Billimoria
[not found] <pan.2006.02.15.08.46.27.708727@bfh.ch>
2006-02-15 8:48 ` Stuck creating sysfs hooks for a driver Seewer Philippe
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=1140092189.4117.74.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=kaiwan@designergraphix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.seewer@bfh.ch \
/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
all inboxes | Powered by JetHome®