From: Richard Purdie <rpurdie@rpsys.net>
To: Robin Farine <robin.farine@terminus.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] LEDS: generic driver
Date: Fri, 08 Jun 2007 00:27:52 +0100 [thread overview]
Message-ID: <1181258872.30600.12.camel@localhost.localdomain> (raw)
In-Reply-To: <200706061902.06738.robin.farine@terminus.org>
On Wed, 2007-06-06 at 19:02 +0200, Robin Farine wrote:
> From: Robin Farine <robin.farine@terminus.org>
>
> This generic LED driver implements the platform independent part of a
> LED driver letting platform specific code focus on the hardware
> details. The driver binds to platform devices named "Generic-LED"
> which provide the platform specific data and code needed to act on an
> LED.
>
> This is useful for platforms with exotic ways of controlling LEDs
> which preclude the use of a common LED driver such as GPIO based
> drivers.
>
> Signed-off-by: Robin Farine <robin.farine@terminus.org>
I'm not sure about this to be honest. I can see a case for perhaps
having a couple of standard suspend/resume functions for platform device
based LED drivers as those functions are often identical. I'm not sure
whether there is going to be much need for more than that.
Having looked through a few of the LED drivers, even the suspend/resume
functions are often different...
>From a style point of view, why not s/pdev_to_led/platform_get_drvdata/?
What are your thoughts on multiple LEDs on a single device?
Given the LED class is going to get a conversion to struct device soon,
I'd prefer to put this on hold until after I've made that conversion at
which point I'll reconsider this.
Regards,
Richard
next prev parent reply other threads:[~2007-06-07 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ab8cd0edce36b4ea93429c7ab695f5a967b11365.1181149111.git.robin.farine@terminus.org>
2007-06-06 17:02 ` Robin Farine
2007-06-07 23:27 ` Richard Purdie [this message]
2007-06-08 8:48 ` Robin Farine
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=1181258872.30600.12.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.farine@terminus.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
all inboxes | Powered by JetHome®