[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <519A97B8.1090503@gmail.com>
Date: Mon, 20 May 2013 23:38:00 +0200
From: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
To: Simon Baatz <gmbnomis@...il.com>
CC: Grant Likely <grant.likely@...aro.org>,
David Miller <davem@...emloft.net>,
Florian Fainelli <florian@...nwrt.org>,
Russell King <linux@....linux.org.uk>,
Jason Cooper <jason@...edaemon.net>,
Andrew Lunn <andrew@...n.ch>, netdev@...r.kernel.org,
devicetree-discuss@...ts.ozlabs.org, linux-doc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 6/7] ARM: kirkwood: add gigabit ethernet and mvmdio
device tree nodes
On 05/20/2013 11:27 PM, Simon Baatz wrote:
> Hi Sebastian,
>
> On Mon, May 06, 2013 at 05:33:39PM +0200, Sebastian Hesselbarth wrote:
>> This patch adds mv643xx_eth and mvmdio device tree nodes for DT enabled
>> Kirkwood boards. Phy nodes are also added with reg property set on a
>> per-board basis.
> ...
>> diff --git a/arch/arm/boot/dts/kirkwood.dtsi b/arch/arm/boot/dts/kirkwood.dtsi
>> index fada7e6..c01a273 100644
>> --- a/arch/arm/boot/dts/kirkwood.dtsi
>> +++ b/arch/arm/boot/dts/kirkwood.dtsi
>> @@ -202,5 +202,57 @@
>> clocks =<&gate_clk 4>;
>> status = "disabled";
>> };
>> +
>> + mdio: mdio-bus@...04 {
>> + compatible = "marvell,orion-mdio";
>> + reg =<0x72004 0x84>;
>> + interrupts =<11>;
>
> Shouldn't this be 46?
Yes, mdio is using GbE0Err interrupt and that is 14 on IRQ HIGH CAUSE.
I was misled by 11 on IRQ LOW CAUSE.
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists