All of lore.kernel.org
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM64: Initial Marvell IAP140 enablement
Date: Tue, 21 Feb 2017 23:26:47 +0100	[thread overview]
Message-ID: <8737f7yyc8.fsf@belgarion.home> (raw)
In-Reply-To: <a8a1279c-4978-f612-e4cd-57b8645f3e79@suse.de> ("Andreas \=\?utf-8\?Q\?F\=C3\=A4rber\=22's\?\= message of "Tue, 21 Feb 2017 19:26:40 +0100")

Andreas F?rber <afaerber@suse.de> writes:

> Hi Gregory,
>
> Am 20.02.2017 um 14:17 schrieb Gregory CLEMENT:
>>  On dim., f?vr. 19 2017, Andreas F?rber <afaerber@suse.de> 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

WARNING: multiple messages have this Message-ID (diff)
From: Robert Jarzmik <robert.jarzmik-GANU6spQydw@public.gmane.org>
To: "Andreas Färber" <afaerber-l3A5Bk7waGM@public.gmane.org>
Cc: Gregory CLEMENT
	<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
	Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
	Sebastian Hesselbarth
	<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Jisheng Zhang <jszhang-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>,
	Daniel Mack <daniel-cYrQPVfZoowdnm+yROfE0A@public.gmane.org>,
	Haojian Zhuang
	<haojian.zhuang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Eric Miao <eric.y.miao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	info-PWLG29+z7hGxBmiGZ5/UTQ@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Thomas Petazzoni
	<thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Subject: Re: [PATCH 0/4] ARM64: Initial Marvell IAP140 enablement
Date: Tue, 21 Feb 2017 23:26:47 +0100	[thread overview]
Message-ID: <8737f7yyc8.fsf@belgarion.home> (raw)
In-Reply-To: <a8a1279c-4978-f612-e4cd-57b8645f3e79-l3A5Bk7waGM@public.gmane.org> ("Andreas \=\?utf-8\?Q\?F\=C3\=A4rber\=22's\?\= message of "Tue, 21 Feb 2017 19:26:40 +0100")

Andreas Färber <afaerber-l3A5Bk7waGM@public.gmane.org> writes:

> Hi Gregory,
>
> Am 20.02.2017 um 14:17 schrieb Gregory CLEMENT:
>>  On dim., févr. 19 2017, Andreas Färber <afaerber-l3A5Bk7waGM@public.gmane.org> 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

WARNING: multiple messages have this Message-ID (diff)
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Gregory CLEMENT <gregory.clement@free-electrons.com>,
	linux-arm-kernel@lists.infradead.org,
	Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Jisheng Zhang <jszhang@marvell.com>,
	Daniel Mack <daniel@zonque.org>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Eric Miao <eric.y.miao@gmail.com>,
	info@andromedabox.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Subject: Re: [PATCH 0/4] ARM64: Initial Marvell IAP140 enablement
Date: Tue, 21 Feb 2017 23:26:47 +0100	[thread overview]
Message-ID: <8737f7yyc8.fsf@belgarion.home> (raw)
In-Reply-To: <a8a1279c-4978-f612-e4cd-57b8645f3e79@suse.de> ("Andreas \=\?utf-8\?Q\?F\=C3\=A4rber\=22's\?\= message of "Tue, 21 Feb 2017 19:26:40 +0100")

Andreas Färber <afaerber@suse.de> writes:

> Hi Gregory,
>
> Am 20.02.2017 um 14:17 schrieb Gregory CLEMENT:
>>  On dim., févr. 19 2017, Andreas Färber <afaerber@suse.de> 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

  parent reply	other threads:[~2017-02-21 22:26 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-19  3:19 [PATCH 0/4] ARM64: Initial Marvell IAP140 enablement Andreas Färber
2017-02-19  3:19 ` Andreas Färber
2017-02-19  3:19 ` Andreas Färber
2017-02-19  3:19 ` [PATCH 1/4] ARM64: Prepare Marvell IAP140 aka PXA1908 Andreas Färber
2017-02-19  3:19   ` Andreas Färber
2017-02-19  3:19   ` Andreas Färber
2017-03-14 16:30   ` Ulf Hansson
2017-03-14 16:30     ` Ulf Hansson
2017-03-14 16:30     ` Ulf Hansson
2017-03-14 16:30     ` Ulf Hansson
2017-03-14 18:10     ` Andreas Färber
2017-03-14 18:10       ` Andreas Färber
2017-03-14 18:10       ` Andreas Färber
2017-02-19  3:19 ` [PATCH 2/4] Documentation: devicetree: arm: Document Marvell IAP140 Andreas Färber
2017-02-19  3:19   ` Andreas Färber
2017-02-19  3:19   ` Andreas Färber
2017-02-20 12:56   ` Thomas Petazzoni
2017-02-20 12:56     ` Thomas Petazzoni
2017-02-20 12:56     ` Thomas Petazzoni
2017-02-20 13:16     ` Andreas Färber
2017-02-20 13:16       ` Andreas Färber
2017-02-20 13:16       ` Andreas Färber
2017-02-20 13:58       ` Thomas Petazzoni
2017-02-20 13:58         ` Thomas Petazzoni
2017-02-20 13:58         ` Thomas Petazzoni
2017-02-19  3:19 ` [PATCH 3/4] ARM64: dts: marvell: Add IAP140 and Andromeda Box Edge Andreas Färber
2017-02-19  3:19   ` Andreas Färber
2017-02-19  3:20 ` [PATCH 4/4] ARM64: dts: marvell: iap140-andromeda-box-edge: Add uart0 clock Andreas Färber
2017-02-19  3:20   ` Andreas Färber
2017-02-19  3:20   ` Andreas Färber
2017-02-20 13:17 ` [PATCH 0/4] ARM64: Initial Marvell IAP140 enablement Gregory CLEMENT
2017-02-20 13:17   ` Gregory CLEMENT
2017-02-20 13:17   ` Gregory CLEMENT
2017-02-21 18:26   ` Andreas Färber
2017-02-21 18:26     ` Andreas Färber
2017-02-21 18:26     ` Andreas Färber
2017-02-21 19:19     ` Andrew Lunn
2017-02-21 19:19       ` Andrew Lunn
2017-02-21 19:19       ` Andrew Lunn
2017-02-21 22:26     ` Robert Jarzmik [this message]
2017-02-21 22:26       ` Robert Jarzmik
2017-02-21 22:26       ` Robert Jarzmik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737f7yyc8.fsf@belgarion.home \
    --to=robert.jarzmik@free.fr \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.