From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751845AbbLJB0A (ORCPT ); Wed, 9 Dec 2015 20:26:00 -0500 Received: from mailout1.w1.samsung.com ([210.118.77.11]:24159 "EHLO mailout1.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750910AbbLJBZ6 (ORCPT ); Wed, 9 Dec 2015 20:25:58 -0500 X-AuditID: cbfec7f5-f79b16d000005389-fc-5668d4a27af7 Subject: Re: [PATCH v2 02/19] PM / devfreq: exynos: Add documentation for generic exynos bus frequency driver To: Chanwoo Choi , myungjoo.ham@samsung.com, kgene@kernel.org References: <1449634091-1842-1-git-send-email-cw00.choi@samsung.com> <1449634091-1842-3-git-send-email-cw00.choi@samsung.com> <5668C9BE.7050900@samsung.com> <5668CC37.1090300@samsung.com> Cc: kyungmin.park@samsung.com, robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, linux@arm.linux.org.uk, tjakobi@math.uni-bielefeld.de, linux.amoon@gmail.com, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org From: Krzysztof Kozlowski Message-id: <5668D49C.80809@samsung.com> Date: Thu, 10 Dec 2015 10:25:48 +0900 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-version: 1.0 In-reply-to: <5668CC37.1090300@samsung.com> Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprLIsWRmVeSWpSXmKPExsVy+t/xy7qLrmSEGZx7Y2px/ctzVov5R86x WvS/Wchqce7VSkaL1y8MLfofv2a2ONv0ht3i8q45bBafe48wWsw4v4/JYt3GW+wWty/zWiy9 fpHJ4nbjCjaLCdPXsli07j3CbtG2+gOrg6DHmnlrGD1amnvYPC739TJ57Jx1l91j5fIvbB6b VnWyefw7xu7Rt2UVo8fnTXIBnFFcNimpOZllqUX6dglcGV/mvGEvuMhWsbF1KlsD4yzWLkZO DgkBE4kr97pZIGwxiQv31rN1MXJxCAksZZRY/3oTI4TzlFGivecBI0iVsEC+xLRtH5lBbBGB MInZM34wQxTtZ5SYdGAJmMMscJdJ4uL7J2wgVWwCxhKbly8Bs3kFNCR2PtkNtptFQFXiaOMn 9i5GDg5RgQiJRTsyIUoEJX5MvscCEuYU0JZY8poLxGQWUJeYMiUXpIJZQF5i85q3zBMYBWYh aZiFUDULSdUCRuZVjKKppckFxUnpuUZ6xYm5xaV56XrJ+bmbGCGR9nUH49JjVocYBTgYlXh4 K5zSw4RYE8uKK3MPMUpwMCuJ8OpfzggT4k1JrKxKLcqPLyrNSS0+xCjNwaIkzjtz1/sQIYH0 xJLU7NTUgtQimCwTB6dUA+Okwh9blkhcndC9UFhoAve+7zc0ZlxQVksr8l/37o3EOt3M3Re7 J05m+3VALXZW/O4/M1quqzW/D5x0uEuoqW2Cy0/DS9W2f1adntCkUH5df+tjP1tuy6rUeLXm 7NxJG9QfrltiWb3oj7vuk9SpDa4HqrvecyYvyDiWx8Lec/h284fn3yfJFIkosRRnJBpqMRcV JwIAM6k1WLACAAA= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10.12.2015 09:49, Chanwoo Choi wrote: > Hi, > (...) >> >>> + >>> + bus_dmc: bus_dmc { >>> + compatible = "samsung,exynos-bus"; >>> + clocks = <&cmu_dmc CLK_DIV_DMC>; >>> + clock-names = "bus"; >>> + operating-points-v2 = <&bus_dmc_opp_table>; >>> + status = "disabled"; >>> + }; >>> + >>> + bus_dmc_opp_table: opp_table0 { >>> + compatible = "operating-points-v2"; >>> + opp-shared; >>> + >>> + opp00 { >> >> Maybe use convention with frequency, like: >> opp@50000000 >> This also used in opp.txt examples. > > In the Documentations/devicetree/bindings/opp/opp.txt, > the example uses the 'opp@0x'. I check the opp.txt of Linux 4.4-rc4. Yes, it was changed by Viresh in "PM / OPP: Rename OPP nodes as opp@". You can find the most actual bindings in linux-next. Best regards, Krzysztof