[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20161018.141437.2029098820682032692.davem@davemloft.net>
Date: Tue, 18 Oct 2016 14:14:37 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: robert.jarzmik@...e.fr
Cc: robh+dt@...nel.org, mark.rutland@....com, daniel@...que.org,
haojian.zhuang@...il.com, jic23@....ac.uk, dhowells@...hat.com,
nico@...xnic.net, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-am33-list@...hat.com
Subject: Re: [PATCH v3 0/4] support smc91x on mainstone and devicetree
From: Robert Jarzmik <robert.jarzmik@...e.fr>
Date: Mon, 17 Oct 2016 21:45:28 +0200
> This serie aims at bringing support to mainstone board on a device-tree based
> build, as what is already in place for legacy mainstone.
>
> The bulk of the mainstone "specific" behavior is that a u16 write doesn't work
> on a address of the form 4*n + 2, while it works on 4*n.
>
> The legacy workaround was in SMC_outw(), with calls to
> machine_is_mainstone(). These calls don't work with a pxa27x-dt machine type,
> which is used when a generic device-tree pxa27x machine is used to boot the
> mainstone board.
>
> Therefore, this serie enables the smc91c111 adapter of the mainstone board to
> work on a device-tree build, exaclty as it's been working for years with the
> legacy arch/arm/mach-pxa/mainstone.c definition.
>
> As a sum up, this extends an existing mechanism to device-tree based pxa platforms.
Series applied, thanks.
Powered by blists - more mailing lists