From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from muru.com ([72.249.23.125]:57082 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726693AbeLJOsy (ORCPT ); Mon, 10 Dec 2018 09:48:54 -0500 Date: Mon, 10 Dec 2018 06:48:51 -0800 From: Tony Lindgren Subject: Re: [PATCH] ARM: dts: Add am335x mcasp with l3 data port ranges Message-ID: <20181210144851.GZ6707@atomide.com> References: <20181205230356.38855-1-tony@atomide.com> <3f44b350-17a9-bdf7-33b4-130b6eeae5f0@ti.com> <48ee14e0-1361-4840-42c6-f676f2911ce6@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48ee14e0-1361-4840-42c6-f676f2911ce6@ti.com> Sender: devicetree-owner@vger.kernel.org To: Peter Ujfalusi Cc: linux-omap@vger.kernel.org, Tero Kristo , =?utf-8?Q?Beno=C3=AEt?= Cousson , devicetree@vger.kernel.org List-ID: * Peter Ujfalusi [181210 09:52]: > On 10/12/2018 9.05, Peter Ujfalusi wrote: > > Works fine on bbb + audio cape. > > For some reason my am335x-evm-sk is not booting up at all w/ linux-next, > > but I believe it is not related to this (disabled audio and still not > > booting). > > bisect on next-20181207 (am335x-evm-sk) points to: > Author: Tony Lindgren > 87fc89ced3a78f7f0845afab1934d509ef4ad0f2 > ARM: dts: am335x: Move l4 child devices to probe them with ti-sysc > > when looking for the non booting of am335x-evm-sk (nothing printed on > serial after stating kernel). OK I'm pretty sure this is because we now need to move the gpio1 ti,no-reset-on-init up to the module level because of the DDR being GPIO controlled. I'll send a patch out shortly for that. It might be also worth adding a check for having ti,no-reset-on-init at the child level to ti-sysc driver too. Regards, Tony