[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160426162441.GJ2274@localhost>
Date: Tue, 26 Apr 2016 21:54:41 +0530
From: Vinod Koul <vinod.koul@...el.com>
To: Sinan Kaya <okaya@...eaurora.org>
Cc: dmaengine@...r.kernel.org, timur@...eaurora.org,
devicetree@...r.kernel.org, cov@...eaurora.org, jcm@...hat.com,
shankerd@...eaurora.org, vikrams@...eaurora.org,
marc.zyngier@....com, mark.rutland@....com, eric.auger@...aro.org,
agross@...eaurora.org, arnd@...db.de,
linux-arm-msm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Dan Williams <dan.j.williams@...el.com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH V17 1/3] dmaengine: qcom_hidma: implement lower level
hardware interface
On Tue, Apr 26, 2016 at 11:04:55AM -0400, Sinan Kaya wrote:
> On 4/25/2016 11:28 PM, Vinod Koul wrote:
> >> +
> >> + /* reset the channel for recovery */
> >> + if (hidma_ll_setup(lldev)) {
> >
> > should this be done in ISR?
>
> I created a new tasklet called rst_task and posted the code there.
sounds better
>
> /*
> + * Abort all transactions and perform a reset.
> + */
> +static void hidma_ll_abort(unsigned long arg)
> +{
> + u8 err_code = HIDMA_EVRE_STATUS_ERROR;
> + u8 err_info = 0xFF;
> +
> + dev_err(lldev->dev, "error 0x%x, resetting...\n",
> + cause);
right justify this and others as well please
> >> +int hidma_ll_resume(struct hidma_lldev *lldev)
> >> +{
> >> + return hidma_ll_enable(lldev);
> >> +}
> >
> > why do we need this empty function, use hidma_ll_enable.
>
> hidma_ll_enable is a common function that gets called from multiple places.
> hidma_ll_resume and hidma_ll_pause is used by the OS interface for pausing
> and resuming the DMA channel.
is there a reason why we can't have the code in resume and that being called
internally as well as externally?
> >> +/*
> >> + * Note that even though we stop this channel
> >> + * if there is a pending transaction in flight
> >> + * it will complete and follow the callback.
> >> + * This request will prevent further requests
> >> + * to be made.
> >
> > Why the odd formating?
>
> aligned to 75 characters.
This seems to be 50 chars!
--
~Vinod
Powered by blists - more mailing lists