From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Anatol Pomozov
<anatol.pomozov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Daniel Lezcano
<daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
John Stultz <john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Paul Walmsley <paul-DWxLp4Yu+b8AvxtiuMwx3w@public.gmane.org>,
marc.zyngier-5wv7dgnIgG8@public.gmane.org
Subject: Re: [PATCH] timekeeping: Move persistent clock registration code from ARM to kernel
Date: Fri, 9 Jan 2015 13:59:07 +0000 [thread overview]
Message-ID: <20150109135907.GF12942@leverpostej> (raw)
In-Reply-To: <20150109094913.GB27845@ulmo>
On Fri, Jan 09, 2015 at 09:49:14AM +0000, Thierry Reding wrote:
> On Sat, Nov 15, 2014 at 02:38:00AM +0100, Thomas Gleixner wrote:
> > On Sat, 15 Nov 2014, Thomas Gleixner wrote:
> > > On Fri, 14 Nov 2014, Anatol Pomozov wrote:
> > > > On Fri, Nov 14, 2014 at 4:18 PM, Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org> wrote:
> > > > >> So what I suppose to do with my patch? If it does not work could
> > > > >> anyone provide patch that removes ARM arch dependency from
> > > > >> tegra20_timer.c?
> > > > >
> > > > > Huch? You want other people to solve your problems?
> > > >
> > > > This is not the point. I provided patch that fixes the issue. Other
> > > > people said that they have ideas how to do it different (and better)
> > > > way. So I am asking to share these ideas represented as a patch.
> > >
> > > That's not the way it works.
> > >
> > > You sent a patch to solve an problem which you are facing.
> > >
> > > Now the people who review the patch think that there is a better
> > > approach than moving code from arm/ to the timekeeping core code.
> > >
> > > So it's up to you to come up with a patch which solves the problem in
> > > the right way.
> >
> > And just for the record this whole thing is just hilarious.
> >
> > ARM64 selects ARM_ARCH_TIMER which registers the architected timer as
> > the primary clocksource.
> >
> > Now that timer has the following flag set:
> >
> > CLOCK_SOURCE_SUSPEND_NONSTOP
> >
> > And that flag causes the core timekeeping code to use the clocksource
> > to figure out the time which the machine spent in suspend.
>
> As I understand it the architected timer will be turned off along with
> the rest of the CPU complex on Tegra. I'm not sure if that's specific to
> Tegra or something that other SoCs may do as well.
That doesn't sound right to me: the architecture specifies that the
system counter must be implemented in an always-on power domain.
Note that that only applies to the counter, not the timers (as the
comparators can be turned off with the CPUs).
Mark.
next prev parent reply other threads:[~2015-01-09 13:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 19:34 [PATCH] timekeeping: Move persistent clock registration code from ARM to kernel Anatol Pomozov
[not found] ` <1415388855-35074-1-git-send-email-anatol.pomozov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-07 19:42 ` Anatol Pomozov
2014-11-10 9:53 ` Thierry Reding
2014-11-10 19:26 ` Anatol Pomozov
[not found] ` <CAOMFOmXpAm5iKCLFyorTW+n9YmgZMmrDGGe736tJX8C6BYQv-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-13 22:46 ` Thomas Gleixner
2014-11-13 23:21 ` John Stultz
[not found] ` <CALAqxLXYVLXZafNH_ag3WDFHkhMe5t23zLbvg7Sq+4_rTfy+Kw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-14 0:26 ` Thomas Gleixner
2015-01-09 9:43 ` Thierry Reding
2015-01-09 19:18 ` John Stultz
2014-11-14 22:03 ` Anatol Pomozov
[not found] ` <CAOMFOmVziftM=pWGG-L9J-E6AHYAK7k9bmBcpS1adPboLciX9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-15 0:18 ` Thomas Gleixner
2014-11-15 0:51 ` Anatol Pomozov
[not found] ` <CAOMFOmV5=tes6Ak1eUKb2qircp8ba6jt6v-bg66Kp_-jYk9m2w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-15 1:09 ` Thomas Gleixner
2014-11-15 1:38 ` Thomas Gleixner
2015-01-09 9:49 ` Thierry Reding
2015-01-09 13:59 ` Mark Rutland [this message]
2015-01-09 14:09 ` Thierry Reding
[not found] ` <20150109140902.GA7526-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>
2015-01-09 19:48 ` Paul Walmsley
2015-01-09 13:30 ` Daniel Lezcano
2014-11-15 1:07 ` 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=20150109135907.GF12942@leverpostej \
--to=mark.rutland-5wv7dgnigg8@public.gmane.org \
--cc=anatol.pomozov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marc.zyngier-5wv7dgnIgG8@public.gmane.org \
--cc=paul-DWxLp4Yu+b8AvxtiuMwx3w@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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).