[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <10fb478ddcf4d2589b9440e2b936f59b2ff27d5a.camel@microchip.com>
Date: Fri, 14 Apr 2023 23:08:16 +0000
From: <Kelvin.Cao@...rochip.com>
To: <hch@...radead.org>
CC: <dmaengine@...r.kernel.org>, <vkoul@...nel.org>,
<George.Ge@...rochip.com>, <linux-kernel@...r.kernel.org>,
<logang@...tatee.com>
Subject: Re: [PATCH v2 1/1] dmaengine: switchtec-dma: Introduce Switchtec DMA
engine PCI driver
On Thu, 2023-04-13 at 22:50 -0700, Christoph Hellwig wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you >
> > know the content is safe
> >
> > On Thu, Apr 13, 2023 at 10:40:41PM +0000, >
> > Kelvin.Cao@...rochip.com wrote:
> > > > > > > > Why is the lock needed while reading the status and
> > > > > > > > waiting
> > > > > > > > for it with long delays?
> > > > There's (low) chance of access to the same ctrl register from
> > > > other
> > > > paths which might change the value of status in an unexpected
> > > > way. > > It
> > > > also prevents the hardware operation from being interrupted
> > > > until > > it
> > > > indicates it has finished by a bit set in the status register.
> >
> > Well, the lock is obviously required to protecte the reads to the
> > register. But why do you need to hold the lock over the reads and
> > the delay?
I wanted to protect the complete hardware operation, from kick-off by
ctrl writing to status change indicating completion, which might
involves delays in between when more than 1 status checks required.
Powered by blists - more mailing lists