2015-08-25 11:18:38 +00:00
|
|
|
if ARCH_MVEBU
|
|
|
|
|
|
2016-05-17 13:00:30 +00:00
|
|
|
config ARMADA_32BIT
|
|
|
|
|
bool
|
|
|
|
|
select CPU_V7
|
|
|
|
|
select SUPPORT_SPL
|
|
|
|
|
select SPL_DM
|
|
|
|
|
select SPL_DM_SEQ_ALIAS
|
|
|
|
|
select SPL_OF_CONTROL
|
|
|
|
|
select SPL_SIMPLE_BUS
|
|
|
|
|
|
|
|
|
|
config ARMADA_64BIT
|
|
|
|
|
bool
|
|
|
|
|
select ARM64
|
|
|
|
|
|
|
|
|
|
# ARMv7 SoCs...
|
2016-01-29 08:14:54 +00:00
|
|
|
config ARMADA_375
|
|
|
|
|
bool
|
2016-05-17 13:00:30 +00:00
|
|
|
select ARMADA_32BIT
|
2016-01-29 08:14:54 +00:00
|
|
|
|
2015-12-21 12:56:33 +00:00
|
|
|
config ARMADA_38X
|
|
|
|
|
bool
|
2016-05-17 13:00:30 +00:00
|
|
|
select ARMADA_32BIT
|
2015-12-21 12:56:33 +00:00
|
|
|
|
|
|
|
|
config ARMADA_XP
|
|
|
|
|
bool
|
2016-05-17 13:00:30 +00:00
|
|
|
select ARMADA_32BIT
|
|
|
|
|
|
|
|
|
|
# ARMv8 SoCs...
|
|
|
|
|
config ARMADA_3700
|
|
|
|
|
bool
|
|
|
|
|
select ARM64
|
2015-12-21 12:56:33 +00:00
|
|
|
|
arm64: mvebu: Add basic support for the Marvell Armada 7K/8K SoC
Compared to the Armada 3700, the Armada 7K and 8K are much more on the
high-end side: they use a dual Cortex-A72 or a quad Cortex-A72, as
opposed to the Cortex-A53 for the Armada 3700.
The Armada 7K and 8K also use a fairly unique architecture, internally
they are composed of several components:
- One AP (Application Processor), which contains the processor itself
and a few core hardware blocks. The AP used in the Armada 7K and 8K
is called AP806, and is available in two configurations:
dual Cortex-A72 and quad Cortex-A72.
- One or two CP (Communication Processor), which contain most of the I/O
interfaces (SATA, PCIe, Ethernet, etc.). The 7K family chips have one
CP, while the 8K family chips integrate two CPs, providing two times
the number of I/O interfaces available in the CP.
The CP used in the 7K and 8K is called CP110.
All in all, this gives the following combinations:
- Armada 7020, which is a dual Cortex-A72 with one CP
- Armada 7040, which is a quad Cortex-A72 with one CP
- Armada 8020, which is a dual Cortex-A72 with two CPs
- Armada 8040, which is a quad Cortex-A72 with two CPs
This patch adds basic support for this ARMv8 based SoC into U-Boot.
Future patches will integrate other device drivers and board support,
starting with the Marvell DB-88F7040 development board.
Signed-off-by: Stefan Roese <sr@denx.de>
Cc: Nadav Haklai <nadavh@marvell.com>
Cc: Neta Zur Hershkovits <neta@marvell.com>
Cc: Kostya Porotchkin <kostap@marvell.com>
Cc: Omri Itach <omrii@marvell.com>
Cc: Igal Liberman <igall@marvell.com>
Cc: Haim Boot <hayim@marvell.com>
Cc: Hanna Hawa <hannah@marvell.com>
2016-05-25 06:13:45 +00:00
|
|
|
# Armada 7K and 8K are very similar - use only one Kconfig symbol for both
|
|
|
|
|
config ARMADA_8K
|
|
|
|
|
bool
|
|
|
|
|
select ARM64
|
|
|
|
|
|
2016-10-26 01:08:30 +00:00
|
|
|
# Armada PLL frequency (used for NAND clock generation)
|
|
|
|
|
config SYS_MVEBU_PLL_CLOCK
|
|
|
|
|
int
|
|
|
|
|
default "2000000000" if ARMADA_XP || ARMADA_3700 || ARMADA_8K
|
|
|
|
|
default "1000000000" if ARMADA_38X || ARMADA_375
|
|
|
|
|
|
2016-05-17 13:00:30 +00:00
|
|
|
# Armada XP/38x SoC types...
|
2015-12-25 13:41:22 +00:00
|
|
|
config MV78230
|
|
|
|
|
bool
|
|
|
|
|
select ARMADA_XP
|
|
|
|
|
|
|
|
|
|
config MV78260
|
|
|
|
|
bool
|
|
|
|
|
select ARMADA_XP
|
|
|
|
|
|
|
|
|
|
config MV78460
|
|
|
|
|
bool
|
|
|
|
|
select ARMADA_XP
|
|
|
|
|
|
2016-09-22 00:56:13 +00:00
|
|
|
config 88F6820
|
2015-12-25 13:41:22 +00:00
|
|
|
bool
|
|
|
|
|
select ARMADA_38X
|
|
|
|
|
|
2015-08-25 11:18:38 +00:00
|
|
|
choice
|
arm64: mvebu: Add basic support for the Marvell Armada 7K/8K SoC
Compared to the Armada 3700, the Armada 7K and 8K are much more on the
high-end side: they use a dual Cortex-A72 or a quad Cortex-A72, as
opposed to the Cortex-A53 for the Armada 3700.
The Armada 7K and 8K also use a fairly unique architecture, internally
they are composed of several components:
- One AP (Application Processor), which contains the processor itself
and a few core hardware blocks. The AP used in the Armada 7K and 8K
is called AP806, and is available in two configurations:
dual Cortex-A72 and quad Cortex-A72.
- One or two CP (Communication Processor), which contain most of the I/O
interfaces (SATA, PCIe, Ethernet, etc.). The 7K family chips have one
CP, while the 8K family chips integrate two CPs, providing two times
the number of I/O interfaces available in the CP.
The CP used in the 7K and 8K is called CP110.
All in all, this gives the following combinations:
- Armada 7020, which is a dual Cortex-A72 with one CP
- Armada 7040, which is a quad Cortex-A72 with one CP
- Armada 8020, which is a dual Cortex-A72 with two CPs
- Armada 8040, which is a quad Cortex-A72 with two CPs
This patch adds basic support for this ARMv8 based SoC into U-Boot.
Future patches will integrate other device drivers and board support,
starting with the Marvell DB-88F7040 development board.
Signed-off-by: Stefan Roese <sr@denx.de>
Cc: Nadav Haklai <nadavh@marvell.com>
Cc: Neta Zur Hershkovits <neta@marvell.com>
Cc: Kostya Porotchkin <kostap@marvell.com>
Cc: Omri Itach <omrii@marvell.com>
Cc: Igal Liberman <igall@marvell.com>
Cc: Haim Boot <hayim@marvell.com>
Cc: Hanna Hawa <hannah@marvell.com>
2016-05-25 06:13:45 +00:00
|
|
|
prompt "Armada XP/375/38x/3700/7K/8K board select"
|
2015-08-25 11:18:38 +00:00
|
|
|
optional
|
|
|
|
|
|
2015-10-20 13:14:47 +00:00
|
|
|
config TARGET_CLEARFOG
|
|
|
|
|
bool "Support ClearFog"
|
2016-09-22 00:56:13 +00:00
|
|
|
select 88F6820
|
2015-10-20 13:14:47 +00:00
|
|
|
|
2016-05-17 13:04:16 +00:00
|
|
|
config TARGET_MVEBU_DB_88F3720
|
|
|
|
|
bool "Support DB-88F3720 Armada 3720"
|
|
|
|
|
select ARMADA_3700
|
|
|
|
|
|
2016-01-29 08:14:54 +00:00
|
|
|
config TARGET_DB_88F6720
|
|
|
|
|
bool "Support DB-88F6720 Armada 375"
|
|
|
|
|
select ARMADA_375
|
|
|
|
|
|
2015-08-25 11:18:38 +00:00
|
|
|
config TARGET_DB_88F6820_GP
|
|
|
|
|
bool "Support DB-88F6820-GP"
|
2016-09-22 00:56:13 +00:00
|
|
|
select 88F6820
|
2015-08-25 11:18:38 +00:00
|
|
|
|
2016-09-22 00:56:14 +00:00
|
|
|
config TARGET_DB_88F6820_AMC
|
|
|
|
|
bool "Support DB-88F6820-AMC"
|
|
|
|
|
select 88F6820
|
|
|
|
|
|
2016-05-25 06:21:21 +00:00
|
|
|
config TARGET_MVEBU_DB_88F7040
|
|
|
|
|
bool "Support DB-88F7040 Armada 7040"
|
|
|
|
|
select ARMADA_8K
|
|
|
|
|
|
2015-08-25 11:18:38 +00:00
|
|
|
config TARGET_DB_MV784MP_GP
|
|
|
|
|
bool "Support db-mv784mp-gp"
|
2015-12-25 13:41:22 +00:00
|
|
|
select MV78460
|
2015-08-25 11:18:38 +00:00
|
|
|
|
mvebu: Support Synology DS414
This adds support for the MV78230 based DS414 NAS by Synology. The
relevant bits have been extracted from the 'synogpl-5004-armadaxp'
package Synology kindly published, garnished with a fair amount of
trial-and-error.
Sadly, support is far from perfect. The major parts I have failed in
are SATA and XHCI support. Details about these and some other things
follow:
Device Tree
-----------
The device tree file armada-xp-synology-ds414.dts has been copied from
Linux and enhanced by recent U-Boot specific changes to
armada-xp-gp.dts.
SATA Support
------------
There is a Marvell 88SX7042 controller attached to PCIe which is
supported by Linux's sata_mv driver but sadly not U-Boot's sata_mv.
I'm not sure if extending the latter to support PCI devices is worth the
effort at all. Porting sata_mv from Linux exceeded my brain's
capacities. :(
XHCI Support
------------
There is an EtronTech EJ168A XHCI controller attached to PCIe which
drives the two rear USB3 ports. After a bit of playing around I managed
to get it recognized by xhci-pci, but never was able to access any
devices attached to it. Enabling it in ds414 board config shows that it
does not respond to commands for whatever reason. The (somewhat) bright
side to it is that it is not even supported in Synology's customized
U-Boot, but that also means nowhere to steal the relevant bits from.
EHCI Support
------------
This seems functional after issuing 'usb start'. At least it detects USB
storage devices, and IIRC reading from them was OK. OTOH Linux fails to
register the controller if 'usb start' wasn't given before in U-Boot.
According to Synology sources, this board seems to support USB device
(gadget?) mode. Though I didn't play around with it.
PCIe Support
------------
This is fine, but trying to gate the clocks of unused lanes will hang
PCI enum. In addition to that, pci_mvebu seems not to support DM_PCI.
DDR3 Training
-------------
Marvell/Synology uses eight PUPs instead of four. Does not look like
this is meant to be customized in mainline U-Boot at all. OTOH I have
no idea what a "PUP" actually is.
PEX Init
--------
Synology uses different values than mainline U-Boot with this patch:
pex_max_unit_get returns 2, pex_max_if_get returns 7 and
max_serdes_lines is set to 7. Not changing this seems to not have an
impact, although I'm not entirely sure it does not cause issues I am not
aware of.
Static Environment
------------------
This allows to boot stock Synology firmware at least. In order to be a
little more flexible when it comes to booting custom kernels, do not
only load zImage partition, but also rd.gz into memory. This way it is
possible to use about 7MB for kernel with piggyback initramfs.
Signed-off-by: Phil Sutter <phil@nwl.cc>
Acked-by: Stefan Roese <sr@denx.de>
Reviewed-by: Tom Rini <trini@konsulko.com>
2015-12-25 13:41:25 +00:00
|
|
|
config TARGET_DS414
|
|
|
|
|
bool "Support Synology DS414"
|
|
|
|
|
select MV78230
|
|
|
|
|
|
2015-08-25 11:18:38 +00:00
|
|
|
config TARGET_MAXBCM
|
|
|
|
|
bool "Support maxbcm"
|
2015-12-25 13:41:22 +00:00
|
|
|
select MV78460
|
2015-08-25 11:18:38 +00:00
|
|
|
|
2016-01-20 07:13:29 +00:00
|
|
|
config TARGET_THEADORABLE
|
|
|
|
|
bool "Support theadorable Armada XP"
|
|
|
|
|
select MV78260
|
|
|
|
|
|
2015-08-25 11:18:38 +00:00
|
|
|
endchoice
|
|
|
|
|
|
2015-12-21 12:40:37 +00:00
|
|
|
config SYS_BOARD
|
|
|
|
|
default "clearfog" if TARGET_CLEARFOG
|
2016-05-17 13:04:16 +00:00
|
|
|
default "mvebu_db-88f3720" if TARGET_MVEBU_DB_88F3720
|
2016-01-29 08:14:54 +00:00
|
|
|
default "db-88f6720" if TARGET_DB_88F6720
|
2015-12-21 12:40:37 +00:00
|
|
|
default "db-88f6820-gp" if TARGET_DB_88F6820_GP
|
2016-09-22 00:56:14 +00:00
|
|
|
default "db-88f6820-amc" if TARGET_DB_88F6820_AMC
|
2016-05-25 06:21:21 +00:00
|
|
|
default "mvebu_db-88f7040" if TARGET_MVEBU_DB_88F7040
|
2015-12-21 12:40:37 +00:00
|
|
|
default "db-mv784mp-gp" if TARGET_DB_MV784MP_GP
|
mvebu: Support Synology DS414
This adds support for the MV78230 based DS414 NAS by Synology. The
relevant bits have been extracted from the 'synogpl-5004-armadaxp'
package Synology kindly published, garnished with a fair amount of
trial-and-error.
Sadly, support is far from perfect. The major parts I have failed in
are SATA and XHCI support. Details about these and some other things
follow:
Device Tree
-----------
The device tree file armada-xp-synology-ds414.dts has been copied from
Linux and enhanced by recent U-Boot specific changes to
armada-xp-gp.dts.
SATA Support
------------
There is a Marvell 88SX7042 controller attached to PCIe which is
supported by Linux's sata_mv driver but sadly not U-Boot's sata_mv.
I'm not sure if extending the latter to support PCI devices is worth the
effort at all. Porting sata_mv from Linux exceeded my brain's
capacities. :(
XHCI Support
------------
There is an EtronTech EJ168A XHCI controller attached to PCIe which
drives the two rear USB3 ports. After a bit of playing around I managed
to get it recognized by xhci-pci, but never was able to access any
devices attached to it. Enabling it in ds414 board config shows that it
does not respond to commands for whatever reason. The (somewhat) bright
side to it is that it is not even supported in Synology's customized
U-Boot, but that also means nowhere to steal the relevant bits from.
EHCI Support
------------
This seems functional after issuing 'usb start'. At least it detects USB
storage devices, and IIRC reading from them was OK. OTOH Linux fails to
register the controller if 'usb start' wasn't given before in U-Boot.
According to Synology sources, this board seems to support USB device
(gadget?) mode. Though I didn't play around with it.
PCIe Support
------------
This is fine, but trying to gate the clocks of unused lanes will hang
PCI enum. In addition to that, pci_mvebu seems not to support DM_PCI.
DDR3 Training
-------------
Marvell/Synology uses eight PUPs instead of four. Does not look like
this is meant to be customized in mainline U-Boot at all. OTOH I have
no idea what a "PUP" actually is.
PEX Init
--------
Synology uses different values than mainline U-Boot with this patch:
pex_max_unit_get returns 2, pex_max_if_get returns 7 and
max_serdes_lines is set to 7. Not changing this seems to not have an
impact, although I'm not entirely sure it does not cause issues I am not
aware of.
Static Environment
------------------
This allows to boot stock Synology firmware at least. In order to be a
little more flexible when it comes to booting custom kernels, do not
only load zImage partition, but also rd.gz into memory. This way it is
possible to use about 7MB for kernel with piggyback initramfs.
Signed-off-by: Phil Sutter <phil@nwl.cc>
Acked-by: Stefan Roese <sr@denx.de>
Reviewed-by: Tom Rini <trini@konsulko.com>
2015-12-25 13:41:25 +00:00
|
|
|
default "ds414" if TARGET_DS414
|
2015-12-21 12:40:37 +00:00
|
|
|
default "maxbcm" if TARGET_MAXBCM
|
2016-01-20 07:13:29 +00:00
|
|
|
default "theadorable" if TARGET_THEADORABLE
|
2015-12-21 12:40:37 +00:00
|
|
|
|
|
|
|
|
config SYS_CONFIG_NAME
|
|
|
|
|
default "clearfog" if TARGET_CLEARFOG
|
2016-05-17 13:04:16 +00:00
|
|
|
default "mvebu_db-88f3720" if TARGET_MVEBU_DB_88F3720
|
2016-01-29 08:14:54 +00:00
|
|
|
default "db-88f6720" if TARGET_DB_88F6720
|
2015-12-21 12:40:37 +00:00
|
|
|
default "db-88f6820-gp" if TARGET_DB_88F6820_GP
|
2016-09-22 00:56:14 +00:00
|
|
|
default "db-88f6820-amc" if TARGET_DB_88F6820_AMC
|
2016-05-25 06:21:21 +00:00
|
|
|
default "mvebu_db-88f7040" if TARGET_MVEBU_DB_88F7040
|
2015-12-21 12:40:37 +00:00
|
|
|
default "db-mv784mp-gp" if TARGET_DB_MV784MP_GP
|
mvebu: Support Synology DS414
This adds support for the MV78230 based DS414 NAS by Synology. The
relevant bits have been extracted from the 'synogpl-5004-armadaxp'
package Synology kindly published, garnished with a fair amount of
trial-and-error.
Sadly, support is far from perfect. The major parts I have failed in
are SATA and XHCI support. Details about these and some other things
follow:
Device Tree
-----------
The device tree file armada-xp-synology-ds414.dts has been copied from
Linux and enhanced by recent U-Boot specific changes to
armada-xp-gp.dts.
SATA Support
------------
There is a Marvell 88SX7042 controller attached to PCIe which is
supported by Linux's sata_mv driver but sadly not U-Boot's sata_mv.
I'm not sure if extending the latter to support PCI devices is worth the
effort at all. Porting sata_mv from Linux exceeded my brain's
capacities. :(
XHCI Support
------------
There is an EtronTech EJ168A XHCI controller attached to PCIe which
drives the two rear USB3 ports. After a bit of playing around I managed
to get it recognized by xhci-pci, but never was able to access any
devices attached to it. Enabling it in ds414 board config shows that it
does not respond to commands for whatever reason. The (somewhat) bright
side to it is that it is not even supported in Synology's customized
U-Boot, but that also means nowhere to steal the relevant bits from.
EHCI Support
------------
This seems functional after issuing 'usb start'. At least it detects USB
storage devices, and IIRC reading from them was OK. OTOH Linux fails to
register the controller if 'usb start' wasn't given before in U-Boot.
According to Synology sources, this board seems to support USB device
(gadget?) mode. Though I didn't play around with it.
PCIe Support
------------
This is fine, but trying to gate the clocks of unused lanes will hang
PCI enum. In addition to that, pci_mvebu seems not to support DM_PCI.
DDR3 Training
-------------
Marvell/Synology uses eight PUPs instead of four. Does not look like
this is meant to be customized in mainline U-Boot at all. OTOH I have
no idea what a "PUP" actually is.
PEX Init
--------
Synology uses different values than mainline U-Boot with this patch:
pex_max_unit_get returns 2, pex_max_if_get returns 7 and
max_serdes_lines is set to 7. Not changing this seems to not have an
impact, although I'm not entirely sure it does not cause issues I am not
aware of.
Static Environment
------------------
This allows to boot stock Synology firmware at least. In order to be a
little more flexible when it comes to booting custom kernels, do not
only load zImage partition, but also rd.gz into memory. This way it is
possible to use about 7MB for kernel with piggyback initramfs.
Signed-off-by: Phil Sutter <phil@nwl.cc>
Acked-by: Stefan Roese <sr@denx.de>
Reviewed-by: Tom Rini <trini@konsulko.com>
2015-12-25 13:41:25 +00:00
|
|
|
default "ds414" if TARGET_DS414
|
2015-12-21 12:40:37 +00:00
|
|
|
default "maxbcm" if TARGET_MAXBCM
|
2016-01-20 07:13:29 +00:00
|
|
|
default "theadorable" if TARGET_THEADORABLE
|
2015-12-21 12:40:37 +00:00
|
|
|
|
|
|
|
|
config SYS_VENDOR
|
|
|
|
|
default "Marvell" if TARGET_DB_MV784MP_GP
|
2016-05-17 13:04:16 +00:00
|
|
|
default "Marvell" if TARGET_MVEBU_DB_88F3720
|
2016-01-29 08:14:54 +00:00
|
|
|
default "Marvell" if TARGET_DB_88F6720
|
2015-12-21 12:40:37 +00:00
|
|
|
default "Marvell" if TARGET_DB_88F6820_GP
|
2016-09-22 00:56:14 +00:00
|
|
|
default "Marvell" if TARGET_DB_88F6820_AMC
|
2016-05-25 06:21:21 +00:00
|
|
|
default "Marvell" if TARGET_MVEBU_DB_88F7040
|
2015-12-21 12:40:37 +00:00
|
|
|
default "solidrun" if TARGET_CLEARFOG
|
mvebu: Support Synology DS414
This adds support for the MV78230 based DS414 NAS by Synology. The
relevant bits have been extracted from the 'synogpl-5004-armadaxp'
package Synology kindly published, garnished with a fair amount of
trial-and-error.
Sadly, support is far from perfect. The major parts I have failed in
are SATA and XHCI support. Details about these and some other things
follow:
Device Tree
-----------
The device tree file armada-xp-synology-ds414.dts has been copied from
Linux and enhanced by recent U-Boot specific changes to
armada-xp-gp.dts.
SATA Support
------------
There is a Marvell 88SX7042 controller attached to PCIe which is
supported by Linux's sata_mv driver but sadly not U-Boot's sata_mv.
I'm not sure if extending the latter to support PCI devices is worth the
effort at all. Porting sata_mv from Linux exceeded my brain's
capacities. :(
XHCI Support
------------
There is an EtronTech EJ168A XHCI controller attached to PCIe which
drives the two rear USB3 ports. After a bit of playing around I managed
to get it recognized by xhci-pci, but never was able to access any
devices attached to it. Enabling it in ds414 board config shows that it
does not respond to commands for whatever reason. The (somewhat) bright
side to it is that it is not even supported in Synology's customized
U-Boot, but that also means nowhere to steal the relevant bits from.
EHCI Support
------------
This seems functional after issuing 'usb start'. At least it detects USB
storage devices, and IIRC reading from them was OK. OTOH Linux fails to
register the controller if 'usb start' wasn't given before in U-Boot.
According to Synology sources, this board seems to support USB device
(gadget?) mode. Though I didn't play around with it.
PCIe Support
------------
This is fine, but trying to gate the clocks of unused lanes will hang
PCI enum. In addition to that, pci_mvebu seems not to support DM_PCI.
DDR3 Training
-------------
Marvell/Synology uses eight PUPs instead of four. Does not look like
this is meant to be customized in mainline U-Boot at all. OTOH I have
no idea what a "PUP" actually is.
PEX Init
--------
Synology uses different values than mainline U-Boot with this patch:
pex_max_unit_get returns 2, pex_max_if_get returns 7 and
max_serdes_lines is set to 7. Not changing this seems to not have an
impact, although I'm not entirely sure it does not cause issues I am not
aware of.
Static Environment
------------------
This allows to boot stock Synology firmware at least. In order to be a
little more flexible when it comes to booting custom kernels, do not
only load zImage partition, but also rd.gz into memory. This way it is
possible to use about 7MB for kernel with piggyback initramfs.
Signed-off-by: Phil Sutter <phil@nwl.cc>
Acked-by: Stefan Roese <sr@denx.de>
Reviewed-by: Tom Rini <trini@konsulko.com>
2015-12-25 13:41:25 +00:00
|
|
|
default "Synology" if TARGET_DS414
|
2015-12-21 12:40:37 +00:00
|
|
|
|
2015-08-25 11:18:38 +00:00
|
|
|
config SYS_SOC
|
|
|
|
|
default "mvebu"
|
|
|
|
|
|
|
|
|
|
endif
|
