From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: OMAP baseline test results for v3.7-rc1 Date: Mon, 22 Oct 2012 10:53:19 -0700 Message-ID: <87objufl68.fsf@deeprootsystems.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-da0-f46.google.com ([209.85.210.46]:63731 "EHLO mail-da0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755842Ab2JVRwy (ORCPT ); Mon, 22 Oct 2012 13:52:54 -0400 Received: by mail-da0-f46.google.com with SMTP id n41so1491086dak.19 for ; Mon, 22 Oct 2012 10:52:54 -0700 (PDT) In-Reply-To: (Paul Walmsley's message of "Sat, 20 Oct 2012 06:24:03 +0000 (UTC)") 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 Paul Walmsley writes: > Hi Kevin > > On Fri, 19 Oct 2012, Paul Walmsley wrote: > >> On Thu, 18 Oct 2012, Paul Walmsley wrote: >> >> > Here are some basic OMAP test results for Linux v3.7-rc1. >> > Logs and other details at http://www.pwsan.com/omap/testlogs/test_v3.7-rc1/ > > ... > >> > Failing tests: needing investigation >> > ------------------------------------ >> > > > ... > >> > PM tests: >> >> * 3730 Beagle XM: OPPs do not initialize >> - Several "find_device_opp: Invalid parameters" messages appear on boot; >> related warnings follow >> - Cause unknown > > This one seems to be caused by this commit: > > commit 24d7b40a60cf19008334bcbcbd98da374d4d9c64 > Author: Kevin Hilman > Date: Thu Sep 6 14:03:08 2012 -0700 > > ARM: OMAP2+: PM: MPU DVFS: use generic CPU device for MPU-SS > > Care to take a look at it and fix it? > Yup, will fix. Looks like this exposed some initcall ordering issues in the Beagle board file when adding OPPs. Kevin