From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Richard Purdie <rpurdie@rpsys.net>,
LKML <linux-kernel@vger.kernel.org>,
Linux-ide <linux-ide@vger.kernel.org>, Jens Axboe <axboe@suse.de>
Subject: Re: [PATCH 10/11] LED: Add IDE disk activity LED trigger
Date: Wed, 01 Feb 2006 09:08:42 +1100 [thread overview]
Message-ID: <1138745323.4934.17.camel@localhost.localdomain> (raw)
In-Reply-To: <58cb370e0601310944l421174f8j1802d94f1ae93a01@mail.gmail.com>
> Ben, code in pmac.c (+ block layer) seems to be doing something
> different then Kconfig help entry states ("Blink laptop LED on drive
> activity")?
>
> > I'll experiment with the feasibility of the block later as I've always
> > been uneasy about the hooks into the lower level layers. There are a
> > number of issues to consider though.
The hook in the block layer was Jens idea :)
> At worst it should be handled at host driver level not device driver
> (like pmac.c and hwif->act_led).
>
> > 1. The block layer isn't always aware of device activity (eg. flash
> > block erasing in mtd devices) (is this the case for IDE?).
>
> Same is true for ide-disk changes - they are aware only of filesystem
> activity (no flush cache, special commands, I/O taskfiles etc.).
It wouldn't be too hard to kick the led on DMA start and off after a
timeout kicked from DMA end...
> Isn't ->end_request hook in ide_driver_t enough?
>
> I see no reason why the custom ->end_request function cannot
> be added to ide-disk. All needed infrastructure is there.
I'm not sure ide-disk is the right spot ... what if one wants LEDs for
CD-ROMs or other IDE devices like flash cards ?
> > Alternatively it could be made to apply to all ide activity if a
> > suitable start request point was found to hook into.
>
> start_request() in ide-io.c
>
> Thanks,
> Bartlomiej
next prev parent reply other threads:[~2006-01-31 22:08 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 [this message]
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
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=1138745323.4934.17.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=axboe@suse.de \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--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.