From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756115Ab2DFKdN (ORCPT ); Fri, 6 Apr 2012 06:33:13 -0400 Received: from na3sys009aog108.obsmtp.com ([74.125.149.199]:38231 "EHLO na3sys009aog108.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753350Ab2DFKdL (ORCPT ); Fri, 6 Apr 2012 06:33:11 -0400 MIME-Version: 1.0 In-Reply-To: <4F7DA009.4010802@linux.intel.com> References: <1333619620-21201-1-git-send-email-pdeschrijver@nvidia.com> <4F7DA009.4010802@linux.intel.com> From: "Shilimkar, Santosh" Date: Fri, 6 Apr 2012 16:02:37 +0530 Message-ID: Subject: Re: [RFC PATCH] cpuidle: allow per cpu latencies To: Peter De Schrijver Cc: Kevin Hilman , Len Brown , Trinabh Gupta , Russell King , Stephen Warren , Daniel Lezcano , linux-kernel@vger.kernel.org, Deepthi Dharwar , linux-tegra@vger.kernel.org, Colin Cross , Olof Johansson , linux-arm-kernel@lists.infradead.org, Arjan van de Ven Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Peter, On Thu, Apr 5, 2012 at 7:07 PM, Arjan van de Ven wrote: > On 4/5/2012 2:53 AM, Peter De Schrijver wrote: >> This patch doesn't update all cpuidle device registrations. I will do that > > question is if you want to do per cpu latencies, or if you want to have > both types of C state in one big table, and have each of the tegra cpyu > types pick half of them... > > Indeed !! That should work. I thought the C-states are always per CPU based and during the cpuidle registration you can register C-state accordingly based on the specific CPU types with different latencies if needed. Am I missing something ? Regards Santosh