public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Kalliguddi, Hema" <hemahk@ti.com>
Cc: "Basak, Partha" <p-basak2@ti.com>,
	"Cousson, Benoit" <b-cousson@ti.com>,
	"paul@pwsan.com" <paul@pwsan.com>,
	"Nayak, Rajendra" <rnayak@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Gadiyar, Anand" <gadiyar@ti.com>,
	"Kamat, Nishant" <nskamat@ti.com>
Subject: Re: On the APIs for Enabling and Disabling Wakeup capability.
Date: Mon, 28 Jun 2010 09:25:26 -0700	[thread overview]
Message-ID: <878w5z6s5l.fsf@deeprootsystems.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E940270192021@dbde02.ent.ti.com> (Hema Kalliguddi's message of "Mon, 28 Jun 2010 19:55:00 +0530")

"Kalliguddi, Hema" <hemahk@ti.com> writes:

>>>>> > http://focus.ti.com/pdfs/wtbu/SWPU223D_Final_EPDF_06_07_2010.pdf
>>>>> >
>>
>>[HK] The errata is applicable to OMAP3430 only.  But this sequence
>>applicable for omap4 as well. So for submitting the changes we need to
>>have the HWMOD api to be changed to enaforce the Autodile set only
>>after the smart idle.
>
> When can I expect the HWMOD API change which includes the auto idle
> setting only after Smart idle setting and wakeup enable/disable
> settings?

Hi Hema,

If this is blocking you, rather than waiting for somone else to add this
feature, I suggest that you add the API you think would be needed with
proposed patches to the hwmod layer.  One for the idle settings, another
for wakeups.  In the changelog, describe (in detail) the reasons these
APIs would be used.

Kevin

  reply	other threads:[~2010-06-28 16:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 14:39 On the APIs for Enabling and Disabling Wakeup capability Basak, Partha
2010-06-16 14:58 ` Basak, Partha
2010-06-17  0:25 ` Kevin Hilman
2010-06-17  3:42   ` Kalliguddi, Hema
2010-06-17  9:34     ` Cousson, Benoit
2010-06-18  8:59       ` Kalliguddi, Hema
2010-06-18 14:58         ` Kevin Hilman
2010-06-22 10:29           ` Basak, Partha
2010-06-23 20:31             ` Kevin Hilman
2010-06-24 14:54               ` Kalliguddi, Hema
2010-06-24 15:04                 ` Basak, Partha
2010-06-28 14:25                 ` Kalliguddi, Hema
2010-06-28 16:25                   ` Kevin Hilman [this message]
2010-06-24 14:42           ` Kalliguddi, Hema
2010-06-27  3:05     ` David Brownell

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=878w5z6s5l.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=b-cousson@ti.com \
    --cc=gadiyar@ti.com \
    --cc=hemahk@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nskamat@ti.com \
    --cc=p-basak2@ti.com \
    --cc=paul@pwsan.com \
    --cc=rnayak@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox