From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Cherian Subject: Re: [PATCH v2] ARM: dts: am33xx: Move the cppi41dma node so it's probed early Date: Tue, 29 Apr 2014 13:57:34 +0530 Message-ID: <535F6276.4050601@ti.com> References: <1398373881-23369-1-git-send-email-ezequiel@vanguardiasur.com.ar> <535F5BA5.6000903@ti.com> <535F5D6B.6090802@linutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from comal.ext.ti.com ([198.47.26.152]:36445 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757141AbaD2I2G (ORCPT ); Tue, 29 Apr 2014 04:28:06 -0400 In-Reply-To: <535F5D6B.6090802@linutronix.de> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Sebastian Andrzej Siewior , Yegor Yefremov , Ezequiel Garcia Cc: linux-arm-kernel , "linux-omap@vger.kernel.org" , Benoit Cousson , Felipe Balbi , Tony Lindgren Hi Sebastian, On 4/29/2014 1:36 PM, Sebastian Andrzej Siewior wrote: > On 04/29/2014 09:58 AM, George Cherian wrote: >>>> This is easily fixed by moving the node at the beggining of the child >>>> list, >>>> so it's probed first. >> This will give issues on module removal. >> Since we use device_for_each_child in remove patch, it will try to >> remove cppi dma controller, while the channel >> is still in use by musb node. > Isn't this currently disabled because it blew up in the phy code? Yes. So how if the dt looks like this usb { .... .... usb_ctrl_mod { .... .... }; usb0 { .... .... }; usb0_phy { .... .... }; usb1 { .... .... }; usb1_phy { .... .... }; cppi41dma { .... .... }; }; > > Sebastian > -- -George