From: afaerber@suse.de (Andreas Färber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM64: Initial Marvell IAP140 enablement
Date: Tue, 21 Feb 2017 19:26:40 +0100 [thread overview]
Message-ID: <a8a1279c-4978-f612-e4cd-57b8645f3e79@suse.de> (raw)
In-Reply-To: <87bmtxatmt.fsf@free-electrons.com>
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.
> 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)
next prev parent reply other threads:[~2017-02-21 18:26 UTC|newest]
Thread overview: 14+ 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 ` [PATCH 1/4] ARM64: Prepare Marvell IAP140 aka PXA1908 Andreas Färber
2017-03-14 16:30 ` Ulf Hansson
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-20 12:56 ` Thomas Petazzoni
2017-02-20 13:16 ` Andreas Färber
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:20 ` [PATCH 4/4] ARM64: dts: marvell: iap140-andromeda-box-edge: Add uart0 clock Andreas Färber
2017-02-20 13:17 ` [PATCH 0/4] ARM64: Initial Marvell IAP140 enablement Gregory CLEMENT
2017-02-21 18:26 ` Andreas Färber [this message]
2017-02-21 19:19 ` Andrew Lunn
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=a8a1279c-4978-f612-e4cd-57b8645f3e79@suse.de \
--to=afaerber@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).