From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 3/5] clocksource: stm32: only use 32 bits timers
Date: Wed, 18 Oct 2017 20:35:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1710182032170.2477@nanos> (raw)
In-Reply-To: <1508331506-23782-4-git-send-email-benjamin.gaignard@linaro.org>
On Wed, 18 Oct 2017, Benjamin Gaignard wrote:
> 16 bits hardware are not enough accure to be used.
That should probably read:
16 bit counters are not accurate enough to be used.
Right?
> Do no allow them to be probed by tested max counter value.
I really do not understand why you want to do this. Accuracy is not really
a reason to dismiss working hardware right away. What you can do is to
lower the rating so other eventually available hardware will be preferred.
I might be missing something, but if so this is obviously missing in the
changelog.
Thanks,
tglx
next prev parent reply other threads:[~2017-10-18 18:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 12:58 [PATCH v6 0/5] stm32 clocksource driver rework Benjamin Gaignard
2017-10-18 12:58 ` [PATCH v6 1/5] timer: add timer_of_deinit function Benjamin Gaignard
2017-10-18 12:58 ` [PATCH v6 2/5] clocksource: stm32: convert driver to timer_of Benjamin Gaignard
2017-10-18 18:31 ` Thomas Gleixner
2017-10-18 19:32 ` Benjamin Gaignard
2017-10-19 9:07 ` Daniel Lezcano
2017-10-18 12:58 ` [PATCH v6 3/5] clocksource: stm32: only use 32 bits timers Benjamin Gaignard
2017-10-18 18:35 ` Thomas Gleixner [this message]
2017-10-18 12:58 ` [PATCH v6 4/5] clocksource: stm32: add clocksource support Benjamin Gaignard
2017-10-18 18:59 ` Thomas Gleixner
2017-10-19 8:06 ` Benjamin Gaignard
2017-10-19 8:18 ` Thomas Gleixner
2017-10-18 12:58 ` [PATCH v6 5/5] arm: dts: stm32: remove useless clocksource nodes Benjamin Gaignard
2017-10-18 13:21 ` Rob Herring
2017-10-18 13:38 ` Benjamin Gaignard
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=alpine.DEB.2.20.1710182032170.2477@nanos \
--to=tglx@linutronix.de \
--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