Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755674AbcCXN7o (ORCPT ); Thu, 24 Mar 2016 09:59:44 -0400 Received: from outbound1a.ore.mailhop.org ([54.213.22.21]:29935 "EHLO outbound1a.ore.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752418AbcCXN7g (ORCPT ); Thu, 24 Mar 2016 09:59:36 -0400 X-MHO-User: ab163400-f1c8-11e5-b278-7d22021d92d7 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 108.39.34.67 X-Mail-Handler: DuoCircle Outbound SMTP X-DKIM: OpenDKIM Filter v2.6.8 io B90DD800E6 Date: Thu, 24 Mar 2016 13:59:31 +0000 From: Jason Cooper To: Andrew Lunn Cc: Thomas Petazzoni , Gregory CLEMENT , Andreas =?utf-8?Q?F=C3=A4rber?= , linux-arm-kernel@lists.infradead.org, Sebastian Hesselbarth , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Catalin Marinas , Will Deacon , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , open list Subject: Re: [PATCH 3/4] arm64: dts: marvell: Clean up armada-7040-db Message-ID: <20160324135931.GE26573@io.lakedaemon.net> References: <1458771861-12392-1-git-send-email-afaerber@suse.de> <1458771861-12392-4-git-send-email-afaerber@suse.de> <20160324091832.0060c907@free-electrons.com> <87oaa4npbk.fsf@free-electrons.com> <20160324114037.1204b46e@free-electrons.com> <20160324133723.GB15624@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160324133723.GB15624@lunn.ch> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 683 Lines: 20 On Thu, Mar 24, 2016 at 02:37:23PM +0100, Andrew Lunn wrote: > > > I agree that converting the Marvell Armada 32-bits SoCs would produce a > > > lot of churn. But if some binding are common there is no file at all are > > > in common, so we could use this solution for the 64 bits SoCs only. > > > > Yes, we could. I'm fine with it. I was merely pointing out that it is > > moving away from our 32 bits way of doing things. > > Sebastian spent a while converting dove and kirkwood to this > scheme. Most boards have i2c, nand, eth, and mdio properties > represented link this. > > There are no many 64 bit boards, so now is the time to make the > change... Agreed. thx, Jason.