From: Andrew Lunn <andrew@lunn.ch>
To: kostap@marvell.com
Cc: tmn505@gmail.com, jaz@semihalf.com, gregory.clement@bootlin.com,
nadavh@marvell.com, robh+dt@kernel.org, stefanc@marvell.com,
mw@semihalf.com, bpeled@marvell.com,
linux-arm-kernel@lists.infradead.org,
sebastian.hesselbarth@gmail.com
Subject: Re: [PATCH v2 4/4] arm64: dts: add support for Marvell cn9130-crb platform
Date: Thu, 17 Dec 2020 16:43:00 +0100 [thread overview]
Message-ID: <20201217154300.GD2943708@lunn.ch> (raw)
In-Reply-To: <20201217075542.12472-5-kostap@marvell.com>
On Thu, Dec 17, 2020 at 09:55:42AM +0200, kostap@marvell.com wrote:
> From: Konstantin Porotchkin <kostap@marvell.com>
>
> The Marvell reference platform CN9130-CRB is a small form factor
> board in a metal case. The platform is based on CN9130 SoC with
> addition of 8 Gigabit ports SOHO Ethernet switch.
> The reference platform features the following:
> * Up to 4 CPU cores ARMv8 Cortex-A72 CPU
> * CPU core operating speed of up to 2.2GHz
> * DDR4 DIMM – 8GB 64bit+ECC @ 2400Mhz.
> * 1x eMMC 8GB device
> * 1x uSD card 4 bits port on CP
> * 1x 128MB SPI NOR flash memory
> * 1x USB 3.0 Host port (Type A)
> * 1x SATA Gen3 via M.2
> * 1x USB 3.0 via M.2
> * 1x SIM card slot
> * 1x 1G Ethernet port via RGMII
> * 1x 10G switch port over SFP+ connector
> * 8x 1G ports through 88E6393X switch via XFI
> * 1x 2.5G/1G/100M/10M port via HS_SGMII
> * 1x PCI Express (PCIe)x1 Gen 3.0
> * 1x PCI Express (PCIe)x4 Gen 3.0 via NVMe M.2
> * JTAG port
>
> The plaform supports two HW configurations - "A" and "B"
> CN9130-CRB-A
> * AP-MPP configuration: SDIO, UART
> * CP0 Serdes configuration:
> * Lane0-3: NVMe (PCIe x4)
> * Lane4: XFI
> * Lane5: HS_SGMII
>
> 2. CN9130-CRB-B
> * AP-MPP configuration: SDIO, UART
> * CP0-MPP configuration: RGMII, SDIO, I2C0, I2C1, SMI, XSMI
> * CP0 Serdes configuration:
> * Lane0: PCIe x1
> * Lane1: USB3_0 x1
> * Lane2: SATA x1
> * Lane3: USB3_1 x1
> * Lane4: XFI
> * Lane5: HS_SGMII
>
> Signed-off-by: Konstantin Porotchkin <kostap@marvell.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-12-17 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 7:55 [PATCH v2 0/4] DTS updates for Marvell Armada CN913x platforms kostap
2020-12-17 7:55 ` [PATCH v2 1/4] Documentation/bindings: phy: update references to cp11x kostap
2020-12-17 7:55 ` [PATCH v2 2/4] arch/arm64/boot/dts/marvell: fix NAND partitioning scheme kostap
2020-12-17 15:36 ` Andrew Lunn
2020-12-17 7:55 ` [PATCH v2 3/4] arm64: dts: cn913x: add device trees for topology B boards kostap
2020-12-17 15:41 ` Andrew Lunn
2020-12-20 7:32 ` [EXT] " Kostya Porotchkin
2020-12-20 16:34 ` Andrew Lunn
2020-12-21 6:57 ` Kostya Porotchkin
2020-12-21 13:58 ` Andrew Lunn
2020-12-21 15:55 ` Kostya Porotchkin
2020-12-17 7:55 ` [PATCH v2 4/4] arm64: dts: add support for Marvell cn9130-crb platform kostap
2020-12-17 15:43 ` Andrew Lunn [this message]
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=20201217154300.GD2943708@lunn.ch \
--to=andrew@lunn.ch \
--cc=bpeled@marvell.com \
--cc=gregory.clement@bootlin.com \
--cc=jaz@semihalf.com \
--cc=kostap@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=stefanc@marvell.com \
--cc=tmn505@gmail.com \
/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).