From: Jens Axboe <axboe@suse.de>
To: Aric Cyr <acyr@alumni.uwaterloo.ca>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: sata_sil 3112 activity LED patch
Date: Thu, 7 Jul 2005 17:11:10 +0200 [thread overview]
Message-ID: <20050707151110.GF24401@suse.de> (raw)
In-Reply-To: <20050707142301.GA11182@alumni.uwaterloo.ca>
On Thu, Jul 07 2005, Aric Cyr wrote:
> > There's also an existing variant of this in the block layer, the
> > activity_fn, that we use on the ibook/powerbook to use the sleep led as
> > an activity light. Just in case you prefer that to overloading the bmdma
> > start/stop handlers.
>
> You suggestion at first looked to be incredibly nice... until I looked
> at how much implementation was required. I am considering trying it,
> but I cannot find a place for an sata driver to call the
> blk_queue_activity_fn() with meaningful parameters during init.
>
> On a second look, I guess I would have to override
> ata_scsi_slave_config() in the driver and hook up the activity light
> there. This would be fine I guess. Unless I am interpreting this
> incorrectly, however, I would need to use a timer or something to turn
> the light back off? I'm probably missing something, so is there a
> simpler way to do this?
Hmm yes, it will require more work for you. It should be cleaned up a
little to pass in a START/STOP variable and handle everything in the
block layer instead. You probably just want to continue using the bmdma
hooks now, that is actually a fine implementation imo.
--
Jens Axboe
prev parent reply other threads:[~2005-07-07 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 2:51 sata_sil 3112 activity LED patch Aric Cyr
2005-07-06 15:07 ` Jeff Garzik
2005-07-07 12:47 ` Jens Axboe
2005-07-07 14:23 ` Aric Cyr
2005-07-07 15:11 ` Jens Axboe [this message]
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=20050707151110.GF24401@suse.de \
--to=axboe@suse.de \
--cc=acyr@alumni.uwaterloo.ca \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).