On 2020/06/15 21:39 Mark Brown <broonie@xxxxxxxxxx> 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 */
RE: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: RE: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- From: Robin Gong <yibin.gong@xxxxxxx>
- Date: Mon, 15 Jun 2020 14:18:54 +0000
- Accept-language: en-US
- Cc: Vinod Koul <vkoul@xxxxxxxxxx>, "shawnguo@xxxxxxxxxx" <shawnguo@xxxxxxxxxx>, "s.hauer@xxxxxxxxxxxxxx" <s.hauer@xxxxxxxxxxxxxx>, "festevam@xxxxxxxxx" <festevam@xxxxxxxxx>, "robin.murphy@xxxxxxx" <robin.murphy@xxxxxxx>, "matthias.schiffer@xxxxxxxxxxxxxxx" <matthias.schiffer@xxxxxxxxxxxxxxx>, "kernel@xxxxxxxxxxxxxx" <kernel@xxxxxxxxxxxxxx>, dl-linux-imx <linux-imx@xxxxxxx>, "linux-spi@xxxxxxxxxxxxxxx" <linux-spi@xxxxxxxxxxxxxxx>, "linux-arm-kernel@xxxxxxxxxxxxxxxxxxx" <linux-arm-kernel@xxxxxxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>
- In-reply-to: <20200615133905.GV4447@sirena.org.uk>
- References: <1591880310-1813-1-git-send-email-yibin.gong@nxp.com> <1591880310-1813-2-git-send-email-yibin.gong@nxp.com> <20200611134042.GG4671@sirena.org.uk> <VE1PR04MB66383245FAD2AE33CFEA76F789810@VE1PR04MB6638.eurprd04.prod.outlook.com> <20200612101357.GA5396@sirena.org.uk> <VE1PR04MB66384013797FE6B01943F2A889810@VE1PR04MB6638.eurprd04.prod.outlook.com> <20200612141611.GI5396@sirena.org.uk> <VE1PR04MB6638B43E3AC83286946DABCD899F0@VE1PR04MB6638.eurprd04.prod.outlook.com> <20200615123553.GP4447@sirena.org.uk> <VE1PR04MB6638C65257F41072C3D61583899C0@VE1PR04MB6638.eurprd04.prod.outlook.com> <20200615133905.GV4447@sirena.org.uk>
- Follow-Ups:
- Re: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- From: Mark Brown
- Re: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- References:
- [PATCH v1 RFC 0/2] introduce fallback to pio in spi core
- From: Robin Gong
- [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- From: Robin Gong
- Re: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- From: Mark Brown
- RE: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- From: Robin Gong
- Re: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- From: Mark Brown
- RE: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- From: Robin Gong
- Re: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- From: Mark Brown
- RE: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- From: Robin Gong
- Re: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- From: Mark Brown
- RE: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- From: Robin Gong
- Re: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- From: Mark Brown
- [PATCH v1 RFC 0/2] introduce fallback to pio in spi core
- Prev by Date: Re: [cadence-spi] daisy chain
- Next by Date: Re: [PATCH v2 1/3] spi: spi-fsl-dspi: Fix external abort on interrupt in exit paths
- Previous by thread: Re: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- Next by thread: Re: [PATCH v1 RFC 1/2] spi: introduce fallback to pio
- Index(es):
 |