From: Thomas Gleixner <tglx@kernel.org>
To: Tapio Reijonen <tapio.reijonen@vaisala.com>,
Russell King <linux@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Tapio Reijonen <tapio.reijonen@vaisala.com>
Subject: Re: [PATCH] ARM: fix get_cycles() always returning zero
Date: Mon, 31 Aug 2026 13:34:39 +0200 [thread overview]
Message-ID: <87ecfecyls.ffs@fw13> (raw)
In-Reply-To: <20260827-arm-get-cycles-v1-1-6495fc03369a@vaisala.com>
On Thu, Aug 27 2026 at 09:54, Tapio Reijonen wrote:
> Commit dfc256dac54c ("calibrate: Rework delay timer calibration")
> renamed read_current_timer() to delay_read_timer() and inverted its
> return convention: the old function returned 0 on success, the new one
> returns true on success. The ternary in get_cycles() was not updated,
> so it now evaluates to 0 whenever the delay timer is present and
> readable, which is precisely when it used to work.
commit e1e3a0ab69c64eedaf53dce9306f8a090bf038f0 upstream
prev parent reply other threads:[~2026-08-31 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 9:54 [PATCH] ARM: fix get_cycles() always returning zero Tapio Reijonen
2026-08-31 11:34 ` Thomas Gleixner [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=87ecfecyls.ffs@fw13 \
--to=tglx@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tapio.reijonen@vaisala.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;
as well as URLs for NNTP newsgroup(s).