From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753331AbdBUS1I (ORCPT ); Tue, 21 Feb 2017 13:27:08 -0500 Received: from mx2.suse.de ([195.135.220.15]:60695 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754804AbdBUS0p (ORCPT ); Tue, 21 Feb 2017 13:26:45 -0500 Subject: Re: [PATCH 0/4] ARM64: Initial Marvell IAP140 enablement To: Gregory CLEMENT References: <20170219032000.4674-1-afaerber@suse.de> <87bmtxatmt.fsf@free-electrons.com> Cc: linux-arm-kernel@lists.infradead.org, Jason Cooper , Andrew Lunn , Sebastian Hesselbarth , Jisheng Zhang , Daniel Mack , Haojian Zhuang , Robert Jarzmik , Eric Miao , info@andromedabox.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Thomas Petazzoni From: =?UTF-8?Q?Andreas_F=c3=a4rber?= Organization: SUSE Linux GmbH Message-ID: Date: Tue, 21 Feb 2017 19:26:40 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <87bmtxatmt.fsf@free-electrons.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Gregory, Am 20.02.2017 um 14:17 schrieb Gregory CLEMENT: > On dim., févr. 19 2017, Andreas Färber wrote: > >> This mini-series adds initial support for the Marvell IAP140 SoC (aka PXA1908) >> and the Andromeda Box Edge development board. > > Given the name of the SoC (PXA1908) and the fact that you reuse driver > related to PXA, for me these SoC is neither a mvebu nor a berlin SoC. That matches my understanding. > So > just to avoid any misunderstanding, I don't mind being CC and possibly > doing review but I don't plan to take this patch ( I don't think the > berlin maintainer will do it too). Sure. There did not seem to be a MAINTAINERS-documented maintainer for dts/marvell/Makefile, so I CC'ed both MVEBU and Berlin for review, in addition to the unclear-to-me PXA vs. MMP separation. I was unsure about the sort order used: Is it that Berlin was first and therefore Berlin comes before Armada (then iap140 goes last), or is it sorted by ARCH_? Becomes relevant below. >> In order to enable the 8250 UART driver, it reuses ARCH_PXA; but some drivers >> enabled with ARCH_PXA don't build due to arm assembly or arm64's lack of mach-, >> so their dependencies need to be limited to ARM alongside (blacklisted). The >> alternative would of course be to choose a new ARCH_ symbol and to selectively >> add it to drivers known working (whitelisting). The latter would require >> finding a suitable name. > > For this kind of issue you can have a look on what we did when > introducing mvebu SoC using ARM64. This is how you introduced MVEBU for arm64: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b4f596b19624d14864596b5b43de5f04cadd4895 There was a discussion with Jisheng on whether to use ARCH_ARMADA_3700, but since I did not propose ARCH_IAP140 here, what are you suggesting exactly? Berlin does not sound like a BU name either. What I am reading out of the documentation Thomas pointed to is that ARCH_MMP would be more correct than ARCH_PXA, despite the PXA1908 name. MMP does help with driver compilation. Just for the OF earlycon I still need the PXA compatible fallback, or we would need to define an MMP earlycon. Since mmp2.dtsi does not use the pxa compatible, I'll look into the latter for v2. MMP sorts before MVEBU, unlike PXA. So MMP would mean Eric and Haojian only - I will drop the other Marvell maintainers for v2 then, except where review comments have been provided. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg)