From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752094AbdB0LWq (ORCPT ); Mon, 27 Feb 2017 06:22:46 -0500 Received: from mail-pf0-f180.google.com ([209.85.192.180]:36542 "EHLO mail-pf0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751778AbdB0LWf (ORCPT ); Mon, 27 Feb 2017 06:22:35 -0500 Date: Mon, 27 Feb 2017 16:25:33 +0530 From: Viresh Kumar To: Mark Rutland Cc: Masahiro Yamada , Rob Herring , linux-pm@vger.kernel.org, devicetree@vger.kernel.org, masahiroy@kernel.org, linux-arm-kernel , Linux Kernel Mailing List Subject: Re: Recommended notation for OPP to avoid DTC warnings Message-ID: <20170227105533.GA19417@vireshk-i7> References: <20170227104445.GE6795@leverpostej> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170227104445.GE6795@leverpostej> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 27-02-17, 10:44, Mark Rutland wrote: > On Sun, Feb 26, 2017 at 02:18:03PM +0900, Masahiro Yamada wrote: > > 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; > > }; > > > 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 "@" ? > > I think just s/@/-/ should be fine, e.g. call the above opp-1000000000. That's fine with me. I can send a patch to fix all existing users if we all agree for it. -- viresh