mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <dave@sr71.net>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: [RFC][PATCH] LED driver for Intel NAS SS4200 series
Date: Tue, 15 Sep 2009 14:52:08 -0700	[thread overview]
Message-ID: <1253051528.10449.11884.camel@nimitz> (raw)
In-Reply-To: <1253050704.30165.64.camel@dax.rpnet.com>

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:
> >     
> > http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Server+Products&ProductLine=Intel%C2%AE+Storage+Systems&ProductProduct=Intel%C2%AE+Entry+Storage+System+SS4200-E&OSVersion=OS+Independent
> >     
> > It was in a file called nasgpio.c inside of a second zip file
> > called SS4200-E_Linux_SIO_Driver-v1.4.zip.
> > 
> > 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
boards.

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


  reply	other threads:[~2009-09-15 21:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 20:38 Dave Hansen
2009-09-15 21:38 ` Richard Purdie
2009-09-15 21:52   ` Dave Hansen [this message]
2009-09-15 21:59     ` Richard Purdie

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=1253051528.10449.11884.camel@nimitz \
    --to=dave@sr71.net \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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®