From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: Aw: Re: RFC on writel and writel_relaxed Date: Wed, 28 Mar 2018 21:20:16 +1100 Message-ID: <1522232416.21446.10.camel@kernel.crashing.org> References: <1e077f6a-90b6-cce9-6f0f-a8c003fec850@codeaurora.org> <20180327151029.GB17494@arm.com> <1522186396.7364.61.camel@kernel.crashing.org> <1522198981.7364.81.camel@kernel.crashing.org> <1522211620.7364.94.camel@kernel.crashing.org> <1522219376.7364.109.camel@kernel.crashing.org> <20180328090710.GB28871@arm.com> <1522230988.21446.7.camel@kernel.crashing.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Will Deacon , Linus Torvalds , Alexander Duyck , Sinan Kaya , Arnd Bergmann , Jason Gunthorpe , David Laight , Oliver , "open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)" , "linux-rdma@vger.kernel.org" , "Paul E. McKenney" , "netdev@vger.kernel.org" To: Lino Sanfilippo Return-path: Received: from gate.crashing.org ([63.228.1.57]:36908 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751219AbeC1KiW (ORCPT ); Wed, 28 Mar 2018 06:38:22 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Wed, 2018-03-28 at 12:13 +0200, Lino Sanfilippo wrote: > Hi, > > > > > > Yeah so that other trick I'm talking about is also used for timing > > accuracy. > > > > For example, let's say I have a device with a reset bit and the spec > > says the reset bit needs to be set for at least 10us. > > > > This is wrong: > > > > writel(1, RESET_REG); > > usleep(10); > > writel(0, RESET_REG); > > > > Because of write posting, the first write might arrive to the device > > right before the second one. > > > > Does not write posting only concern PCI? This seems to be a different topic. Furthermore > write posting should not include write reordering... Nobody's talking about re-ordering and no, write posting is rather common practice on a whole lot of different busses, not just PCI(e). Cheers, Ben.