From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758737AbcC3HyB (ORCPT ); Wed, 30 Mar 2016 03:54:01 -0400 Received: from mout.kundenserver.de ([212.227.17.24]:62415 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758143AbcC3Hx7 (ORCPT ); Wed, 30 Mar 2016 03:53:59 -0400 From: Arnd Bergmann To: linaro-kernel@lists.linaro.org Cc: Viresh Kumar , k.kozlowski@samsung.com, kgene.kim@samsung.com, heiko@sntech.de, linux-pm@vger.kernel.org, mmcclint@codeaurora.org, xf@rock-chips.com, Rafael Wysocki , linux-kernel@vger.kernel.org Subject: Re: [PATCH V1 Resend 2/3] cpufreq: dt: Add generic platform-device creation support Date: Wed, 30 Mar 2016 09:53:34 +0200 Message-ID: <7250220.227umpmTug@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20160330032240.GB8773@vireshk-i7> References: <12972545.Mi9sHiNJpR@wuerfel> <20160330032240.GB8773@vireshk-i7> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:A4eX2bSwuGECBNYhTSWaJ20CmvfYFe2QJOJ1wo/RjE6zVXsgGec f1xAdQJFOMIRTMQQVH73ncCcVzlo9J47XwSIu14sUpj/jSO36VIa8Xz9gUNGKNA8dv7ipDj d3lNLbptjpN2ASL4yijYId+I3nypS7WDeGaJgE/wOxeGxDo0HlxE1mjxugB7Z+D8tMe/ykt +hE1icQnIB8xBnOf9ZmuA== X-UI-Out-Filterresults: notjunk:1;V01:K0:C9rVM+xFoZk=:B6fC6cnAW6vyNqJqp5t2SR v/Qeufu8esSTJv4q5xDNlIRkhygASOxvfl1UFbWYrNvaxe85iycNO4pafTHvZKoFi9yHk48UJ MrdexFYqRjMIdkihNNziWjQmEvmJZo0FvHV5/H8Qz7t7Ais2/dGSzuvV9Gpk1tj0om+tzhtaz OM+vR+ZGw260MfugdcIteybgJEHCxfMHtBkQt9TmZ6kPAwwb9T/DTn6QBihAl7zLT+YnW8Scy z3y0PsGtEFYEQIhZ+93jSB2PlzMhdgRCAZXxq4muMD7NO42I/yYXyILLqImF/tED4gfId4FZk HlBIM3Tm0EmfAwiDn4dM6Cn1dGZyB9b5cpgDf/bBqbOE3cB5D4AXiOioA/5Mjow0gSW+VR2dS olCpEylAv5QkSPA2vBgDcR2Q/chHOOAE6VYMDVpX07epxZLo24+uZ65mfHfU7vkNJh9a/aQzr gIHyNo0rDcPiQlY5jMX2Xn5Q1uXxH+RaUG0jHBkeeIsGJ+syqMutNyoqYCrWW/zQIch4T8aTZ ikjnpPAHv/f04ryf8WjPXcj3k5POk4NKMg0JoY6F7FcDT7ZFz5LzPKECYCxhFMc+SFXVLbuI+ 9cqxFvLk7IK7P+Rjc/jxrcrx+FbHWlOpwaq3uTbLWZhEs17uZnp6x+WBoR5UYH/hfMB1MLNuv II0olbFHVSokZeS/p4aaYjo61aITDlyl+GpAYRW2AYnwYW6xCaUTiNEhopIJPWrr5MveX7MSt 59aDJat/8GlE3e0Y Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 30 March 2016 08:52:40 Viresh Kumar wrote: > On 29-03-16, 21:45, Arnd Bergmann wrote: > > Regarding new platforms, I'd hope that we could manage to define an extension > > to the oppv2 binding that marks a machine as compatible with opp, so we can > > The extension of oppv2 binding or compatible string is for platforms that really > need extend oppv2 (like ST, which already have a new compatible string). I am > not sure if we should be putting that into the Machine's compatible area, as I > though it is something internal to OPP layer or their driver. > > But we can see that when we handle it. > I think it should be something in the /cpus or the /opp_table hierarchy, not the root of the device tree, but other than that I don't care much whether it's a variation of the oppv2 compatible string or an additional property in any of the nodes. Arnd