Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	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: Tue, 31 Jan 2006 23:39:17 +0000	[thread overview]
Message-ID: <1138750757.6869.324.camel@localhost.localdomain> (raw)
In-Reply-To: <1138745323.4934.17.camel@localhost.localdomain>

On Wed, 2006-02-01 at 09:08 +1100, Benjamin Herrenschmidt wrote:
> > 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 ?

Flash cards mainly go through ide-cs which uses ide-disk.

There are several options:

1. Have the trigger on ide-disk activity (confined to ide-disk.c).

2. Have the trigger on ide-io activity (confined to ide-io.c).

3. Do something else.

4. Don't add disk activity (or any?) triggers in mainline.

Thanks to a generic API, adding triggers anywhere is fairly trivial but
probably not without controversy so they need to be carefully placed, if
at all.

We could always wait and see which of the above there is demand for. I
suspect options 1 or 2 would cover most people's needs. We're never
going to satisfy everyone (but anyone is free to apply simple patches to
get their desired trigger).

I'd rather go with option 4 than block all the led class/driver code
over any controversial triggers.

Richard


  reply	other threads:[~2006-01-31 23:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1138714918.6869.139.camel@localhost.localdomain>
     [not found] ` <58cb370e0601310646y263acb96h62c422435e7016e@mail.gmail.com>
     [not found]   ` <1138724479.6869.201.camel@localhost.localdomain>
2006-01-31 17:44     ` [PATCH 10/11] LED: Add IDE disk activity LED trigger Bartlomiej Zolnierkiewicz
2006-01-31 20:29       ` Jens Axboe
2006-01-31 22:08       ` Benjamin Herrenschmidt
2006-01-31 23:39         ` Richard Purdie [this message]
2006-02-04 15:29       ` Richard Purdie

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=1138750757.6869.324.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=axboe@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=bzolnier@gmail.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