From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "Jens Axboe" <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org, rpurdie@rpsys.net
Subject: Re: LED: Add IDE disk activity LED trigger
Date: Tue, 31 Jan 2006 14:22:49 -0700 [thread overview]
Message-ID: <20060131212249.GR31163@cosmic.amd.com> (raw)
In-Reply-To: <20060131203552.GG4215@suse.de>
On 31/01/06 21:35 +0100, "Jens Axboe" wrote:
> Perhaps a generic solution isn't feasible, because this isn't really a
> generic problem. The LED stuff has very limited use - you mention
> embedded platforms, perhaps they should just be doing this on their own?
Possibly, but what you'll find is that many different embedded platforms
end up wanting similar behavior, and if they all do it on their own, that
ends up in a mess.
Take the Alchemy platform for example - we have a bank of LEDs at our
disposal, and we too would like to use them to do very similar things
as the ARM/Xscale folks - things like show IDE/SD/MTD traffic, or the
status of a battery. Rather then go in and hack that stuff in ourselves,
I would much rather just define a few API hooks and getting the rest for
free (or really cheap).
Perhaps it can be hidden behind a CONFIG_EMBEDDED or something so that
the desktop platforms aren't bothered by it, but speaking for the two
embedded platforms I'm attached to, my vote for this LED class is a "yes".
--
Jordan Crouse
Senior Linux Engineer
AMD - Personal Connectivity Solutions Group
<www.amd.com/embeddedprocessors>
next prev parent reply other threads:[~2006-01-31 21:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 13:41 [PATCH 10/11] LED: Add IDE disk activity LED trigger Richard Purdie
2006-01-31 14:46 ` Bartlomiej Zolnierkiewicz
2006-01-31 16:21 ` Richard Purdie
2006-01-31 17:44 ` Bartlomiej Zolnierkiewicz
2006-01-31 20:29 ` Jens Axboe
2006-01-31 22:08 ` Benjamin Herrenschmidt
2006-01-31 23:39 ` Richard Purdie
2006-02-04 15:29 ` Richard Purdie
2006-01-31 20:35 ` Jens Axboe
2006-01-31 21:22 ` Jordan Crouse [this message]
2006-02-01 0:12 ` Matt Reimer
2006-02-02 1:32 ` Adrian Bunk
2006-01-31 22:03 ` [PATCH 10/11] " Richard Purdie
2006-02-02 11:07 ` Pavel Machek
2006-02-01 16:09 ` Jan Engelhardt
2006-02-04 9:54 ` Jan-Benedict Glaw
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=20060131212249.GR31163@cosmic.amd.com \
--to=jordan.crouse@amd.com \
--cc=axboe@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.