linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Bartlomiej Sieka" <tur@semihalf.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>, rpurdie@rpsys.net
Subject: Re: Please pull linux-2.6-mpc52xx.git
Date: Tue, 18 Mar 2008 08:47:55 -0600	[thread overview]
Message-ID: <fa686aa40803180747u532f6a0bq1e64e01662bdb6bd@mail.gmail.com> (raw)
In-Reply-To: <47DF7D6F.8010808@semihalf.com>

On Tue, Mar 18, 2008 at 2:29 AM, Bartlomiej Sieka <tur@semihalf.com> wrote:
>  Grant,
>
>  Yes, the Motion-PRO LED driver has been reworked and posted:
>  http://patchwork.ozlabs.org/linuxppc/patch?q=Motion-pro&id=16617
>
>
>
>   > I need to look at it again,
>  > but it is a lot of code for a very simple thing and I wasn't sure if I
>  > should be the one to pick it up because it is in drivers/leds which
>  > has a different maintainer.
>
>  I'm copying Richard Purdie who's listed as LED SUBSYSTEM maintainer.
>
>  Richard -- could pick up the above mentioned Motion-PRO LED driver for
>  upstream inclusion? It started as a MPC5200-specific thing posted to
>  linuxppc-dev and got reviewed there, with the intent to go upstream via
>  Grant (MPC52XX maintainer). However, it seems that it should be merged
>  through your subsystem.

Okay, I've taken another look at the driver and I've figured out what
has been bothering me about it.  It seems to me that the motion pro
led driver is just the first of many that we will see (seeing as some
many people find the blinking lights rather soothing) and it's a non
trivial amount of code.

(Note: I'm not actually opposed to this driver if Richard is okay with
it; but I do think that in the long term we should move towards a more
generic approach)

In essence, this driver sets up two GPIO pins to drive LEDs.  A pretty
common approach for putting LEDs on a board.  In this case each GPIO
bank only contains 1 pin; but I imagine that on other boards there
will be multiple pins in a GPIO bank, only some of which actually used
for blinking LEDs.

I've started thinking that it would be better to split things up in
the device tree to have one node for each GPIO block and a single LED
node that maps LEDs to gpio pins.  That would allow a common driver to
be written for all GPIO driven LEDs with a single block of device tree
parsing code.  Plus, it allows other devices to use GPIO pins within
the same block (not an issue for the motion pro board; but when other
boards start coming on-line it would allow us to reduce the amount of
board specific code).  Finally, it means that the timer pin GPIO
driver can be used for more than just flashing an attached LED.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  parent reply	other threads:[~2008-03-18 14:47 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24  7:35 Please pull linux-2.6-mpc52xx.git Grant Likely
     [not found] ` <47DE94F4.90804@semihalf.com>
2008-03-17 19:19   ` Grant Likely
2008-03-17 20:59     ` Wolfgang Denk
2008-03-17 21:43       ` Grant Likely
2008-03-17 22:28         ` Wolfgang Denk
2008-03-17 23:43           ` Grant Likely
2008-03-18  0:26             ` Wolfgang Denk
2008-03-18  2:42               ` Grant Likely
2008-03-18 12:20                 ` Josh Boyer
2008-03-18  8:29             ` Bartlomiej Sieka
2008-03-18 10:04               ` Richard Purdie
2008-03-25 15:29                 ` Bartlomiej Sieka
2008-03-18 14:47               ` Grant Likely [this message]
2008-03-18 16:41                 ` Richard Purdie
2008-03-18 16:53                   ` Grant Likely
2008-03-25 16:50                     ` Bartlomiej Sieka
2008-03-25 18:49                       ` Grant Likely
2008-03-25 17:38             ` Bartlomiej Sieka
2008-03-25 18:51               ` Grant Likely
2008-04-01 12:37                 ` Bartlomiej Sieka
2008-04-04 11:13                   ` Bartlomiej Sieka
2008-04-04 16:11                     ` Grant Likely
2008-04-04 16:14                       ` Grant Likely
2008-04-04 16:38                         ` Olof Johansson
2008-04-04 17:15                           ` Josh Boyer
2008-04-04 17:25                             ` Grant Likely
2008-04-15 10:34                       ` Bartlomiej Sieka
2008-03-18  7:57     ` Bartlomiej Sieka
  -- strict thread matches above, loose matches on Subject: below --
2009-01-09 23:09 Grant Likely
2008-11-14 19:20 Grant Likely
2008-11-24  3:38 ` Paul Mackerras
2008-11-24 14:41   ` Grant Likely
2008-05-01 18:04 Grant Likely
2008-04-29 13:34 Grant Likely
2007-10-16 23:22 Grant Likely
2007-10-17 10:27 ` Paul Mackerras
2007-10-17 13:13   ` Grant Likely
2007-10-10 16:30 Grant Likely
2007-10-11 17:35 ` tnt

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=fa686aa40803180747u532f6a0bq1e64e01662bdb6bd@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rpurdie@rpsys.net \
    --cc=tur@semihalf.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;
as well as URLs for NNTP newsgroup(s).