All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Mike Chan <mike@android.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Paul Walmsley <paul@pwsan.com>
Subject: Re: Future of resource framework?
Date: Thu, 20 May 2010 18:23:20 -0500	[thread overview]
Message-ID: <4BF5C468.208@ti.com> (raw)
In-Reply-To: <AANLkTilpHjef3xbxB9QN9bj6MFmJA1jMwVxNQyZQcSKy@mail.gmail.com>

Mike Chan had written, on 05/20/2010 05:37 PM, the following:
> I'm not sure if this has been discussed, yet but since it seems that
> the resource framework will not be making it upstream, I am curious
http://marc.info/?l=linux-omap&m=127206504624556&w=2 (we are getting to 
the one month expiry date btw..)

> what are the replacements under consideration. I am starting to see
> similar issues on other platforms (msm / tegra) so more generic
> (non-omap) solution might be something to consider.

I know of one by Sanjeev Premi:
[1] http://marc.info/?l=linux-omap&m=125716806431649&w=2
it should be rather trivial to adapt it to opp layer and make it work.

-- 
Regards,
Nishanth Menon

  reply	other threads:[~2010-05-20 23:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20 22:37 Future of resource framework? Mike Chan
2010-05-20 23:23 ` Nishanth Menon [this message]
2010-05-21 16:47 ` Kevin Hilman
2010-06-03 23:31   ` Mike Chan
2010-06-03 23:52     ` Kevin Hilman
2010-06-04  0:10       ` Mike Chan
2010-06-04  3:01       ` Gadiyar, Anand
2010-06-04 10:50         ` Gopinath, Thara
2010-06-04 10:52           ` Gadiyar, Anand
2010-06-07 19:29         ` Mike Chan
2010-06-08  5:24           ` Gopinath, Thara
2010-06-07 19:31         ` Felipe Balbi

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=4BF5C468.208@ti.com \
    --to=nm@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mike@android.com \
    --cc=paul@pwsan.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.