From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] Documentation: devicetree: arm: Document Marvell IAP140
Date: Mon, 20 Feb 2017 14:58:25 +0100 [thread overview]
Message-ID: <20170220145825.5f7cbe74@free-electrons.com> (raw)
In-Reply-To: <cac4ed13-5952-cccc-fee7-d9c29e77d8bb@suse.de>
Hello,
On Mon, 20 Feb 2017 14:16:13 +0100, Andreas F?rber wrote:
> I'm confused now. According to Marvell IR [0] they are NASDAQ-listed as
> MRVL. My understanding is that in that case the official vendor prefix
> becomes mrvl. Why not here?
Not sure why, but as of today, we have a mix of "mrvl" and "marvell" in
the tree, and "marvell" is the one official listed in
vendor-prefixes.txt.
> Any comments on the iap140 vs. pxa1908 naming? The Communication
> Processors section has disappeared from marvell.com, so I couldn't
> verify whether IAP140 was renamed from PXA1908 or whether both coexist
> and we should add a second compatible string here?
I don't have an opinion on this because I'm not familiar with this
family of Marvell SoCs. However, the only thing I would recommend is
that you send a patch to update Documentation/arm/Marvell/README to
document this PXA1908/IAP140 thing. This is particularly important
since this document mentions PXA1908 already.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: "Andreas Färber" <afaerber-l3A5Bk7waGM@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Jisheng Zhang <jszhang-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>,
Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
Eric Miao <eric.y.miao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
info-PWLG29+z7hGxBmiGZ5/UTQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Haojian Zhuang
<haojian.zhuang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Gregory Clement
<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Robert Jarzmik <robert.jarzmik-GANU6spQydw@public.gmane.org>,
Daniel Mack <daniel-cYrQPVfZoowdnm+yROfE0A@public.gmane.org>,
Sebastian Hesselbarth
<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 2/4] Documentation: devicetree: arm: Document Marvell IAP140
Date: Mon, 20 Feb 2017 14:58:25 +0100 [thread overview]
Message-ID: <20170220145825.5f7cbe74@free-electrons.com> (raw)
In-Reply-To: <cac4ed13-5952-cccc-fee7-d9c29e77d8bb-l3A5Bk7waGM@public.gmane.org>
Hello,
On Mon, 20 Feb 2017 14:16:13 +0100, Andreas Färber wrote:
> I'm confused now. According to Marvell IR [0] they are NASDAQ-listed as
> MRVL. My understanding is that in that case the official vendor prefix
> becomes mrvl. Why not here?
Not sure why, but as of today, we have a mix of "mrvl" and "marvell" in
the tree, and "marvell" is the one official listed in
vendor-prefixes.txt.
> Any comments on the iap140 vs. pxa1908 naming? The Communication
> Processors section has disappeared from marvell.com, so I couldn't
> verify whether IAP140 was renamed from PXA1908 or whether both coexist
> and we should add a second compatible string here?
I don't have an opinion on this because I'm not familiar with this
family of Marvell SoCs. However, the only thing I would recommend is
that you send a patch to update Documentation/arm/Marvell/README to
document this PXA1908/IAP140 thing. This is particularly important
since this document mentions PXA1908 already.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
--
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: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: linux-arm-kernel@lists.infradead.org,
Jisheng Zhang <jszhang@marvell.com>, Andrew Lunn <andrew@lunn.ch>,
Eric Miao <eric.y.miao@gmail.com>,
Jason Cooper <jason@lakedaemon.net>,
info@andromedabox.org, linux-kernel@vger.kernel.org,
Haojian Zhuang <haojian.zhuang@gmail.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Gregory Clement <gregory.clement@free-electrons.com>,
Mark Rutland <mark.rutland@arm.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Daniel Mack <daniel@zonque.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 2/4] Documentation: devicetree: arm: Document Marvell IAP140
Date: Mon, 20 Feb 2017 14:58:25 +0100 [thread overview]
Message-ID: <20170220145825.5f7cbe74@free-electrons.com> (raw)
In-Reply-To: <cac4ed13-5952-cccc-fee7-d9c29e77d8bb@suse.de>
Hello,
On Mon, 20 Feb 2017 14:16:13 +0100, Andreas Färber wrote:
> I'm confused now. According to Marvell IR [0] they are NASDAQ-listed as
> MRVL. My understanding is that in that case the official vendor prefix
> becomes mrvl. Why not here?
Not sure why, but as of today, we have a mix of "mrvl" and "marvell" in
the tree, and "marvell" is the one official listed in
vendor-prefixes.txt.
> Any comments on the iap140 vs. pxa1908 naming? The Communication
> Processors section has disappeared from marvell.com, so I couldn't
> verify whether IAP140 was renamed from PXA1908 or whether both coexist
> and we should add a second compatible string here?
I don't have an opinion on this because I'm not familiar with this
family of Marvell SoCs. However, the only thing I would recommend is
that you send a patch to update Documentation/arm/Marvell/README to
document this PXA1908/IAP140 thing. This is particularly important
since this document mentions PXA1908 already.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-20 13:58 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 [this message]
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
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=20170220145825.5f7cbe74@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.