From mboxrd@z Thu Jan 1 00:00:00 1970 From: robert.jarzmik@free.fr (Robert Jarzmik) Date: Tue, 21 Feb 2017 23:26:47 +0100 Subject: [PATCH 0/4] ARM64: Initial Marvell IAP140 enablement In-Reply-To: ("Andreas \=\?utf-8\?Q\?F\=C3\=A4rber\=22's\?\= message of "Tue, 21 Feb 2017 19:26:40 +0100") References: <20170219032000.4674-1-afaerber@suse.de> <87bmtxatmt.fsf@free-electrons.com> Message-ID: <8737f7yyc8.fsf@belgarion.home> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Andreas F?rber writes: > 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. ...zip... > 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. I agree here. PXA for me are XScale micro-architecture based SoCs, quite old. PXA1908 has a quite recent Cortex-A53 (or several of them), which makes me think its either an MMP or something newer than MMP. > 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. Yes please. Cheers. -- Robert From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Jarzmik Subject: Re: [PATCH 0/4] ARM64: Initial Marvell IAP140 enablement Date: Tue, 21 Feb 2017 23:26:47 +0100 Message-ID: <8737f7yyc8.fsf@belgarion.home> References: <20170219032000.4674-1-afaerber@suse.de> <87bmtxatmt.fsf@free-electrons.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: ("Andreas \=\?utf-8\?Q\?F\=C3\=A4rber\=22's\?\= message of "Tue, 21 Feb 2017 19:26:40 +0100") Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Andreas =?utf-8?Q?F=C3=A4rber?= Cc: Gregory CLEMENT , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Jason Cooper , Andrew Lunn , Sebastian Hesselbarth , Jisheng Zhang , Daniel Mack , Haojian Zhuang , Eric Miao , info-PWLG29+z7hGxBmiGZ5/UTQ@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Thomas Petazzoni List-Id: devicetree@vger.kernel.org Andreas Färber writes: > 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. ...zip... > 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. I agree here. PXA for me are XScale micro-architecture based SoCs, quite old. PXA1908 has a quite recent Cortex-A53 (or several of them), which makes me think its either an MMP or something newer than MMP. > 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. Yes please. Cheers. -- Robert -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752884AbdBUW07 convert rfc822-to-8bit (ORCPT ); Tue, 21 Feb 2017 17:26:59 -0500 Received: from smtp07.smtpout.orange.fr ([80.12.242.129]:18637 "EHLO smtp.smtpout.orange.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751334AbdBUW04 (ORCPT ); Tue, 21 Feb 2017 17:26:56 -0500 X-ME-Helo: belgarion X-ME-Auth: amFyem1pay5yb2JlcnRAb3JhbmdlLmZy X-ME-Date: Tue, 21 Feb 2017 23:26:53 +0100 X-ME-IP: 92.149.57.213 From: Robert Jarzmik To: Andreas =?utf-8?Q?F=C3=A4rber?= Cc: Gregory CLEMENT , linux-arm-kernel@lists.infradead.org, Jason Cooper , Andrew Lunn , Sebastian Hesselbarth , Jisheng Zhang , Daniel Mack , Haojian Zhuang , Eric Miao , info@andromedabox.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Thomas Petazzoni Subject: Re: [PATCH 0/4] ARM64: Initial Marvell IAP140 enablement References: <20170219032000.4674-1-afaerber@suse.de> <87bmtxatmt.fsf@free-electrons.com> X-URL: http://belgarath.falguerolles.org/ Date: Tue, 21 Feb 2017 23:26:47 +0100 In-Reply-To: ("Andreas \=\?utf-8\?Q\?F\=C3\=A4rber\=22's\?\= message of "Tue, 21 Feb 2017 19:26:40 +0100") Message-ID: <8737f7yyc8.fsf@belgarion.home> User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.4 (gnu/linux) MIME-Version: 1.0 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 Andreas Färber writes: > 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. ...zip... > 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. I agree here. PXA for me are XScale micro-architecture based SoCs, quite old. PXA1908 has a quite recent Cortex-A53 (or several of them), which makes me think its either an MMP or something newer than MMP. > 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. Yes please. Cheers. -- Robert