mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: lenz@cs.wisc.edu, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [rfc] Collie battery status sensing code
Date: Fri, 10 Mar 2006 18:50:54 +0100	[thread overview]
Message-ID: <20060310175054.GC8018@elf.ucw.cz> (raw)
In-Reply-To: <1141924371.10107.75.camel@localhost.localdomain>

Hi!

> > I thought about it, and considered it quite ugly. Result would be all
> > data on the platform bus with half-empty device on ucb1x00 "bus". It
> > would bring me some problems with registering order: if platform
> > device is registered too soon, ucb will be NULL and it will crash and
> > burn. OTOH I already have static *ucb, so it is doable, and I can do
> > it if you prefer it that way...
> 
> If you register the sharpsl-pm device in the collie_pm_add() function,
> ucb should always have registered by that point? As you say, you already
> have the static *ucb and I'm hoping using the platform device will mean
> less invasive changes in sharpsl_pm itself in the future?

Well, difference is not going to be 

> For the record, this patch from Dirk Opfer also exists. He's working on
> using sharpsl-pm on tosa.
> 
> http://www.rpsys.net/openzaurus/patches/archive/sharpsl_pm-do-r2.patch

Yep, looks nice, and will be useful for collie, too.
								Pavel

-- 
68:        byte [] adUSER = GetAtomData( GetAtomPos( AtomUSER ), true );

  reply	other threads:[~2006-03-10 17:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-09 12:38 Pavel Machek
2006-03-09 13:11 ` Pavel Machek
2006-03-09 13:19 ` Richard Purdie
2006-03-05  0:12   ` Pavel Machek
2006-03-09 17:12     ` Richard Purdie
2006-03-10 17:50       ` Pavel Machek [this message]
2006-03-10  8:55   ` Pavel Machek

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=20060310175054.GC8018@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=lenz@cs.wisc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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

Powered by JetHome