[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200615143622.GX4447@sirena.org.uk>
Date: Mon, 15 Jun 2020 15:36:22 +0100
From: Mark Brown <broonie@...nel.org>
To: Robin Gong <yibin.gong@....com>
Cc: Vinod Koul <vkoul@...nel.org>,
"shawnguo@...nel.org" <shawnguo@...nel.org>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
"festevam@...il.com" <festevam@...il.com>,
"robin.murphy@....com" <robin.murphy@....com>,
"matthias.schiffer@...tq-group.com"
<matthias.schiffer@...tq-group.com>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
dl-linux-imx <linux-imx@....com>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
On Mon, Jun 15, 2020 at 02:18:54PM +0000, Robin Gong wrote:
> On 2020/06/15 21:39 Mark Brown <broonie@...nel.org> wrote:
> > On Mon, Jun 15, 2020 at 01:35:01PM +0000, Robin Gong wrote:
> > > Then how about choosing specific error code for such dma not ready
> > > case where nothing went out on the bus neither?
> > Yes, that's what I suggested.
> Seems not easy to find a suitable error value, how about EBADR which
> sounds like no any available dma_async_tx_descriptor got by calling dmaengine_prep_slave_sg?
> #define EBADR 53 /* Invalid request descriptor */
We could also pass in a flag that could be set separately to the error
code to indicate that nothing had happened to the hardware yet.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists