From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from layka.disroot.org (layka.disroot.org [178.21.23.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D382330C14C for ; Fri, 15 May 2026 18:21:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=178.21.23.139 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778869280; cv=none; b=gldqW7nITYwzyLKrxKed62TsUstq837X3oLcsONJlSjqvxe32t8+/I6jZ7ZcDl2EiKBN1Iz2a0260Bqz1rXd85O2qTGhttSwSHSHx2SXxEKtWBE6FRjXslyyvhNbhdEOj9+lMBOETeRe09+qlQwALQQHMffUZJcGoxTAmmU8iZw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778869280; c=relaxed/simple; bh=zMsw4hDO1QrpuEuH2VA8Ur+UcazX6kdzV8Rz6qyfJgc=; h=MIME-Version:Date:From:To:Cc:Subject:In-Reply-To:References: Message-ID:Content-Type; b=m38HFFfEfziKmP7eGFnd+whRSbwatZhfXsN6gCbbtWs+tYqj0bOgkOmGuwBgA8AOgfrpsJzPMzTy4scLyxCpMEvDTFltuPbB4FAGHYvvuty/p+PioD1zRFIn+OL77cv9zf2eW9EHi8pJ6/bCgmA0ClBYq0I1H0lK/2rUBJNXqTs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=disroot.org; spf=pass smtp.mailfrom=disroot.org; dkim=pass (2048-bit key) header.d=disroot.org header.i=@disroot.org header.b=IY1Iqw1y; arc=none smtp.client-ip=178.21.23.139 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=disroot.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=disroot.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=disroot.org header.i=@disroot.org header.b="IY1Iqw1y" Received: from mail01.disroot.lan (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id C9A37267E0; Fri, 15 May 2026 20:21:15 +0200 (CEST) X-Virus-Scanned: SPAM Filter at disroot.org Received: from layka.disroot.org ([127.0.0.1]) by localhost (disroot.org [127.0.0.1]) (amavis, port 10024) with ESMTP id AHmlk5vZCN0t; Fri, 15 May 2026 20:21:15 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1778869275; bh=zMsw4hDO1QrpuEuH2VA8Ur+UcazX6kdzV8Rz6qyfJgc=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=IY1Iqw1yehQz81Wt+UgzFr0N0KjtmxGwkaKCt7MWeUB5NETqTCvghvFNHND7mE2SX Rz6GvHAVTMfvJRWW6G6P5Bi0xBUSnrXncvDUTn/6a25iqoow9HC3FCB5uzp9eorvqy zHI3l96t7BuOqNeDz7k44eah9plBkVT/StEWJiyqGstV838s9eCKcmLPUTLHFOTsN/ XHAzoeNTUH+l/oQH0rAVR9UTAZOPgRibsnu5xuNE1FFqFCkUxaE7Je6fHbYxoaqsYl 741V2q4AIqULSP5W7EOn/NCwQSUOhYjb5Fk0WJxJOLMZWQ+7TS6gW/HnbOGmOhIZ/A WBVqTWXo/GhcQ== Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Date: Fri, 15 May 2026 18:21:14 +0000 From: Rustam Adilov To: markus.stockhausen@gmx.de Cc: 'Chris Packham' , 'Daniel Lezcano' , 'Thomas Gleixner' , linux-kernel@vger.kernel.org Subject: Re: AW: AW: [PATCH] clocksource: rtl-otto: Change driver to use __raw reads and writes In-Reply-To: <007b01dce48e$dbebb9a0$93c32ce0$@gmx.de> References: <20260511131520.98420-1-adilov@disroot.org> <4536f1b3a66411a36ca0d01538003fd4@disroot.org> <021301dce3e3$4a530b70$def92250$@gmx.de> <007b01dce48e$dbebb9a0$93c32ce0$@gmx.de> Message-ID: <1282957d0625682218b277f0f92f5d7f@disroot.org> X-Sender: adilov@disroot.org Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On 2026-05-15 17:18, markus.stockhausen@gmx.de wrote: >> Von: Rustam Adilov >> 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 Not really because the readl_relaxed and readl appear to be both mapped to ioswabl which changes behavior as per IO_SWAP config [1]. [1] - https://elixir.bootlin.com/linux/v7.0.6/source/arch/mips/include/asm/io.h#L49