[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZQrR5RBBaJn4wZB+@arm.com>
Date: Wed, 20 Sep 2023 12:05:09 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Jan Bottorff <janb@...amperecomputing.com>
Cc: Yann Sionneau <ysionneau@...rayinc.com>,
Wolfram Sang <wsa@...nel.org>,
Serge Semin <fancer.lancer@...il.com>,
Yann Sionneau <yann@...nneau.net>,
Will Deacon <will@...nel.org>,
Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Jan Dabros <jsd@...ihalf.com>,
Andi Shyti <andi.shyti@...nel.org>,
Philipp Zabel <p.zabel@...gutronix.de>,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] i2c: designware: Fix corrupted memory seen in the ISR
On Wed, Sep 20, 2023 at 11:44:58AM +0100, Catalin Marinas wrote:
> On Tue, Sep 19, 2023 at 11:54:10AM -0700, Jan Bottorff wrote:
> > The ARM docs do have a specific example case where the device write triggers
> > an interrupt, and that example specifically says a DSB barrier is needed.
>
> Yeah, the Arm ARM is not very precise here on what the mailbox is,
> whether it's a local or shared peripheral and they went for the
> stronger DMB. Will added a good explanation on why a DMB is sufficient
^^^
DSB
(fixing typo in my reply)
--
Catalin
Powered by blists - more mailing lists