[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 09 Sep 2016 22:50:43 +0200
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Hoan Tran <hotran@....com>, linux-hwmon@...r.kernel.org,
Jonathan Corbet <corbet@....net>,
Jean Delvare <jdelvare@...e.com>,
Ashwin Chaugule <ashwin.chaugule@...aro.org>,
Duc Dang <dhdang@....com>,
Jassi Brar <jassisinghbrar@...il.com>,
linux-doc@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>,
Devicetree List <devicetree@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>, Loc Ho <lho@....com>,
Guenter Roeck <linux@...ck-us.net>
Subject: Re: [PATCH] hwmon: xgene: access mailbox as RAM
On Friday, September 9, 2016 1:43:17 PM CEST Hoan Tran wrote:
>
> > * Are you sure you don't need any smp_rmb()/smp_wmb() barriers
> > between the accesses?
>
> No, we don't need a strict read/write during access PCC subspace. Just
> make sure all access is committed before PCC send message to the
> platform which done by PCC mailbox driver.
>
Ok, got it. The PCC mailbox driver presumably uses writel() to
send the message, and that implies the necessary barrier
(unlike writel_relaxed), right?
Arnd
Powered by blists - more mailing lists