From: Jon Hunter <jonathanh@nvidia.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Thierry Reding <thierry.reding@gmail.com>,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
Pohsun Su <pohsuns@nvidia.com>, Robert Lin <robelin@nvidia.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/2] clocksource/drivers/timer-tegra186: Avoid 64-bit divide operation
Date: Thu, 3 Jul 2025 13:34:05 +0100 [thread overview]
Message-ID: <b77c900b-3b54-4cb6-8057-e5b7ca0fdfa8@nvidia.com> (raw)
In-Reply-To: <aFq29Fr5c2TAZOYO@mai.linaro.org>
Hi Daniel,
On 24/06/2025 15:32, Daniel Lezcano wrote:
> On Sat, Jun 14, 2025 at 10:55:55AM -0700, Guenter Roeck wrote:
>> Building the driver on xtensa fails with
>>
>> tensa-linux-ld: drivers/clocksource/timer-tegra186.o:
>> in function `tegra186_timer_remove':
>> timer-tegra186.c:(.text+0x350):
>> undefined reference to `__udivdi3'
>>
>> Avoid the problem by rearranging the offending code to avoid the 64-bit
>> divide operation.
>>
>
> Hi Guenter,
>
> Arnd posted a version which seems more complete.
>
> https://lore.kernel.org/all/20250620111939.3395525-1-arnd@kernel.org/
Actually Arnd responded here saying this version looks better :-)
https://lore.kernel.org/all/5a571236-7de0-42bc-bfb2-52a57e210852@app.fastmail.com/
OK, to pick up this series now?
Thanks
Jon
--
nvpublic
next prev parent reply other threads:[~2025-07-03 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 17:55 Guenter Roeck
2025-06-14 17:55 ` [PATCH 2/2] clocksource/drivers/timer-tegra186: Simplify calculating timeleft Guenter Roeck
2025-06-19 7:25 ` Jon Hunter
2025-07-23 7:17 ` [tip: timers/clocksource] " tip-bot2 for Guenter Roeck
2025-07-25 10:31 ` tip-bot2 for Guenter Roeck
2025-06-19 7:17 ` [PATCH 1/2] clocksource/drivers/timer-tegra186: Avoid 64-bit divide operation Jon Hunter
2025-06-24 14:32 ` Daniel Lezcano
2025-07-03 12:34 ` Jon Hunter [this message]
2025-07-03 12:42 ` Daniel Lezcano
2025-07-15 11:11 ` Daniel Lezcano
2025-07-23 7:17 ` [tip: timers/clocksource] " tip-bot2 for Guenter Roeck
2025-07-25 10:31 ` tip-bot2 for Guenter Roeck
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=b77c900b-3b54-4cb6-8057-e5b7ca0fdfa8@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=pohsuns@nvidia.com \
--cc=robelin@nvidia.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®