[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vekh0YeqrQs2eO0+sNMhn5qBLNS+9fQQLkJak=qwHeToQ@mail.gmail.com>
Date: Tue, 3 Nov 2015 10:22:25 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Vinod Koul <vinod.koul@...el.com>,
Sinan Kaya <okaya@...eaurora.org>,
"dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>,
timur@...eaurora.org, cov@...eaurora.org, jcm@...hat.com,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V2 2/3] dmaselftest: add memcpy selftest support functions
On Tue, Nov 3, 2015 at 9:44 AM, Dan Williams <dan.j.williams@...el.com> wrote:
> On Mon, Nov 2, 2015 at 10:30 PM, Vinod Koul <vinod.koul@...el.com> wrote:
>> On Mon, Nov 02, 2015 at 11:18:37PM -0500, Sinan Kaya wrote:
>>> On 11/2/2015 11:15 PM, Vinod Koul wrote:
>>> >On Mon, Nov 02, 2015 at 01:07:38AM -0500, Sinan Kaya wrote:
>>> This one; on the other hand, is selftest to verify hardware is
>>> working as expected during power up.
I prefer to have such nice case by run time parameter (let's say
common to all DMA Engine drivers)
>> We can have common code which is used for dmatest as well as selftest. I do
>> not want to see same code duplicated..
First thought was to merge this to dmatest, however, some DMA
controllers doesn't have a memcpy capability.
How would we test them?
--
With Best Regards,
Andy Shevchenko
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists