From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1034291AbcJRSOl (ORCPT ); Tue, 18 Oct 2016 14:14:41 -0400 Received: from shards.monkeyblade.net ([184.105.139.130]:44966 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031213AbcJRSOk (ORCPT ); Tue, 18 Oct 2016 14:14:40 -0400 Date: Tue, 18 Oct 2016 14:14:37 -0400 (EDT) Message-Id: <20161018.141437.2029098820682032692.davem@davemloft.net> To: robert.jarzmik@free.fr Cc: robh+dt@kernel.org, mark.rutland@arm.com, daniel@zonque.org, haojian.zhuang@gmail.com, jic23@cam.ac.uk, dhowells@redhat.com, nico@fluxnic.net, netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-am33-list@redhat.com Subject: Re: [PATCH v3 0/4] support smc91x on mainstone and devicetree From: David Miller In-Reply-To: <1476733532-29716-1-git-send-email-robert.jarzmik@free.fr> References: <1476733532-29716-1-git-send-email-robert.jarzmik@free.fr> X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Tue, 18 Oct 2016 11:14:39 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Robert Jarzmik 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. From mboxrd@z Thu Jan 1 00:00:00 1970 From: davem@davemloft.net (David Miller) Date: Tue, 18 Oct 2016 14:14:37 -0400 (EDT) Subject: [PATCH v3 0/4] support smc91x on mainstone and devicetree In-Reply-To: <1476733532-29716-1-git-send-email-robert.jarzmik@free.fr> References: <1476733532-29716-1-git-send-email-robert.jarzmik@free.fr> Message-ID: <20161018.141437.2029098820682032692.davem@davemloft.net> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org From: Robert Jarzmik 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.