[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151103160622.GC12910@localhost>
Date: Tue, 3 Nov 2015 21:36:22 +0530
From: Vinod Koul <vinod.koul@...el.com>
To: Dan Williams <dan.j.williams@...el.com>
Cc: 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 Mon, Nov 02, 2015 at 11:44:23PM -0800, Dan Williams wrote:
> Originally ioatdma and iop-adma had local self tests before Haavard
> created dmatest. I agree having the drivers also do a test each boot
> is redundant, but then again dmatest is not automatic and I saw the
> local self test catch an interrupt setup regression.
Well the question here is not about why selftest but rather code duplication
and using same routines for both selftest as well as dmatest
>
> Maybe you could arrange for drivers to do a quick autorun through
> dmatest on load if dmatest is enabled, but otherwise load without
> testing?
That would be a good thing to do, but then most distro just enable all
config options, so this should be protected for "test" builds
> Just my 2 cents from a dmaengine spectator.
Thats an understatement :)
> --
> To unsubscribe from this list: send the line "unsubscribe dmaengine" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
~Vinod
--
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