linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] convert powermac ide blink to new led infrastructure
Date: Mon, 01 May 2006 19:10:47 +1000	[thread overview]
Message-ID: <1146474648.30710.48.camel@localhost.localdomain> (raw)
In-Reply-To: <1146473959.24172.4.camel@localhost>

On Mon, 2006-05-01 at 10:59 +0200, Johannes Berg wrote:
> On Mon, 2006-05-01 at 16:56 +1000, Benjamin Herrenschmidt wrote:
> 
> > Hrm... you find out the hard way in general ... we'll have to be careful
> > with this one, maybe have the PMU driver stop the LED after the device
> > suspend dance or do a sysdev with a suspend/resume and make sure that
> > any pending LED request is complete. Also, your code isn't testing if
> > the PMU request is still in progress before possibly sending another
> > one ... that's a bit dangerous (and may cause the LED to get "stuck").
> > You can re-use a request once it's complete though. In addition, my PMU
> > code was written to minimize spinlock usage in the hot path... There
> > might be a way to do the same here.
> 
> I don't really understand how the PMU works hence wasn't really sure
> what the whole request thing does. Do we get an interrupt when it
> completes or something? If so, could I get at that notification via the
> request structure?

Yes, there is a callback, that's the "done" function, but you can also
poll/check on request->complete though in this case, polling is not
recommended, the LED stuff should be as low latency as possible.

> I'll take a closer look and rework this, I think it's worthwhile even if
> it requires some more effort.
> 
> johannes

  reply	other threads:[~2006-05-01  9:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28 14:49 [PATCH] convert powermac ide blink to new led infrastructure Johannes Berg
2006-04-28 15:15 ` Johannes Berg
2006-04-29  9:27   ` Johannes Berg
2006-05-01  6:56   ` Benjamin Herrenschmidt
2006-05-01  8:59     ` Johannes Berg
2006-05-01  9:10       ` Benjamin Herrenschmidt [this message]
2006-05-01  9:25         ` Johannes Berg
2006-05-01  9:35           ` Benjamin Herrenschmidt
2006-05-01 21:19             ` Johannes Berg
  -- strict thread matches above, loose matches on Subject: below --
2006-06-06 23:05 Johannes Berg
2006-06-08  0:28 ` Benjamin Herrenschmidt
2006-06-09 11:47   ` Johannes Berg
2006-06-09 11:56     ` Anton Blanchard
2006-06-09 12:01       ` Johannes Berg
2006-06-21 10:11 ` Johannes Berg
2006-06-27  7:50   ` Benjamin Herrenschmidt
2006-06-27 17:31     ` Johannes Berg
2006-06-28  9:38       ` Richard Purdie
2006-06-28  9:43         ` Johannes Berg

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=1146474648.30710.48.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=johannes@sipsolutions.net \
    --cc=linuxppc-dev@ozlabs.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).