From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: smp_twd: Reconfigure clockevents after cpufreq change
Date: Tue, 14 Jun 2011 08:14:55 +0200 [thread overview]
Message-ID: <BANLkTin7DGz4P1J4k0LV8oxFTkBPJwuX9Q@mail.gmail.com> (raw)
In-Reply-To: <4DF6FBBA.7010309@ti.com>
2011/6/14 Santosh Shilimkar <santosh.shilimkar@ti.com>:
> That should be taken care by
> "smp_call_function_single(freqs->cpu, )" with notifier
> being called with all the available CPU's in the mask.
Ah! I see now.
> Did you see any issue with this patch on your platform ?
No, I don't think so, I think we saw the problem on an
earlier version that didn't use smp_call_function_single().
Thanks,
Linus Walleij
next prev parent reply other threads:[~2011-06-14 6:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 9:15 [PATCH] ARM: smp_twd: Reconfigure clockevents after cpufreq change Linus Walleij
2011-06-14 5:50 ` Linus Walleij
2011-06-14 6:00 ` Colin Cross
2011-06-14 6:12 ` Santosh Shilimkar
2011-06-14 6:14 ` Linus Walleij [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-16 23:21 Colin Cross
2011-05-17 14:00 ` Santosh Shilimkar
2011-05-17 17:06 ` Colin Cross
2011-05-18 11:32 ` Santosh Shilimkar
2011-05-19 17:32 ` Linus Walleij
2011-05-19 23:26 ` Colin Cross
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=BANLkTin7DGz4P1J4k0LV8oxFTkBPJwuX9Q@mail.gmail.com \
--to=linus.walleij@linaro.org \
--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).