From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6] OMAP2+: PM: omap device: API's for handling mstandby mode
Date: Thu, 2 Dec 2010 09:22:38 +0100 [thread overview]
Message-ID: <4CF7574E.7060705@ti.com> (raw)
In-Reply-To: <4CF75192.3090705@nokia.com>
Hi Adrian and Manju,
On 12/2/2010 8:58 AM, Adrian Hunter wrote:
> On 02/12/10 08:12, ext G, Manjunath Kondaiah wrote:
>> * Adrian Hunter<adrian.hunter@nokia.com> [2010-12-01 22:16:44 +0200]:
>>> On 01/12/10 20:47, ext G, Manjunath Kondaiah wrote:
[...]
>>> Also, there is a mutex but don't these functions get called
>>> sometimes in interrupt context?
>>
>> I feel we should leave this to caller of these API's. The caller should
>> make sure that, he disables interrupts if it is used in interrupt context.
>
> How does that help? It seems to me that a mutex cannot be used for this.
That mutex is the one that was protecting the hwmod list and should not
be used, we do have a per-hwmod mutex.
But it will disappear soon, Paul already submitted a patch to replace it
by a spinlock (8297db801c424f95ef3ebfbd28e62b94798d35dd)
Please note that the goal of this API is to not be used at all :-)
It is there because of dirty HW bugs in several IPs.
So I'm fine to limit its usability and to prevent its usage everywhere.
Thanks to the spinlock it will anyway no longer be an issue.
Thanks,
Benoit
prev parent reply other threads:[~2010-12-02 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1291229228-4438-1-git-send-email-manjugk@ti.com>
2010-12-01 20:16 ` [PATCH v6] OMAP2+: PM: omap device: API's for handling mstandby mode Adrian Hunter
2010-12-02 6:12 ` G, Manjunath Kondaiah
2010-12-02 7:58 ` Adrian Hunter
2010-12-02 8:22 ` Cousson, Benoit [this message]
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=4CF7574E.7060705@ti.com \
--to=b-cousson@ti.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).