Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934201AbbHKMBb (ORCPT ); Tue, 11 Aug 2015 08:01:31 -0400 Received: from mail-pa0-f41.google.com ([209.85.220.41]:35833 "EHLO mail-pa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934132AbbHKMB3 (ORCPT ); Tue, 11 Aug 2015 08:01:29 -0400 Date: Tue, 11 Aug 2015 17:31:24 +0530 From: Viresh Kumar To: Lee Jones Cc: Stephen Boyd , Rob Herring , Nishanth Menon , kernel@stlinux.com, "linux-pm@vger.kernel.org" , Dmitry Eremin-Solenikov , Rafael Wysocki , "linux-kernel@vger.kernel.org" , Sebastian Reichel , "devicetree@vger.kernel.org" , Arnd Bergmann , Ajit Pal Singh , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH v4 2/2] dt: power: st: Provide bindings for ST's OPPs Message-ID: <20150811120124.GH5509@linux> References: <20150729221526.GE3159@codeaurora.org> <20150730084634.GD9319@x1> <20150731163715.GV3159@codeaurora.org> <20150803034642.GV899@linux> <20150810132247.GH3249@x1> <20150811080023.GB5509@linux> <20150811093039.GA18282@x1> <20150811100941.GG5509@linux> <20150811115425.GE18282@x1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150811115425.GE18282@x1> 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: 1367 Lines: 33 On 11-08-15, 12:54, Lee Jones wrote: > The framework does not need to parse this information. It is used > solely by the platform driver, whose job it is to decide which OPPs > are appropriate for the running platform. The OPP layer needs to parse OPP nodes in DT. But for doing that it needs to know which OPPs to pick from the table as, in cases like yours or qcom, not all OPPs might be available. One of the ways to do that is: - the platform reads its efuses (or whatever) and encodes the information into a string. - This string should match with the strings present (somewhere) in the OPP table. That location can be like what I proposed few mails back. - Then the *generic* OPP code can parse only those OPP nodes which match with that string. This way, we can avoid pushing the platform code to parse OPP tables. > Back to my question; how would you like arbitrary version information, > which means different things to different vendors to be used in > shared/generic/framework code? Exactly like I wrote above. The platform just needs to give a string that should match with the OPPs .. -- viresh -- 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/