From: Jonathan Cameron <jic23@cam.ac.uk>
To: Himanshu Chauhan <hschauhan@nulltrace.org>
Cc: Greg KH <greg@kroah.com>,
Guenter Roeck <guenter.roeck@ericsson.com>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernelnewbies@kernelnewbies.org"
<kernelnewbies@kernelnewbies.org>
Subject: Re: [lm-sensors] [PATCH] hwmon class driver registration with a device number
Date: Fri, 07 Oct 2011 12:11:01 +0100 [thread overview]
Message-ID: <4E8EDE45.5030507@cam.ac.uk> (raw)
In-Reply-To: <20111007095621.GB2944@ubuntu.ubuntu-domain>
On 10/07/11 10:56, Himanshu Chauhan wrote:
> On Thu, Oct 06, 2011 at 11:52:37PM -0700, Greg KH wrote:
>> On Fri, Oct 07, 2011 at 12:12:40PM +0530, Himanshu Chauhan wrote:
>>> On Thu, Oct 06, 2011 at 12:07:52PM -0700, Guenter Roeck wrote:
>>>> And why, and what for.
>>>
>>> The initial idea of posting to kernelnewbies was to get a hint on how
>>> the patch would be taken as. I wanted to know if developers will like
>>> the idea behind it or not. I guess, Guenter is not convinced with
>>> any of my reasoning. I am willing to clean it up further only if
>>> I get a positive hint. But it doesn't seem to be going anywhere.
>>>
>>> Thanks Guenter, Alan, and Greg for taking your time and reviewing it.
>>>
>>> Greg: To answer your last question, if this was taken positively, I
>>> was thinking of having functionality similar to misc device registration.
>>
>> But why? What is that device node going to be used for? Who would be
>> using it in userspace and where would it be tied into in the kernel?
>>
> The device node, as I said earlier, can be used for doing IOCTLS. In user space,
> applications that manage and monitor system environment will need to use this
> interface for querying the sensor's location, for example. In side the kernel,
> the driver that is driving the particular hardware sensor can register a char
> interface for all this and then register with hwmon with the same major/minor
> for usual sysfs export of data.
If location is useful info why not propose a sysfs interface for it?
next prev parent reply other threads:[~2011-10-07 11:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 17:13 [PATCH] hwmon class driver registration with a device number Himanshu Chauhan
2011-10-05 18:30 ` Guenter Roeck
2011-10-06 4:06 ` Himanshu Chauhan
2011-10-06 5:19 ` Guenter Roeck
2011-10-06 7:43 ` [lm-sensors] " Jean Delvare
2011-10-06 15:12 ` Himanshu Chauhan
2011-10-06 15:46 ` Alan Cox
2011-10-06 16:25 ` Himanshu Chauhan
2011-10-06 15:15 ` Guenter Roeck
2011-10-06 16:43 ` Himanshu Chauhan
2011-10-05 19:33 ` Greg KH
2011-10-06 4:10 ` Himanshu Chauhan
2011-10-06 18:25 ` Greg KH
2011-10-06 19:07 ` [lm-sensors] " Guenter Roeck
2011-10-07 6:42 ` Himanshu Chauhan
2011-10-07 6:52 ` Greg KH
2011-10-07 9:56 ` Himanshu Chauhan
2011-10-07 11:11 ` Jonathan Cameron [this message]
2011-10-07 15:46 ` Greg KH
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=4E8EDE45.5030507@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=greg@kroah.com \
--cc=guenter.roeck@ericsson.com \
--cc=hschauhan@nulltrace.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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