[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7308700.atIMKyMFZU@wuerfel>
Date: Mon, 22 Aug 2016 13:55:22 +0200
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
linux-amlogic@...ts.infradead.org, khilman@...libre.com,
carlo@...one.org, mturquette@...libre.com, peppe.cavallaro@...com,
alexandre.torgue@...com, mark.rutland@....com,
devicetree@...r.kernel.org, catalin.marinas@....com,
will.deacon@....com, robh+dt@...nel.org, netdev@...r.kernel.org,
sboyd@...eaurora.org
Subject: Re: [PATCH v2 1/4] net: dt-bindings: Document the new Meson8b and GXBB DWMAC bindings
On Saturday, August 20, 2016 11:35:35 AM CEST Martin Blumenstingl wrote:
> +- reg: The first register range should be the one of the DWMAC
> + controller. The second range is is for the Amlogic specific
> + configuration (for example the PRG_ETHERNET register range
> + on Meson8b and newer)
>
...
> +Example for GXBB:
> + ethmac: ethernet@...10000 {
> + compatible = "amlogic,meson-gxbb-dwmac", "snps,dwmac";
> + reg = <0x0 0xc9410000 0x0 0x10000>,
> + <0x0 0xc8834540 0x0 0x8>;
>
The address "0xc8834540" suggests that this is part of a larger register
range that is used for various things, i.e. a "syscon" type of device.
How about making this a syscon reference rather than a "reg" address?
Arnd
Powered by blists - more mailing lists