[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56F56911.6020603@cogentembedded.com>
Date: Fri, 25 Mar 2016 19:36:33 +0300
From: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To: Rob Herring <robh+dt@...nel.org>
Cc: David Lechner <david@...hnology.com>,
Petr Kulhavy <petr@...ix.com>, David.Laight@...lab.com,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Russell King <linux@....linux.org.uk>,
Sekhar Nori <nsekhar@...com>,
Kevin Hilman <khilman@...nel.org>,
Kishon Vijay Abraham I <kishon@...com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alan Stern <stern@...land.harvard.edu>, Bin Liu <b-liu@...com>,
Lee Jones <lee.jones@...aro.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
"moderated list:ARM PORT" <linux-arm-kernel@...ts.infradead.org>,
"open list:USB SUBSYSTEM" <linux-usb@...r.kernel.org>
Subject: Re: [PATCH v3 01/16] dt: davinci: use proper address after @
Hello.
On 03/25/2016 06:13 PM, Rob Herring wrote:
>>> TI has been using the physical address in DT after the @ in device nodes.
>>> The device tree convention is to use the same address that is used for
>>> the reg property. This updates all davinci DT files to use the proper
>>> convention.
>>>
>>> Signed-off-by: David Lechner <david@...hnology.com>
>>
>> [...]
>>
>>> diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi
>>> index 226cda7..4294849 100644
>>> --- a/arch/arm/boot/dts/da850.dtsi
>>> +++ b/arch/arm/boot/dts/da850.dtsi
>>> @@ -15,7 +15,7 @@
>>> #address-cells = <1>;
>>> #size-cells = <1>;
>>> ranges;
>>> - intc: interrupt-controller {
>>> + intc: interrupt-controller@...ee000 {
>>> compatible = "ti,cp-intc";
>>> interrupt-controller;
>>> #interrupt-cells = <1>;
>>> @@ -23,7 +23,7 @@
>>> reg = <0xfffee000 0x2000>;
>>> };
>>> };
>>> - soc {
>>> + soc@...0000 {
>>
>>
>> This node doesn't have the "reg" prop.
> But probably has a ranges property which is correct.
Yes, it does. Didn't know that "ranges" can be used that way, thanks...
> Rob
MBR, Sergei
Powered by blists - more mailing lists