From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 5/6] OMAP: omap_device: Create a default omap_device_pm_latency
Date: Tue, 27 Sep 2011 11:37:52 -0700 [thread overview]
Message-ID: <20110927183752.GN6324@atomide.com> (raw)
In-Reply-To: <87hb3xzvmo.fsf@ti.com>
* Kevin Hilman <khilman@ti.com> [110927 10:56]:
> Tony Lindgren <tony@atomide.com> writes:
>
> > Isn't this racey between devices if the latency values get adjusted
> > automatically for each device?
>
> A copy of this is made for each device (uses kmemdup later in the patch.)
Oh ok, sorry for the noise.
Tony
next prev parent reply other threads:[~2011-09-27 18:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 17:18 [PATCH v3 0/6] OMAP: omap_device cleanup before device-tree integration Benoit Cousson
2011-09-27 17:18 ` [PATCH v3 1/6] OMAP: omap_device: Add omap_device_get_by_hwmod_name Benoit Cousson
2011-09-27 17:18 ` [PATCH v3 2/6] OMAP3: beagle-board: Use the omap_hwmod_name_get_dev API Benoit Cousson
2011-09-27 17:18 ` [PATCH v3 3/6] OMAP2+: pm: Use hwmod name instead of dev pointer Benoit Cousson
2011-09-27 17:18 ` [PATCH v3 4/6] OMAP2+: pm: Remove static devices variable for mpu, dsp, iva and l3 PM Benoit Cousson
2011-09-27 17:18 ` [PATCH v3 5/6] OMAP: omap_device: Create a default omap_device_pm_latency Benoit Cousson
2011-09-27 17:30 ` Tony Lindgren
2011-09-27 18:29 ` Kevin Hilman
2011-09-27 18:37 ` Tony Lindgren [this message]
2011-09-27 17:18 ` [PATCH v3 6/6] OMAP2+: devices: Remove all omap_device_pm_latency structures Benoit Cousson
2011-09-27 21:32 ` [PATCH v3 0/6] OMAP: omap_device cleanup before device-tree integration Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2011-08-09 14:54 [PATCH v3 5/6] OMAP: omap_device: Create a default omap_device_pm_latency Benoit Cousson
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=20110927183752.GN6324@atomide.com \
--to=tony@atomide.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).