[lkml]   [2009]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC][PATCH] LED driver for Intel NAS SS4200 series
On Tue, 2009-09-15 at 22:38 +0100, Richard Purdie wrote:
> On Tue, 2009-09-15 at 13:38 -0700, Dave Hansen wrote:
> > This code is based on a driver that came in the "Open-source
> > and GPL components" download here:
> >
> >
> >
> > It was in a file called nasgpio.c inside of a second zip file
> > called
> >
> > That code used an ioctl() call to operate the LEDs. It also
> > created a new top-level /proc file just to let userspace locate
> > which dynamic major number had been allocated to the device.
> > I decided that the interface probably wasn't mergeable in that
> > form. :)
> >
> > I ripped out all of the hardware monitor support from nasgpio.c
> > as well as the smbus code that controls the LED brightness. I
> > then converted the code to use the existing LED interfaces
> > rather than the ioctl(). I don't have any need for brightness
> > control, and its code is *completely* separate from the on/off
> > controls implemented here. If anyone else wants it, I'd be
> > happy to look into adding it, but I don't care enough for now.
> At a quick review this looks good. One question: These LEDs appear to be
> attached to generic GPIOs on a southbridge that is probably in other
> devices? If so, how do we know they're connected to LEDs? Do we need to
> add some further check of what kind of device we're running on?

Good question. I assumed that the PCI ids were a sufficient enough
check. But, you're right, those PCI ids look like they're for all ICH7

Any suggestions on what kinds of checks we might add? This thing acts
like a pretty generic normal PC. Do any of the other LED drivers have a
similar problem?

-- Dave

 \ /
  Last update: 2009-09-15 23:55    [W:0.037 / U:17.060 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site