linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: afaerber@suse.de (Andreas Färber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] Documentation: devicetree: arm: Document Marvell IAP140
Date: Mon, 20 Feb 2017 14:16:13 +0100	[thread overview]
Message-ID: <cac4ed13-5952-cccc-fee7-d9c29e77d8bb@suse.de> (raw)
In-Reply-To: <20170220135646.2b0219c1@free-electrons.com>

Hi,

Am 20.02.2017 um 13:56 schrieb Thomas Petazzoni:
> On Sun, 19 Feb 2017 04:19:58 +0100, Andreas F?rber wrote:
> 
>> + - compatible :  must contain "mrvl,iap140"
> 
> Even though there's indeed a good number of existing "mrvl," compatible
> strings in the tree, the official vendor prefix according to
> Documentation/devicetree/bindings/vendor-prefixes.txt is "marvell".
> Probably you should use that instead for new bindings?

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? Would be good to understand for other
pending vendors such as Actions Semi.

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?

Thanks,
Andreas

[0] http://investor.marvell.com/phoenix.zhtml?c=120802&p=irol-irhome

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)

  reply	other threads:[~2017-02-20 13:16 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 [this message]
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
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=cac4ed13-5952-cccc-fee7-d9c29e77d8bb@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).