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

[-- Attachment #1: Type: text/plain, Size: 686 bytes --]

On Mon, 2006-05-01 at 19:10 +1000, Benjamin Herrenschmidt wrote:

> 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 suppose then what I'll do is request a done callback, and when an LED
update comes in while not done, just save it into a new 'next state
should be' variable, which is compared when done so that at worst I
loose events, but not the final status.

Can I use pmu_request from within the done callback with the same
structure? Probably not a good idea right? I can schedule_work then.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]

  reply	other threads:[~2006-05-01  9:25 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
2006-05-01  9:25         ` Johannes Berg [this message]
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=1146475513.24172.10.camel@localhost \
    --to=johannes@sipsolutions.net \
    --cc=benh@kernel.crashing.org \
    --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).