From: davidb@codeaurora.org (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 RESEND 1/2] ARM: arch timer: Set the TVAL before timer is enabled
Date: Sat, 15 Sep 2012 10:00:26 -0700 [thread overview]
Message-ID: <20120915170026.GA8706@codeaurora.org> (raw)
In-Reply-To: <1347694914-1457-1-git-send-email-rvaswani@codeaurora.org>
On Sat, Sep 15, 2012 at 12:41:53AM -0700, Rohit Vaswani wrote:
> On some hardware, the timer deasserts the interrupt when a
> new TVAL is written only when the enable bit is cleared.
> Hence explicitly disable the timer and then program the
> TVAL followed by enabling the timer.
> If this order is not followed, there are chances that
> you would not receive any timer interrupts.
It's a little unclear to me who you intend to take this patch. In the
To field, you've listed Marc, the MSM maintainers, as well as Russell.
The MSM tree doesn't really make sense, since this is general ARM
code. Marc would make sense if you depend on an active patch series
he is working on, so he could include it.
I'm guessing you meant it for Russell, though, and the rest of us as
CCs.
Thanks,
David
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2012-09-15 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 7:41 [PATCH v2 RESEND 1/2] ARM: arch timer: Set the TVAL before timer is enabled Rohit Vaswani
2012-09-15 7:41 ` [PATCH v2 RESEND 2/2] ARM: local timers: add timer support using IO mapped register Rohit Vaswani
2012-09-25 19:08 ` Rohit Vaswani
2012-09-27 15:46 ` Marc Zyngier
2012-09-28 12:28 ` Mark Rutland
2012-09-28 15:57 ` Dave Martin
2012-09-28 17:15 ` Lorenzo Pieralisi
2012-10-02 11:27 ` Dave Martin
2012-10-02 13:44 ` Lorenzo Pieralisi
2012-10-02 15:03 ` Dave Martin
2012-09-15 17:00 ` David Brown [this message]
2012-09-15 19:53 ` [PATCH v2 RESEND 1/2] ARM: arch timer: Set the TVAL before timer is enabled Rohit Vaswani
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=20120915170026.GA8706@codeaurora.org \
--to=davidb@codeaurora.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).