Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933870AbbHKIAb (ORCPT ); Tue, 11 Aug 2015 04:00:31 -0400 Received: from mail-pa0-f41.google.com ([209.85.220.41]:36164 "EHLO mail-pa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932320AbbHKIA1 (ORCPT ); Tue, 11 Aug 2015 04:00:27 -0400 Date: Tue, 11 Aug 2015 13:30:23 +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: <20150811080023.GB5509@linux> References: <1438010430-5802-2-git-send-email-lee.jones@linaro.org> <20150728022936.GB1229@linux> <20150728225510.GB3159@codeaurora.org> <20150729081403.GH2284@x1> <20150729221526.GE3159@codeaurora.org> <20150730084634.GD9319@x1> <20150731163715.GV3159@codeaurora.org> <20150803034642.GV899@linux> <20150810132247.GH3249@x1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150810132247.GH3249@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: 1024 Lines: 37 On 10-08-15, 14:22, Lee Jones wrote: > > Optional properties: > > +- opp-cuts: One or more strings, describing the versions of hardware the OPPs > > + can support. > > This isn't very generic. > > I'm guessing some vendors my have quite a few ways to differentiate > between board versions/revisions/cuts etc. > > How about another array where a vendor can choose to identify a piece > of hardware however they see fit. > > Example 1 (simple version): > > /* Version 1 */ > opp-version = <1>; > > Example 2 (using the kernel's versioning): > > /* 2.6.32-rc1 */ > opp-version = <2 6 32 1>; > > Example 3 (using ST's versioning): > > /* Major 2, Minor 0, Cut 2, All substrates */ > opp-version = <2 0 2 0xff>; But how will we parse this with generic code ? -- 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/