[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <515E97AE.4080608@openwrt.org>
Date: Fri, 05 Apr 2013 11:21:50 +0200
From: Florian Fainelli <florian@...nwrt.org>
To: Simon Baatz <gmbnomis@...il.com>
CC: davem@...emloft.net, thomas.petazzoni@...e-electrons.com,
moinejf@...e.fr, jason@...edaemon.net, andrew@...n.ch,
netdev@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
rob.herring@...xeda.com, grant.likely@...retlab.ca,
jogo@...nwrt.org, buytenh@...tstofly.org, jm@...tin.co.uk,
linux-arm-kernel@...ts.infradead.org,
sebastian.hesselbarth@...il.com
Subject: Re: [PATCH 3/5 v2] ARM: kirkwood: add device node entries for the
gigabit interfaces
Le 04/04/13 23:35, Simon Baatz a écrit :
> Hi Florian,
>
> On Thu, Apr 04, 2013 at 12:27:13PM +0200, Florian Fainelli wrote:
>> This patch modifies kirkwood.dtsi to specify the various gigabit
>> interfaces nodes available on kirkwood devices. They are disabled by
>> default and should be enabled on a per-board basis. egiga0 and egiga1
>> aliases are defined for convenience. The mdio node is also present and
>> should be enabled on a per-board basis as well.
>>
>> Signed-off-by: Florian Fainelli <florian@...nwrt.org>
>> ---
>> Changes since v1:
>> - dropped change to arch/arm/mach-kirkwood/common.c to avoid merge conflicts
>
> I think we should remove the clock aliases in
> kirkwood_legacy_clk_init() in mach-kirkwood/dt-board.c (once we have
> proper clock support, see my other mail).
>
[snip]
>
> Don't we need to add:
>
> interrupts = <46>;
>
> here?
Right this is missing, in fact it still works ok because the orion-mdio
driver can do busy waiting instead of interrupt signaling. Will fix that
in the next round, thanks!
--
Florian
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists