linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pawel Moll <pawel.moll@arm.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexander Shiyan <shc_work@mail.ru>,
	Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>,
	Russell King <linux@arm.linux.org.uk>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>
Subject: Re: [PATCH 2/3] ARM/leds: move ARM Versatile LED driver to leds subsystem
Date: Tue, 11 Mar 2014 12:23:54 +0000	[thread overview]
Message-ID: <1394540634.21334.27.camel@hornet> (raw)
In-Reply-To: <CACRpkdb+nLnjM7PUtkzmSJLjEC7FOH65sgOB6m-BUPB8YMzxiA@mail.gmail.com>

On Tue, 2014-03-11 at 12:18 +0000, Linus Walleij wrote:
> On Thu, Feb 27, 2014 at 3:07 PM, Alexander Shiyan <shc_work@mail.ru> wrote:
> > Четверг, 27 февраля 2014, 14:58 +01:00 от Linus Walleij <linus.walleij@linaro.org>:
> >> Now that we have converted this driver to a real platform device
> >> module-based thing, we move the driver down into the LEDs
> >> subsystem and rename the config option to LEDS_VERSATILE.
> >
> > In fact, it can be converted to use basic-mmio-gpio => leds-gpio.
> 
> Hm, yeah I see what you mean. However this register is not described
> as a GPIO register, and on all Versatile/RealView boards these signals
> are soldered to LEDs, so they are not general purpose at all.
> 
> On some systems without "real" GPIO the above would lead to
> compiling in the entire gpiolib (149 KB) just to do this.
> 
> I would agree more with inventing something like leds-mmio as a
> separate refactoring after this, i.e. a driver for any memory-mapped
> LED, which should cover a few cases. What do you think about this
> idea?

Something like this?
http://thread.gmane.org/gmane.linux.kernel/1387110 ;-)

But seriously speaking, I did exactly what Alexander mentioned on VE,
considering the SYS_LED & alikes as "pseudo-gpios".

Pawel

  reply	other threads:[~2014-03-11 12:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 13:58 [PATCH 1/3] ARM: plat-versatile: convert LEDs to platform device Linus Walleij
2014-02-27 13:58 ` [PATCH 2/3] ARM/leds: move ARM Versatile LED driver to leds subsystem Linus Walleij
2014-02-27 14:07   ` Alexander Shiyan
2014-03-11 12:18     ` Linus Walleij
2014-03-11 12:23       ` Pawel Moll [this message]
2014-03-11 12:41         ` Alexander Shiyan
2014-03-14  9:55         ` Linus Walleij
2014-03-11 12:19   ` Linus Walleij
2014-03-27 17:30     ` Bryan Wu
2014-02-27 13:58 ` [PATCH 3/3] ARM: plat-versatile: update defconfigs for Versatile LEDs Linus Walleij

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=1394540634.21334.27.camel@hornet \
    --to=pawel.moll@arm.com \
    --cc=cooloney@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=rpurdie@rpsys.net \
    --cc=shc_work@mail.ru \
    /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).