Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Radhey Shyam Pandey <radheys@xilinx.com>
To:     Vinod Koul <vinod.koul@intel.com>
CC:     "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
        "michal.simek@xilinx.com" <michal.simek@xilinx.com>,
        "Appana Durga Kedareswara Rao" <appanad@xilinx.com>,
        "lars@metafoo.de" <lars@metafoo.de>,
        "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "'RADHEYCS@GMAIL.COM'" <RADHEYCS@GMAIL.COM>
Subject: RE: [RFC 5/6] dmaengine: xilinx_dma: Program interrupt delay timeout
Thread-Topic: [RFC 5/6] dmaengine: xilinx_dma: Program interrupt delay timeout
Thread-Index: AQHTym7m/FvHP37H0EyBh1KYjLHUhaP7VWyAgAmlbQA=
Date:   Tue, 17 Apr 2018 12:48:14 +0000
Message-ID: <BN6PR02MB3282D496EC4D004A5CE37570C7B70@BN6PR02MB3282.namprd02.prod.outlook.com>
References: <1522665546-10035-1-git-send-email-radheys@xilinx.com>
 <1522665546-10035-6-git-send-email-radheys@xilinx.com>
 <20180411091159.GA6014@localhost>
In-Reply-To: <20180411091159.GA6014@localhost>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: xilinx.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d40c657b-c2dd-45c1-5d22-08d5a4617c42
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Apr 2018 12:48:14.5675
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 657af505-d5df-48d0-8300-c31994686c5c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR02MB2324
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Vinod,

> -----Original Message-----
> From: Vinod Koul [mailto:vinod.koul@intel.com]
> Sent: Wednesday, April 11, 2018 2:42 PM
> To: Radhey Shyam Pandey <radheys@xilinx.com>
> Cc: dan.j.williams@intel.com; michal.simek@xilinx.com; Appana Durga
> Kedareswara Rao <appanad@xilinx.com>; Radhey Shyam Pandey
> <radheys@xilinx.com>; lars@metafoo.de; dmaengine@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org
> Subject: Re: [RFC 5/6] dmaengine: xilinx_dma: Program interrupt delay
> timeout
>=20
> On Mon, Apr 02, 2018 at 04:09:05PM +0530, Radhey Shyam Pandey wrote:
> > Program IRQDelay for AXI DMA. The interrupt timeout mechanism causes
> > the DMA engine to generate an interrupt after the delay time period
> > has expired. It enables dmaengine to respond in real-time even though
> > interrupt coalescing is configured.
>=20
> again you are doing this only for axieth_connected, why is that?
The initial application was axieth but yes delay timeout feature may
be needed for other use cases as well. We can make delay timeout
an optional DT property. Is that fine?=20

>=20
> >
> > Signed-off-by: Radhey Shyam Pandey <radheys@xilinx.com>
> > ---
> >  drivers/dma/xilinx/xilinx_dma.c |   16 ++++++++++++++--
> >  1 files changed, 14 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/dma/xilinx/xilinx_dma.c
> b/drivers/dma/xilinx/xilinx_dma.c
> > index 518465e..ab8f1b0 100644
> > --- a/drivers/dma/xilinx/xilinx_dma.c
> > +++ b/drivers/dma/xilinx/xilinx_dma.c
> > @@ -161,8 +161,12 @@
> >  /* AXI DMA Specific Masks/Bit fields */
> >  #define XILINX_DMA_MAX_TRANS_LEN	GENMASK(22, 0)
> >  #define XILINX_DMA_CR_COALESCE_MAX	GENMASK(23, 16)
> > +#define XILINX_DMA_CR_DELAY_MAX		GENMASK(31, 24)
> >  #define XILINX_DMA_CR_CYCLIC_BD_EN_MASK	BIT(4)
> >  #define XILINX_DMA_CR_COALESCE_SHIFT	16
> > +#define XILINX_DMA_CR_DELAY_SHIFT	24
> > +#define XILINX_DMA_CR_WAITBOUND_DFT	254
> > +
> >  #define XILINX_DMA_BD_SOP		BIT(27)
> >  #define XILINX_DMA_BD_EOP		BIT(26)
> >  #define XILINX_DMA_COALESCE_MAX		255
> > @@ -1294,6 +1298,12 @@ static void xilinx_dma_start_transfer(struct
> xilinx_dma_chan *chan)
> >  		reg &=3D ~XILINX_DMA_CR_COALESCE_MAX;
> >  		reg |=3D chan->desc_pendingcount <<
> >  				  XILINX_DMA_CR_COALESCE_SHIFT;
> > +
> > +		if (chan->xdev->has_axieth_connected) {
> > +			reg  &=3D ~XILINX_DMA_CR_DELAY_MAX;
> > +			reg  |=3D XILINX_DMA_CR_WAITBOUND_DFT <<
> > +					XILINX_DMA_CR_DELAY_SHIFT;
> > +		}
> >  		dma_ctrl_write(chan, XILINX_DMA_REG_DMACR, reg);
> >  	}
> >
> > @@ -1508,7 +1518,8 @@ static irqreturn_t xilinx_dma_irq_handler(int irq=
,
> void *data)
> >  		}
> >  	}
> >
> > -	if (status & XILINX_DMA_DMASR_DLY_CNT_IRQ) {
> > +	if (!chan->xdev->has_axieth_connected && (status &
> > +			XILINX_DMA_DMASR_DLY_CNT_IRQ)) {
> >  		/*
> >  		 * Device takes too long to do the transfer when user
> requires
> >  		 * responsiveness.
> > @@ -1516,7 +1527,8 @@ static irqreturn_t xilinx_dma_irq_handler(int irq=
,
> void *data)
> >  		dev_dbg(chan->dev, "Inter-packet latency too long\n");
> >  	}
> >
> > -	if (status & XILINX_DMA_DMASR_FRM_CNT_IRQ) {
> > +	if (status & (XILINX_DMA_DMASR_FRM_CNT_IRQ |
> > +		      XILINX_DMA_DMASR_DLY_CNT_IRQ)) {
> >  		spin_lock(&chan->lock);
> >  		xilinx_dma_complete_descriptor(chan);
> >  		chan->idle =3D true;
> > --
> > 1.7.1
> >
>=20
> --
> ~Vinod