[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190604123331.GE15118@vkoul-mobl>
Date: Tue, 4 Jun 2019 18:03:31 +0530
From: Vinod Koul <vkoul@...nel.org>
To: yibin.gong@....com
Cc: robh@...nel.org, shawnguo@...nel.org, s.hauer@...gutronix.de,
festevam@...il.com, mark.rutland@....com, dan.j.williams@...el.com,
linux-imx@....com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, dmaengine@...r.kernel.org,
devicetree@...r.kernel.org, kernel@...gutronix.de
Subject: Re: [PATCH v3 5/8] dmaengine: fsl-edma: add drvdata for vf610
On 29-05-19, 17:08, yibin.gong@....com wrote:
> @@ -205,8 +228,9 @@ static int fsl_edma_probe(struct platform_device *pdev)
> if (!fsl_edma)
> return -ENOMEM;
>
> - fsl_edma->version = v1;
> - fsl_edma->dmamux_nr = DMAMUX_NR;
> + fsl_edma->drvdata = drvdata;
> + fsl_edma->version = drvdata->version;
> + fsl_edma->dmamux_nr = drvdata->dmamuxs;
And can we avoid the duplication here, you have version and dmamuxs
represented in two places. But right now it looks logical so the removal
should be done after this series
--
~Vinod
Powered by blists - more mailing lists