From mboxrd@z Thu Jan 1 00:00:00 1970 From: Santosh Shilimkar Subject: Re: Multiple issues with omap4 panda es in linux next Date: Fri, 19 Apr 2013 23:23:38 +0530 Message-ID: <517184A2.9020908@ti.com> References: <20130419171318.GK10155@atomide.com> <517181B2.9070302@ti.com> <20130419174454.GM10155@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from comal.ext.ti.com ([198.47.26.152]:35191 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751564Ab3DSRvd (ORCPT ); Fri, 19 Apr 2013 13:51:33 -0400 In-Reply-To: <20130419174454.GM10155@atomide.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Tony Lindgren Cc: linux-omap@vger.kernel.org, Felipe Balbi , Tomi Valkeinen , Luciano Coelho , Roger Quadros , linux-arm-kernel@lists.infradead.org, Kishon Vijay Abraham I , Ravi Babu , Ruslan Bilovol On Friday 19 April 2013 11:14 PM, Tony Lindgren wrote: > * Santosh Shilimkar [130419 10:43]: >> On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote: >>> Hi all, >>> >>> Here's a list of breakage I've noticed so far while trying to >>> use linux next on my pandaboard es. Probably similar issues exist >>> on other boards as well. >>> >>> Ideally we would not have any breakage by the merge window, so >>> let's try to get these fixed ASAP: >>> >>> 1. Serial console broken on panda es booting with DT >>> >>> The symptoms are dmesg output stopping after few lines >>> and only continuing after pressing a key. Does not seem to >>> happen on blaze with DT for some reason. And does not happen >>> on panda es with legacy booting. >>> >> This one is known and reported on list along with fix patches and >> later pull request [1]. >> >> Unfortunately with all the testing and everything and patches have >> been on the list for quite some time, feedback on one of the patch >> received was after pull request and then there was no further >> clarification. That series address the same exact issue you have >> mentioned above. > > OK thanks. I think Paul picked some of those and the plan was > to update the branch? Which one(s) should go into v3.10 as fixes? > Main in that series was to handle driver sysc handling withing hwmod layer and that is where the series got stuck [2]. Without that support other patches won't fix the issue. > >> [1] http://patchwork.ozlabs.org/patch/229269/ [2] https://patchwork.kernel.org/patch/2166931/