From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH] OMAP3: PM: Dynamic calculation of SDRC clock stabilization delay Date: Fri, 11 Dec 2009 16:49:15 -0800 Message-ID: <87my1pggok.fsf@deeprootsystems.com> References: <5A47E75E594F054BAF48C5E4FC4B92AB030ADD4B50@dbde02.ent.ti.com> <87skbhjwjo.fsf@deeprootsystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-pz0-f188.google.com ([209.85.222.188]:39538 "EHLO mail-pz0-f188.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762430AbZLLAtK (ORCPT ); Fri, 11 Dec 2009 19:49:10 -0500 Received: by pzk26 with SMTP id 26so963518pzk.4 for ; Fri, 11 Dec 2009 16:49:17 -0800 (PST) In-Reply-To: <87skbhjwjo.fsf@deeprootsystems.com> (Kevin Hilman's message of "Fri\, 11 Dec 2009 08\:38\:19 -0800") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "Reddy, Teerth" Cc: "linux-omap@vger.kernel.org" Kevin Hilman writes: [...] > PMC code is ARM generic and already largely exists in other places > (oprofile for one.) So the use of the PMC will need to be generalized > as well as be shown not to interfere with other users (as raised > already by Jean Pihet.) Someone is already trying to generalize a PMC interface. You might want to follow this thread: http://lists.infradead.org/pipermail/linux-arm-kernel/2009-December/005898.html Kevin