linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andy@warmcat.com (Andy Green)
To: linux-arm-kernel@lists.infradead.org
Subject: Device probe order (i2c regulator vs. platform device)
Date: Wed, 24 Mar 2010 14:38:31 +0000	[thread overview]
Message-ID: <4BAA23E7.9010100@warmcat.com> (raw)
In-Reply-To: <20100324140101.GC26453@rakim.wolfsonmicro.main>

On 03/24/10 14:01, Somebody in the thread at some point said:

>>> The only system I'm aware of which had any stuff like this was the
>>> GTA02.  I never investigated to figure out why the code there was doing
>>> what it was.
>
>> I wouldn't be so quick to assert that, you do not know all the code
>> out there in order to tell.
>
> I really am very sure that nobody has ever reported any issues here -

There's plenty of out-of-tree code.  I'm not trying to blame you for 
something, just it's too strong to say there's no problem here because 
you personally didn't see it in your neck of the woods (especially when 
I spent many weeks fighting exactly that on GTA02).

There problem's generic -->

> Until we have real systems we can look at I'm not really sure it's worth
> worrying about since there's a risk of desigining something that doesn't
> fit well with what people actually need, and there's always the chance
> that something like the device layer will solve the problem before
> anyone notices.

No I agree after both Marek's and your discussion (and remembering the 
other races I had seen), the problem is bigger than regulator API and 
the device layer would be the right place.

You're right someone needs to bring it up elsewhere.

-Andy

  reply	other threads:[~2010-03-24 14:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24  7:10 Device probe order (i2c regulator vs. platform device) Marek Szyprowski
2010-03-24  9:19 ` Andy Green
2010-03-24 11:11   ` Marek Szyprowski
2010-03-24 12:50     ` Andy Green
2010-03-24 13:11       ` Mark Brown
2010-03-24 13:22         ` Andy Green
2010-03-24 11:32   ` Mark Brown
2010-03-24 12:11     ` Andy Green
2010-03-24 14:01       ` Mark Brown
2010-03-24 14:38         ` Andy Green [this message]
2010-03-25 10:22           ` Mark Brown
2010-03-25 10:52             ` Andy Green
2010-03-24 10:21 ` Mark Brown
2010-03-24 10:57   ` Andy Green
2010-03-24 11:02   ` Marek Szyprowski
2010-03-24 11:08     ` Mark Brown
2010-03-24 11:27       ` Andy Green
2010-03-24 12:19         ` Mark Brown
2010-03-24 12:29           ` Andy Green

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=4BAA23E7.9010100@warmcat.com \
    --to=andy@warmcat.com \
    --cc=linux-arm-kernel@lists.infradead.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).