From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Cedric Pradalier <cedric.pradalier@inrialpes.fr>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 001/001 Updated] PMAC HD runtime blinking control
Date: Tue, 24 Jan 2006 10:10:26 +1100 [thread overview]
Message-ID: <1138057827.4907.30.camel@localhost.localdomain> (raw)
In-Reply-To: <20060124073133.5cab0e93.cedric.pradalier@inrialpes.fr>
On Tue, 2006-01-24 at 07:31 +1000, Cedric Pradalier wrote:
> According to Benjamin Herrenschmidt, on Tue, 24 Jan 2006
> 00:47:16 +1100,
> >> The key I could not understand was that hwif->gendev is
> >> only initialised in the probe. So I had to move the
> >> device creation after that.
> >>
> >> Currently, it is blinking by default. Should it be that
> >> way? I guess so, since it is activated by a kernel config
> >> option. It is easy to change if required.
> >
> >Yes. In fact, by enabled default for ATA disks and by disabled for ATAPI
> >would make sense...
>
> How do I tell the difference?. There is a 'kind' in pmif,
> and also a atapi_dma flag in hwif. Which is more sensible?
You need to check drive->media ... Which is a bit annoying since it mans
it's per drive, not per-HWIF... you may want to move your sysfs entry
down one more level :) (Each HWIF has an array of 2 drives, though check
drive->present before expecting a useful struct device there)
> >Also, we should think a bit about the file name... "blinking_led" isn't
> >terrific for something that will end up in a non-ppc specific location.
> >Or maybe on the contrary it's good ... what about "activity_led"
> >rather ?
> >
>
> I'm open to any suggestion. I'll wait a bit to see if
> someone else has a comment, then I'll change to
> "activity_led".
>
> --
> Cedric
next prev parent reply other threads:[~2006-01-23 23:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 2:19 [PATCH 001/001] PMAC HD runtime blinking control Cedric Pradalier
2006-01-22 2:49 ` Benjamin Herrenschmidt
2006-01-22 8:11 ` Cedric Pradalier
2006-01-22 8:25 ` Benjamin Herrenschmidt
2006-01-23 13:38 ` [PATCH 001/001 Updated] " Cedric Pradalier
2006-01-23 13:47 ` Benjamin Herrenschmidt
2006-01-23 21:31 ` Cedric Pradalier
2006-01-23 23:10 ` Benjamin Herrenschmidt [this message]
2006-01-24 12:25 ` [PATCH 001/001 Updated again] " Cedric Pradalier
2006-01-24 23:14 ` Benjamin Herrenschmidt
2006-01-25 11:06 ` Andreas Schwab
2006-01-25 11:27 ` Cedric Pradalier
2006-01-25 12:44 ` Andreas Schwab
2006-01-22 11:56 ` [PATCH 001/001] " Arkadiusz Miskiewicz
2006-01-22 21:59 ` Benjamin Herrenschmidt
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=1138057827.4907.30.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=Linuxppc-dev@ozlabs.org \
--cc=cedric.pradalier@inrialpes.fr \
/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).