From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vinod Koul Subject: Re: [PATCH] dmaengine: tegra: add slave capabilities reporting Date: Wed, 14 Jan 2015 00:01:44 +0530 Message-ID: <20150113183144.GJ15411@intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Paul Walmsley Cc: Paul Walmsley , Laxman Dewangan , Dan Williams , Stephen Warren , Thierry Reding , Alexandre Courbot , Maxime Ripard , dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-tegra@vger.kernel.org On Tue, Jan 06, 2015 at 06:44:56AM +0000, Paul Walmsley wrote: > > After commit ecc19d17868be9c9f8f00ed928791533c420f3e0 ("dmaengine: Add > a warning for drivers not using the generic slave caps retrieval"), > the Tegra APB DMA driver causes this warning during boot: > > WARNING: CPU: 0 PID: 1 at drivers/dma/dmaengine.c:830 dma_async_device_register+0x294/0x538() > this driver doesn't support generic slave capabilities reporting > > Fix by setting the appropriate reporting structure fields that are > passed to dma_async_device_register(). > Applied, thanks -- ~Vinod