From: Tony Lindgren <tony@atomide.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Nishanth Menon <nm@ti.com>,
marc.zyngier@arm.com,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
Felipe Balbi <balbi@ti.com>
Subject: Re: [PATCH] arm: dts: dra7: arch timer sits in always-on power domain
Date: Wed, 15 Jul 2015 03:00:36 -0700 [thread overview]
Message-ID: <20150715100035.GB17550@atomide.com> (raw)
In-Reply-To: <20150715092437.GC9627@leverpostej>
* Mark Rutland <mark.rutland@arm.com> [150715 02:27]:
> On Mon, Jul 13, 2015 at 09:41:41PM +0100, Felipe Balbi wrote:
> > According to DRA7x TRM section 4.3.5 Realtime Counter (Master Counter),
> > the realtime counter sits in the Wakeup Always-On Power domain.
> > Furthermore, the counter will automatically switch the 32K clock source
> > when MPU goes into standby and automatically switch back to SYS_CLK or
> > ABE_LP when MPU goes out of standby.
>
> While the counter is in an always-on domain (the architecture mandates
> this) I don't think that applies to the timers (i.e. the comparators
> within a CPU), which are almost certainly not in an always-on domain.
>
> I suspect that this is incorrect, and it will be very painful to debug
> if it is...
OK good point. And there would have to be some wake-up line wired to the
IO chain or the PMIC in this case if the comparator was always on.
Dropping this patch for now anyways.
Regards,
Tony
prev parent reply other threads:[~2015-07-15 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 20:41 [PATCH] arm: dts: dra7: arch timer sits in always-on power domain Felipe Balbi
2015-07-13 20:53 ` Nishanth Menon
2015-07-14 4:49 ` Tony Lindgren
2015-07-14 7:05 ` Tony Lindgren
2015-07-15 9:24 ` Mark Rutland
2015-07-15 10:00 ` Tony Lindgren [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=20150715100035.GB17550@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
/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