From: Joel Stanley <joel@jms.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Linus Walleij <linus.walleij@linaro.org>,
Andrew Jeffery <andrew@aj.id.au>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] clocksource/drivers/fttmr010: Be stricter on IRQs
Date: Wed, 1 Sep 2021 23:38:19 +0000 [thread overview]
Message-ID: <CACPK8Xfu7K0FosjnfaiETXVP+QX9fOtUE5PymegvHc3MaWy52A@mail.gmail.com> (raw)
In-Reply-To: <567a65a8-077b-7394-c8e2-dbd9f063e02c@kaod.org>
On Sat, 28 Aug 2021 at 08:08, Cédric Le Goater <clg@kaod.org> wrote:
> AFAICT, the ast2600 does not use a fttmr010 clocksource.
Correct.
When doing bringup of the ast2600, I updated this driver to support
the new layout. Only once I'd submitted it did I learn that aspeed
preferred to use only the Cortex A7's timer source, and only that
source.
The armv7 timer can be lost when a core goes into power save mode, but
I am told the ast2600 does not implement power saving modes, so we set
the always-on property for the arm,armv7-timer. This allows us to use
the timer as a clocksource for hrtimers, removing the need to use the
fttmr010 driver at all.
Cheers,
Joel
next prev parent reply other threads:[~2021-09-01 23:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 22:44 [PATCH 1/2] clocksource/drivers/fttmr010: Pass around less pointers Linus Walleij
2021-07-24 22:44 ` [PATCH 2/2] clocksource/drivers/fttmr010: Be stricter on IRQs Linus Walleij
2021-08-20 8:53 ` Daniel Lezcano
2021-08-20 13:39 ` Linus Walleij
2021-08-20 14:16 ` Daniel Lezcano
2021-08-21 4:20 ` Guenter Roeck
2021-08-21 8:04 ` Daniel Lezcano
2021-08-27 22:01 ` Linus Walleij
2021-08-27 22:31 ` Guenter Roeck
2021-08-28 3:37 ` Guenter Roeck
2021-08-28 8:08 ` Cédric Le Goater
2021-08-30 4:16 ` Andrew Jeffery
2021-08-30 4:58 ` [PATCH 2/2]: Be stric clocksource/drivers/fttmr010ter " Guenter Roeck
2021-08-30 6:30 ` Andrew Jeffery
2021-08-30 7:47 ` [PATCH 2/2]: Be stric clocksource/drivers/fttmr010 " Cédric Le Goater
2021-08-30 15:24 ` Guenter Roeck
2021-09-01 23:38 ` Joel Stanley [this message]
2021-08-26 16:25 ` [tip: timers/core] clocksource/drivers/fttmr010: Pass around less pointers tip-bot2 for Linus Walleij
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=CACPK8Xfu7K0FosjnfaiETXVP+QX9fOtUE5PymegvHc3MaWy52A@mail.gmail.com \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=daniel.lezcano@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.