linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Pilcher <arequipeno@gmail.com>
To: linux-leds@vger.kernel.org
Subject: Re: Registering GPIO LEDs
Date: Tue, 13 Aug 2013 18:35:06 -0500	[thread overview]
Message-ID: <kuefr3$4li$1@ger.gmane.org> (raw)
In-Reply-To: <A874F61F95741C4A9BA573A70FE3998F82E86950@DQHE06.ent.ti.com>

On 08/09/2013 12:26 AM, Kim, Milo wrote:
> It sounds you want to make the LED platform data flexible, right?

Yes, but only to the extent that it can handle this particular hardware.
I'm mostly concerned that something like a kernel upgrade, BIOS upgrade,
or loading additional modules will cause the "magic" GPIO numbers to
change.

> If you can use .dtb file in your system, it may be possible to use just offset
> values with GPIO controller, ich_gpio. Then, no hardcoded GPIO is required.

I'm fairly sure that device tree is not an option in most x86_64
distros.  (And the whole reason I'm doing this is to used such a
"mainstream" distro on this hardware, rather than the NAS vendor's
"firmware".)

For now, I think I'll go the kernel module route.  If necessary, user-
space can use sysfs to find the GPIO base of the ICH and pass it in.  I
suspect there's a way to do this entirely in the kernel, but I also
suspect that it's too much trouble to be worth the effort right now.

Thanks!

-- 
========================================================================
Ian Pilcher                                         arequipeno@gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.
========================================================================


      reply	other threads:[~2013-08-13 23:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07 22:51 Registering GPIO LEDs Ian Pilcher
2013-08-09  2:08 ` Kim, Milo
2013-08-09  3:51   ` Ian Pilcher
2013-08-09  5:26     ` Kim, Milo
2013-08-13 23:35       ` Ian Pilcher [this message]

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='kuefr3$4li$1@ger.gmane.org' \
    --to=arequipeno@gmail.com \
    --cc=linux-leds@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).