public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Tegra: Add smp_twd clock for Tegra20
Date: Thu, 13 Sep 2012 12:33:18 -0600	[thread overview]
Message-ID: <505226EE.70201@wwwdotorg.org> (raw)
In-Reply-To: <20120913182749.3094.64766@nucleus>

On 09/13/2012 12:27 PM, Mike Turquette wrote:
> Quoting Stephen Warren (2012-09-13 10:26:34)
>> On 09/13/2012 09:57 AM, Stephen Warren wrote:
>>> On 09/13/2012 03:34 AM, Prashant Gaikwad wrote:
>>>> Clockevent's frequency is changed upon cpufreq change
>>>> notification. It fetches local timer's rate to update the
>>>> clockevent frequency. This patch adds local timer clock
>>>> for Tegra20.
>>>
>>> Hmm. Off-list, I'd asked you to check whether this patch, and Mike's
>>> twd/clk-notifier changes were OK for Tegra, and part of your reponse was:
>>>
>>> Tegra20 (Ventana)
>>>         Tegra's for-next (common clock) + smp_twd : Panic
>>>
>>> Is that true? If so, I can't apply this patch...
>>
>> Oh, perhaps you mean the warning below? That's exactly the issue that
>> Mike's patch was intended to solve, so it's not surprising that it'd be
>> seen as soon as we actually implement the smp_twd clock. If that's all,
>> then it seems OK to apply this.
>>
> 
> Can you confirm that the problem goes away with this patch:
> http://article.gmane.org/gmane.linux.ports.arm.kernel/187488/match=

Yes, it does.

That patch is what triggered the creation of this patch (since because
of it I noticed we didn't have the smp_twd clock in our driver).

  reply	other threads:[~2012-09-13 18:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13  9:34 [PATCH] ARM: Tegra: Add smp_twd clock for Tegra20 Prashant Gaikwad
2012-09-13 15:57 ` Stephen Warren
2012-09-13 17:26   ` Stephen Warren
2012-09-13 18:27     ` Mike Turquette
2012-09-13 18:33       ` Stephen Warren [this message]
2012-09-13 17:48 ` Stephen Warren

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=505226EE.70201@wwwdotorg.org \
    --to=swarren@wwwdotorg.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