Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758526Ab3CGBqq (ORCPT ); Wed, 6 Mar 2013 20:46:46 -0500 Received: from mail-pb0-f50.google.com ([209.85.160.50]:61641 "EHLO mail-pb0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754288Ab3CGBqn (ORCPT ); Wed, 6 Mar 2013 20:46:43 -0500 Date: Wed, 6 Mar 2013 17:46:57 -0800 From: Olof Johansson To: Viresh Kumar Cc: rjw@sisk.pl, cpufreq@vger.kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, robin.randhawa@arm.com, Steve.Bannister@arm.com, Liviu.Dudau@arm.com, charles.garcia-tobin@arm.com, linaro-kernel@lists.linaro.org, mark.hambleton@broadcom.com, linux-arm-kernel@lists.infradead.org, Sudeep KarkadaNagesha Subject: Re: [PATCH] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue Message-ID: <20130307014657.GA7426@quad.lixom.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1540 Lines: 48 On Tue, Mar 05, 2013 at 12:52:41PM +0800, Viresh Kumar wrote: > +++ b/Documentation/devicetree/bindings/cpufreq/arm_big_little_dt.txt > @@ -0,0 +1,29 @@ > +Generic ARM big LITTLE cpufreq driver's DT glue > +----------------------------------------------- > + > +It is DT specific glue layer for generic cpufreq driver for big LITTLE systems. > + > +Both required and optional properties listed below must be defined under node > +cluster*. * can be 0 or 1. > + > +Required properties: > +- freqs: List of all supported frequencies. > + > +Optional properties: > +- clock-latency: Specify the possible maximum transition latency for clock, in > + unit of nanoseconds. > + > +Examples: > + > +cluster0: cluster@0 { > + .. > + > + freqs = <500000000 600000000 700000000 800000000 900000000 1000000000 1100000000 1200000000>; > + clock-latency = <200000>; > + > + .. > + > + cores { > + .. > + }; > +}; This binding makes no sense to me. It needs to be substantially better documented, not just a couple of sentences that people that understand bit.LITTLE thoroughly can make sense of. It also duplicates the cpu binding. I suspect this should instead be done through additions of the cpu bindings instead of duplication. So this needs to be substantially reworked. -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/