[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <307da709-5dbd-845b-b7ec-d0c3d46ad2e6@gmail.com>
Date: Wed, 4 Jan 2017 09:30:07 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: linux-arm-kernel@...ts.infradead.org,
vivien.didelot@...oirfairelinux.com,
Jason Cooper <jason@...edaemon.net>,
Gregory Clement <gregory.clement@...e-electrons.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Russell King <linux@...linux.org.uk>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/8] ARM: dts: armada-370-rd: Utilize new DSA binding
On 01/03/2017 08:36 AM, Andrew Lunn wrote:
>> +
>> + switch: switch@10 {
>> + compatible = "marvell,mv88e6085";
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + reg = <16>;
>
> Hummm, a device tree question. switch@10, reg = <16>. Is there an
> implicit understanding that the 10 is hex?
Most (if not all?) unit addresses are hexadecimal, which is why this was
chosen here, but I really don't mind changing that.
--
Florian
Powered by blists - more mailing lists