From: <markus.stockhausen@gmx.de>
To: "'Rustam Adilov'" <adilov@disroot.org>
Cc: "'Chris Packham'" <Chris.Packham@alliedtelesis.co.nz>,
"'Daniel Lezcano'" <daniel.lezcano@kernel.org>,
"'Thomas Gleixner'" <tglx@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: AW: AW: [PATCH] clocksource: rtl-otto: Change driver to use __raw reads and writes
Date: Fri, 15 May 2026 19:18:30 +0200 [thread overview]
Message-ID: <007b01dce48e$dbebb9a0$93c32ce0$@gmx.de> (raw)
In-Reply-To: <d1bd3937ca18e26e87195ae6c967662b@disroot.org>
> Von: Rustam Adilov <adilov@disroot.org>
> Gesendet: Freitag, 15. Mai 2026 16:33
> An: markus.stockhausen@gmx.de
> Betreff: Re: AW: [PATCH] clocksource: rtl-otto: Change driver to use __raw
reads and writes
> ...
> > IIRC the current functions use memory barriers while the
> > new ones do not. Timers are critical and cost me a lot
> > of time in the past [1]. We nearly lost support for several
> > devices last year. So I like to have at least some stability
> > confirmation from downstream.
>
> As far as i can see, if you untangle the the BUILDIO_MEM(l, u32) in [1]
> you should see they do have barriers as denoted by barrier argument being
set.
> So that means, in MIPS, both readl/writel are the same as their __raw
variants.
> And both ioread32/iowrite32 are using readl/writel under the hood so...
Hi,
will the __relaxed functions serve your IO_SWAP scenario too?
Markus
next prev parent reply other threads:[~2026-05-15 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 13:15 [PATCH] clocksource: rtl-otto: Change driver to use __raw reads and writes Rustam Adilov
2026-05-13 18:31 ` Rustam Adilov
2026-05-13 21:05 ` Chris Packham
2026-05-14 20:50 ` AW: " markus.stockhausen
2026-05-15 14:32 ` Rustam Adilov
2026-05-15 17:18 ` markus.stockhausen [this message]
2026-05-15 18:21 ` AW: " Rustam Adilov
2026-05-15 18:39 ` AW: " markus.stockhausen
2026-05-15 19:47 ` Rustam Adilov
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='007b01dce48e$dbebb9a0$93c32ce0$@gmx.de' \
--to=markus.stockhausen@gmx.de \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=adilov@disroot.org \
--cc=daniel.lezcano@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@kernel.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