public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Albert Cranford <ac9410@attbi.com>
Cc: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [PATCH] More i2c driver changes for 2.5.66
Date: Wed, 2 Apr 2003 22:33:59 -0800	[thread overview]
Message-ID: <20030403063359.GA1536@kroah.com> (raw)
In-Reply-To: <3E8BD2D9.8050002@attbi.com>

On Thu, Apr 03, 2003 at 01:21:13AM -0500, Albert Cranford wrote:
> I read the thread concerning the removal of proc.c & proc.h
> but hope that this does not go to Linus until the interface
> between i2c & sensors to application is somewhat defined.
> 
> At the moment we have a sysctl API used by sensors, video and
> other i2c kernel applications that is working.

The only in-kernel drivers that were using the sysctl/proc interface was
the lm75 and adm1021 drivers.  The video and other i2c kernel drivers do
not use this interface at all.

Those two drivers, and the two other chip drivers that I added to the
kernel in this set of patches were converted over to the sysfs interface
(well one of the new ones were, the other one will build and run, but
doesn't export any sysfs files yet, that will change soon.)

> Our desire to switch the sensors to sysfs interface should not
> break other applications.  At least until we have a model/api
> to propose to these other drivers.

Yes, any applications that used the sysctl interface to get data from
those two driver will break.  However we have to switch at some point in
time, and the userspace library can't be worked on very well if the
kernel can't support it yet :)

So I'm choosing to update the kernel first, and will be working on the
library in the coming weeks.  As there is no real sensors support
besides those two drivers in the main kernel, I didn't break much :)

> In my personal home systems I use it87 driver and have been
> somewhat successful in switching to sysfs.  A big blocking
> point is there is no application to read/set/monitor the
> driver, so it is basically unverified.

I tested the changes I did by using echo and cat, no library or other
applications are needed just yet.

thanks,

greg k-h

  reply	other threads:[~2003-04-03  6:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-03  0:14 [BK PATCH] More i2c driver changes for 2.5.66 Greg KH
2003-04-03  0:15 ` [PATCH] " Greg KH
2003-04-03  0:15   ` Greg KH
2003-04-03  0:15     ` Greg KH
2003-04-03  0:15       ` Greg KH
2003-04-03  0:15         ` Greg KH
2003-04-03  0:15           ` Greg KH
2003-04-03  0:15             ` Greg KH
2003-04-03  0:15               ` Greg KH
2003-04-03  0:15                 ` Greg KH
2003-04-03  0:15                   ` Greg KH
2003-04-03  0:15                     ` Greg KH
2003-04-03  0:15                       ` Greg KH
2003-04-03  0:15                         ` Greg KH
2003-04-03  0:15                           ` Greg KH
2003-04-03  0:15                             ` Greg KH
2003-04-03  6:21                 ` Albert Cranford
2003-04-03  6:33                   ` Greg KH [this message]
2003-04-03 13:06                     ` Albert Cranford
2003-04-03 16:37                       ` 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=20030403063359.GA1536@kroah.com \
    --to=greg@kroah.com \
    --cc=ac9410@attbi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sensors@stimpy.netroedge.com \
    /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