From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [PATCH net-next 2/4] net: stmmac: use correct barrier between coherent memory and MMIO Date: Fri, 2 Mar 2018 10:20:00 +0100 Message-ID: <20180302091959.GC15948@amd> References: <20180226214709.4359-1-niklas.cassel@axis.com> <20180226214709.4359-3-niklas.cassel@axis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TiqCXmo5T1hvSQQg" Cc: Giuseppe Cavallaro , Alexandre Torgue , Jose.Abreu@synopsys.com, Niklas Cassel , netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: Niklas Cassel Return-path: Content-Disposition: inline In-Reply-To: <20180226214709.4359-3-niklas.cassel@axis.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org --TiqCXmo5T1hvSQQg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! Thanks for doing the detective work! > This barrier cannot be a simple dma_wmb(), since a dma_wmb() is only > used to guarantee the ordering, with respect to other writes, > to cache coherent DMA memory. Could you explain this a bit more (and perhaps in code comment)? Ensuring other writes are done before writing the "GO!" bit should be enough, no? (If it is not, do we need heavier barriers in other places, too?) Best regards, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --TiqCXmo5T1hvSQQg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlqZFz8ACgkQMOfwapXb+vL1fgCgqThlDwvpcOZuyqi6Hp1deKW8 KWkAoLaqDLOJdCTDch6GEjgJwCEQMEgN =YSd2 -----END PGP SIGNATURE----- --TiqCXmo5T1hvSQQg--