From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: OMAP baseline test results for v3.16-rc4 Date: Mon, 14 Jul 2014 23:04:31 -0700 Message-ID: <20140715060431.GH20068@atomide.com> References: <20140707080238.GF28884@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:21812 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750938AbaGOGF5 (ORCPT ); Tue, 15 Jul 2014 02:05:57 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Paul Walmsley Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kernel-build-reports@lists.linaro.org * Paul Walmsley [140714 10:32]: > On Mon, 7 Jul 2014, Tony Lindgren wrote: > > > With v3.16-rc4 the PM features for omap3 should be working > > finally for device tree based booting. At lest beaglexm and > > 3xxevm should work. > > > > Maybe you are using legacy booting path to idle the UARTs still? > > > > FYI, I'm doing this to find the UART entries: > > > > uarts=$(find /sys/class/tty/ttyO*/device/power/ -type d) > > for uart in $uarts; do > > echo 3000 > $uart/autosuspend_delay_ms > > done > > > > uarts=$(find /sys/class/tty/ttyO*/power/ -type d) > > for uart in $uarts; do > > echo enabled > $uart/wakeup > > echo auto > $uart/control > > done > > > > echo 1 > /sys/kernel/debug/pm_debug/enable_off_mode > > OK thanks, I'll take a close look at it. It's not using the legacy paths, > but based on a glance at the 37xxevm logs, it looks like the bus address > of the UART isn't right. Hmm for which UART? I'm using ttyO2 on my 37xxevm FYI, it can be selected on the board based on some switch settings. I may have patched my u-boot for that too but don't remember for sure. Regards, Tony