From mboxrd@z Thu Jan 1 00:00:00 1970 From: Masahiro Yamada Subject: Recommended notation for OPP to avoid DTC warnings Date: Sun, 26 Feb 2017 14:18:03 +0900 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Viresh Kumar , Rob Herring , linux-pm@vger.kernel.org, devicetree@vger.kernel.org, Mark Rutland Cc: masahiroy@kernel.org, Linux Kernel Mailing List , linux-arm-kernel List-Id: devicetree@vger.kernel.org Hi. Decumentation/devicetree/bindings/opp/opp.txt takes examples like this: opp@1000000000 { opp-hz = /bits/ 64 <1000000000>; opp-microvolt = <970000 975000 985000>; opp-microamp = <70000>; clock-latency-ns = <300000>; opp-suspend; }; opp@1100000000 { opp-hz = /bits/ 64 <1100000000>; opp-microvolt = <980000 1000000 1010000>; opp-microamp = <80000>; clock-latency-ns = <310000>; }; opp@1200000000 { opp-hz = /bits/ 64 <1200000000>; opp-microvolt = <1025000>; clock-latency-ns = <290000>; turbo-mode; }; If we follow this notation and the device-tree is built with W=1, DTC warns like follows: Warning (unit_address_vs_reg): Node /opp_table0/opp@1000000000 has a unit name, but no reg property Is there a recommended notation to avoid it? Maybe, simply omit the "@" ? -- Best Regards Masahiro Yamada